The Legal category in AIUNIFY PROS SUITE currently contains four active subscriber-facing tools:
The current Sidebar routes these tools to:
/privacy-policy/terms-of-service/disclaimer-generator/refund-policyPrivacy Policy and Terms of Service are marked Pro in the current Sidebar metadata. Disclaimer and Refund Policy are active Legal tools without the Pro marker.
The shorter Sidebar labels open pages whose full workspace titles are:
Unlike specialized workspaces such as Recipe Generator, Meeting Notes, or Resume Builder, all four current Legal tools use AIUNIFY's shared:
Standard AI Generator Workspace
There is no separate legal-document wizard in the current subscriber source.
All four Legal tools use the same basic operating sequence:
Describe the Business or Legal Need
→ Generate
→ Review the AI Draft
→ Copy or Download
→ Customize and Verify
→ Obtain Appropriate Review Where Needed
→ Publish or Implement Through the Appropriate Business System
The Legal tools generate written content.
They do not independently determine whether the resulting document is legally sufficient for:
The safest operating interpretation is:
AIUNIFY PROS SUITE Legal Tools create AI-generated legal-document drafts that should be reviewed against the actual business practices, jurisdiction, contractual terms, and regulatory requirements that apply to the subscriber.
Using a PROS SUITE Legal generator does not itself establish professional legal representation.
The current Legal category does not automatically file documents with:
The four Legal tools do not provide a source-verified:
workflow.
Generated Policies or Terms are not automatically added to:
Publishing remains a separate operation.
The active Legal Sidebar contains:
The Sidebar currently marks Privacy Policy with:
New
metadata.
The Sidebar also marks Privacy Policy:
Pro.
Terms of Service is currently marked:
New.
Terms of Service is also marked:
Pro.
Disclaimer is marked:
New
but not Pro in the current Sidebar definition.
Refund Policy is also marked:
New
without the Pro metadata used on Privacy Policy and Terms of Service.
The Pro designation indicates the Tool may be associated with higher-tier access in AIUNIFY PROS SUITE.
Actual availability can also depend on:
as documented in earlier chapters.
Each of the four active Legal pages directly renders Standard ToolPage.
The individual page files do not add a separate Legal-specific FeatureGuard wrapper.
This does not override broader PROS SUITE subscription or access controls.
The source contains additional Legal feature definitions for:
However, these entries are commented out in the current shared feature catalogue.
Do not expect a standalone:
Cookie Policy
Tool in the current Legal Sidebar.
A commented:
GDPR Compliance
feature exists in source references, but it is not part of the current active subscriber Legal menu.
The source contains a commented Legal Summarizer feature reference.
It should not be treated as an available subscriber Tool in this version.
A Contract Clause feature is also present only as a commented reference.
The active Contract Generator covered in Chapter 35 belongs to the Business category.
It is separate from the inactive/commented Legal Contract Clause feature.
Standard ToolPage requires an authenticated AIUNIFY PROS SUITE session.
If authentication is unavailable, the shared page redirects toward:
/login.
Each current Legal Tool displays:
The shared Header structure is source-verified in ToolPage.
The main left-side Card is:
Input
The shared description is:
Describe what you want to generate.
All four Legal tools use one main natural-language Textarea.
They do not provide structured legal fields such as:
as separate controls.
These details must be entered inside the Prompt when relevant.
Each Legal Tool provides different Prompt guidance.
Those exact placeholders are documented in the individual Tool sections below.
Select:
Generate
to begin the AI request.
During active generation:
Generating...
appears on the Generate button.
The Generate button is disabled when the Prompt contains no meaningful text.
Inside Standard ToolPage:
Ctrl + Enter
also starts generation.
If generation is attempted without usable text, the current message is:
Input required
with:
Please enter a prompt to continue.
Each Legal page provides three built-in examples.
Selecting one fills the Prompt field.
The subscriber must still select:
Generate
or use Ctrl + Enter.
All four Legal Tools currently use Standard ToolPage's generic System instruction:
“You are a helpful AI assistant for the tool: [Tool Title]. [Tool Description]”
rather than a specialized legal drafting engine.
The page title and description tell the selected AI Model the intended Legal purpose.
However, the ToolPage does not itself impose a comprehensive fixed legal drafting schema.
Because the interface is open-ended, document quality depends heavily on the details supplied by the subscriber.
The Tool does not automatically interview the subscriber about every fact that may matter to the document.
If the Prompt only says:
“Write a privacy policy”
the Model has substantially less business-specific information than if you provide:
The Tool does not automatically inspect your:
to discover your actual practices.
A generated Policy or Terms document should accurately reflect what the business actually does.
The right-side Card is:
Output
with:
Generated content will appear here.
Generated Legal content appears progressively.
The shared Output is presented through AIUNIFY's Markdown renderer.
This can organize a Legal draft with:
depending on the generated response.
When Output is available, the Header displays a Copy action.
Copy places the current generated content on the browser Clipboard.
Successful Copy displays:
Copied!
with:
Content copied to clipboard.
Standard Legal ToolPage also provides a Download button.
All current Legal ToolPage downloads use:
plain text (.txt).
Current pattern:
[tool-id]-output.txt
Privacy Policy downloads as:
privacy-policy-output.txt
Terms of Service downloads as:
terms-of-service-output.txt
Disclaimer downloads as:
disclaimer-generator-output.txt
Refund Policy downloads as:
refund-policy-output.txt
The current Legal ToolPage does not generate a PDF.
It does not create a Word .docx file.
There is no dedicated Legal-document HTML export.
Any signature language that appears is simply part of generated text.
The Tool does not create executable signature fields.
The Output Card is not directly editable in Standard ToolPage.
For detailed revisions:
There is no persistent Save action.
No source-verified persistent Legal-document history is available through these Tool pages.
The Tool does not provide:
for Legal drafts.
Important Legal drafts should be saved externally before generating replacements.
Standard ToolPage includes a Reset control.
Reset clears:
and returns focus toward the Prompt field.
Modifying the Prompt and selecting Generate creates a new AI result.
Because there is no persistent version-management system, Copy or Download an important draft before replacing it.
Standard Legal Tools use the same selected AI Model pathway as other Standard ToolPage generators.
The shared Legal request passes the specific toolId to AIUNIFY's streaming generation function.
privacy-policy
terms-of-service
disclaimer-generator
refund-policy
The shared AI streaming system can use subscriber-configured provider API Keys as documented in Chapter 11.
Different Models can vary in:
Therefore, a document generated using one Model should not be assumed identical to a version generated using another.
Standard ToolPage determines its Base Cost using:
The live page shows:
[amount] tokens per use
and the subscriber's current Token balance.
When the selected Model is categorized as OpenAI, Standard ToolPage applies its current:
1.5×
display multiplier to the Base Cost, rounded upward.
If the live page displays a different Token amount from a static manual reference, use the live Tool display.
| Legal ToolCurrent Base Catalogue Reference | |
| Privacy Policy | 30 Tokens |
| Terms of Service | 30 Tokens |
| Disclaimer | 15 Tokens |
| Refund Policy | 15 Tokens |
The route values and feature catalogue currently agree on these amounts.
Both currently reference:
30 Tokens
Both currently reference:
30 Tokens
Both currently reference:
15 Tokens
Both currently reference:
15 Tokens
Navigate to:
Sidebar → Legal → Privacy Policy
Route:
/privacy-policy
The full workspace title is:
Privacy Policy Generator.
Current description:
Generate comprehensive privacy policies for your website or app.
Current guidance:
Describe your business, data collection practices, and jurisdiction...
Privacy policy for an e-commerce website
GDPR-compliant privacy policy for a SaaS app
Privacy policy for a mobile fitness app.
Current Base Reference:
30 Tokens
The current Sidebar identifies Privacy Policy as:
Pro.
A strong Privacy Policy Prompt should identify the business or service being described.
State whether the Policy applies to:
The built-in placeholder specifically asks the subscriber to describe:
jurisdiction.
This is important because privacy obligations can differ by location.
The Prompt should accurately describe what information the business actually collects.
Depending on the business, relevant categories can include:
Only include categories that accurately reflect the business.
Explain why information is collected or used.
If the service creates user accounts, describe this accurately.
If the business accepts payments, describe relevant payment-handling practices accurately.
If Analytics services are used, include accurate information about them.
If Personal Data is used for Email, advertising, or other Marketing purposes, describe the actual practice.
Describe how the company communicates with customers if relevant.
If third-party processors or platforms handle information, this can be relevant to the Privacy Policy Prompt.
If the Website uses Cookies or similar tracking technologies, provide accurate information.
If the applicable legal framework provides user privacy rights, the document may need to address them.
The Tool does not automatically determine every jurisdiction-specific right from verified current law.
Provide the correct business contact process where the final Policy should direct privacy requests.
Privacy Policy Generator does not automatically scan a Website to determine what data it collects.
It does not source-verify live Cookie detection.
It does not automatically detect:
The Tool does not automatically map how Personal Data moves through your technical infrastructure.
It does not automatically retrieve all subprocessors or data vendors.
It does not inspect databases to determine actual retention periods.
The built-in example can request a:
GDPR-compliant privacy policy
but the current Tool is a text generator.
It does not perform a comprehensive compliance audit.
Similarly, the Tool does not automatically audit a business against every U.S. state privacy requirement.
The Tool does not independently establish which privacy regimes apply to a business.
Privacy Policy Generator does not implement Cookie/consent controls.
It does not operationalize:
A Policy that says one thing while the business does another can create operational and legal risk.
Review generated language carefully.
Do not copy broad categories merely because they sound legally comprehensive.
Explain what users actually do on the Website/App.
Include relevant location context where known.
Provide key third-party services when appropriate.
Review generated rights language against the jurisdictions that actually apply.
Do not publish placeholder or invented contact information.
Privacy Policies should be checked against:
Navigate to:
Sidebar → Legal → Terms of Service
Route:
/terms-of-service
Full workspace title:
Terms of Service Generator.
Current description:
Generate comprehensive terms of service for your platform.
Current guidance:
Describe your service, user obligations, and key policies...
Terms of service for a SaaS platform
User agreement for a social media app
Terms and conditions for an online marketplace.
Current Base Reference:
30 Tokens
The Sidebar currently identifies Terms of Service as:
Pro.
Explain what the Platform actually provides.
If minimum Age, business status, professional eligibility, or other qualification matters, include the real requirement.
Describe what users are responsible for when they create an account.
The Tool's placeholder specifically asks for:
user obligations.
These should match the actual operating rules of the Platform.
If the Platform prohibits certain behavior, describe those restrictions.
For subscription services, provide accurate:
where appropriate.
If the service offers a Free Trial, describe its actual terms.
If Plans limit:
include accurate information where relevant.
Specify how the business handles its own intellectual property and user-provided content where applicable.
For platforms where customers upload or create content, describe the actual rights and responsibilities.
If the business can suspend Accounts, describe the circumstances accurately.
Provide actual account termination rules.
Terms may include disclaimers, but these should align with the business and applicable law.
If liability limitations are desired, identify the relevant business/jurisdiction context for review.
If the business uses:
do not allow the AI to invent that approach without business approval.
If a Governing Law clause is appropriate, provide the intended jurisdiction rather than allowing arbitrary inference.
Use accurate company contact details.
The Tool does not inspect how Account functionality actually behaves.
It does not automatically retrieve live pricing, renewals, or cancellation behavior.
Generated Terms do not automatically stay synchronized with future Plan changes.
Terms are generated text.
Users do not accept them through this page.
The Tool does not add:
I Agree
checkboxes to your Product.
The Tool does not record which user accepted which version.
The AI can draft a clause but does not independently establish which Governing Law is legally appropriate.
The generator does not operate an arbitration process.
Generating Terms does not guarantee every clause is enforceable.
If the business changes:
the Terms do not automatically regenerate or update.
Describe actual service functionality.
Never publish invented:
Make prohibited conduct and permitted use clear.
Ensure ownership/licensing language reflects the actual business model.
Dispute Resolution and Governing Law can have significant consequences.
When the Product changes materially, review whether the Terms should also change.
Navigate to:
Sidebar → Legal → Disclaimer
Route:
/disclaimer-generator
Full title:
Disclaimer Generator.
Current description:
Generate appropriate disclaimers for websites and content.
Current guidance:
Describe the type of disclaimer needed and your content type...
Medical disclaimer for a health blog
Affiliate disclaimer for product reviews
Financial disclaimer for investment content.
Current Base Reference:
15 Tokens
The active Sidebar entry is marked New but not Pro.
Explain what material the Disclaimer applies to.
Identify who is likely to use or rely on the content.
Examples can include:
Where relevant, disclose actual relationships such as Affiliate arrangements.
The built-in Medical Disclaimer example confirms health-related content is a supported generation use case.
The built-in Financial Disclaimer example confirms investment-related content is another intended use case.
The built-in Affiliate example confirms the Tool can generate disclosure-style content for product reviews.
The Tool generates text.
It does not determine the legal effect of that text in a specific circumstance.
The Tool does not automatically audit whether a Disclaimer satisfies every applicable regulatory disclosure requirement.
It does not inspect all Website or Channel content to determine which disclaimers are required.
The Tool does not automatically find affiliate URLs.
It does not monitor future financial content to ensure disclaimers remain appropriately displayed.
The Tool does not verify the underlying health or medical claims contained in content.
The Tool does not place the Disclaimer on:
It does not control when a disclosure is shown relative to the content.
Do not use a generic Disclaimer when the activity is highly specific.
Do not disclose an arrangement that does not exist, and do not omit one that does when disclosure is required.
A Disclaimer does not make false or misleading underlying claims acceptable.
Financial, health, professional, and other high-stakes content can require particular care.
The generated text must still be placed through the appropriate publishing system.
Navigate to:
Sidebar → Legal → Refund Policy
Route:
/refund-policy
Full workspace title:
Refund Policy Generator.
Current description:
Create clear refund and return policies for your business.
Current guidance:
Describe your product/service type and refund preferences...
30-day refund policy for digital products
Return policy for an e-commerce clothing store
Cancellation policy for a subscription service.
Current Base Reference:
15 Tokens
The Sidebar entry is active and marked New, without the Pro flag.
Tell the Tool what the business sells.
Examples:
If applicable, provide the actual Refund period.
For physical goods, include the intended Return period.
If Items must be:
state the actual requirement.
Identify actual exclusions.
Digital-product Refund rules can differ from physical-product Returns.
Describe the intended policy accurately.
If the Product is subscription-based, explain:
as applicable.
If Free Trials are used, state the actual conversion/cancellation process.
For physical Returns, describe who bears Return Shipping costs if relevant.
If Refund processing has a defined expected period, provide the actual business practice.
If Refunds return to the original Payment Method, state this only if accurate.
If Exchanges are offered, include the actual process.
If Store Credit can be provided, describe it accurately.
Specify how customers should request a Refund or Return.
Refund Policy Generator does not connect to actual customer Orders.
The Tool cannot issue money back to a Customer.
It does not process Refunds through:
No RMA or Return Authorization number is created.
The Tool does not generate Return Shipping labels.
Returned Items are not added back into stock.
Generating Cancellation language does not cancel an actual customer subscription.
The Tool does not independently determine whether the requested Refund Policy complies with every applicable consumer-protection requirement.
A subscriber may request:
No refunds
but the Tool does not establish whether that position is legally permissible for every Product, Customer, or jurisdiction.
Your written Policy should match how the business actually handles Refunds and Returns.
Use realistic timelines.
If certain Products have different rules, identify them.
The published Policy and actual billing/cancellation settings should agree.
Support teams should follow the same Policy customers see.
Useful business facts include:
Be explicit about whether you need:
Do not assume the Model will infer it correctly.
Examples:
The AI should draft around your real operating rules.
Important figures should be supplied by the subscriber.
Use actual:
when known.
Use the correct legal or commercial name intended for the document.
Use the correct:
where needed.
Before publishing, search the generated document for placeholder language such as:
[Company Name][Email Address][State][Effective Date]and replace it appropriately.
The Legal Tool does not publish the document.
A Website owner can Copy the approved final text into the Website's appropriate page-management system.
App operators may need to publish the final document through their Website, App interface, App Store metadata, or other appropriate workflow.
The Legal Tool does not perform those steps.
If Terms or Refund information needs to appear at Checkout, implementation must be performed separately.
If users must accept Terms during registration, the application must separately implement that acceptance workflow.
The Tool does not automatically add Footer or Navigation links.
The generator does not maintain a version-effective-date database.
No user-acceptance ledger is maintained by these Tool pages.
Business operations can change.
Consider reviewing documents after significant changes involving:
Entering new markets can introduce different requirements.
Privacy documentation should be revisited when Data practices change materially.
Terms and Refund Policies should reflect actual billing behavior.
Disclosures may need changes when advertising or Affiliate relationships change.
PROS SUITE does not automatically detect those business changes and update the documents.
A Legal Prompt usually does not need:
Provide enough information to draft accurately without unnecessarily exposing confidential credentials.
Do not paste unnecessary customer or employee Personal Data into the generator.
Subscriber-configured AI provider Keys are managed through the PROS SUITE Model/API-Key workflow described earlier.
They should not be pasted into a Legal Prompt.
Enter non-whitespace Prompt content.
Add enough information to describe the intended Legal document.
Provide additional detail about:
Replace placeholders with accurate business information before use.
Explicitly provide the correct Company Name and regenerate or edit externally.
State the intended jurisdiction in the Prompt and regenerate.
Standard ToolPage has no direct Legal Output editor.
Copy the result into a document editor.
The current page downloads .txt only.
DOCX export is not implemented.
There is no persistent Legal Save function.
No Legal version-history system exists in these Tool pages.
The Tool generates text only.
Website publishing must be completed elsewhere.
Regenerate with an accurate list of Data practices or remove the inaccurate provision during external editing.
Add the relevant business practice or third-party service to the Prompt and regenerate/revise.
That built-in Prompt is an example of requested generation.
It should not be interpreted as a source-verified compliance certification.
There is no standalone active Cookie Policy Tool in the current Legal Sidebar.
Cookie-related language can be requested within a relevant Legal Prompt, but the inactive/commented Cookie Policy entry should not be presented as an available Tool.
Provide the exact current billing and cancellation terms.
Do not accept material clauses automatically.
Revise the document according to the actual business decision and appropriate legal review.
The Generator cannot implement acceptance.
That functionality belongs in the Website/Application.
Specify the exact Content Type and risk area.
Use the Affiliate example or explain the actual Affiliate relationship.
The Tool supports drafting those types through its example use cases, but the generated language should still be reviewed for the specific content and jurisdiction.
The document and actual billing system need to be reconciled manually.
Refund Policy Generator does not process financial transactions.
Use the appropriate billing/payment system.
The Generator creates policy language only.
Use the actual subscription-management system to perform a cancellation.
| CapabilityPrivacy PolicyTerms of ServiceDisclaimerRefund Policy | ||||
| Standard ToolPage | Yes | Yes | Yes | Yes |
| Pro Sidebar Marker | Yes | Yes | No | No |
| Prompt Input | Yes | Yes | Yes | Yes |
| Example Prompts | Yes | Yes | Yes | Yes |
| Streaming Output | Yes | Yes | Yes | Yes |
| Copy | Yes | Yes | Yes | Yes |
| TXT Download | Yes | Yes | Yes | Yes |
| Direct Edit | No | No | No | No |
| Save | No | No | No | No |
| Version History | No | No | No | No |
| PDF Export | No | No | No | No |
| DOCX Export | No | No | No | No |
| Automatic Publishing | No | No | No | No |
| FunctionCurrent Legal Tools Execute It? | |
| Generate Legal Draft | Yes |
| Copy Draft | Yes |
| Download TXT | Yes |
| Edit in Tool | No |
| Save Legal Project | No |
| Publish to Website | No |
| Obtain User Acceptance | No |
| Record Acceptance | No |
| Sign Agreement | No |
| File With Government | No |
| Issue Refund | No |
| Cancel Subscription | No |
| Scan Website Privacy Practices | No |
| Certify Legal Compliance | No |
| ToolCatalogue ReferenceRoute Fallback | ||
| Privacy Policy | 30 | 30 |
| Terms of Service | 30 | 30 |
| Disclaimer | 15 | 15 |
| Refund Policy | 15 | 15 |
Privacy Policy Generator currently supports:
It does not establish:
Terms of Service Generator currently supports:
It does not establish:
Disclaimer Generator currently supports:
It does not establish:
Refund Policy Generator currently supports:
It does not establish:
Document Actual Data Practices
→ Identify Website/App
→ Identify Jurisdictions
→ Identify Data Categories
→ Identify Data Uses
→ Identify Third Parties
→ Generate Privacy Policy
→ Review Every Clause
→ Compare Against Actual Technology
→ Obtain Appropriate Legal/Privacy Review
→ Publish
→ Maintain Over Time
Document Product Rules
→ Document Account Rules
→ Document Billing
→ Document Cancellation
→ Document User Obligations
→ Document IP/User Content Rules
→ Choose Approved Dispute/Governing-Law Framework
→ Generate Terms
→ Review
→ Implement Acceptance Separately
→ Track Future Revisions Separately
Identify Content
→ Identify Risk Area
→ Identify Commercial/Affiliate Relationships
→ Generate Disclaimer
→ Review Accuracy
→ Verify Applicable Disclosure Requirements
→ Place the Approved Disclaimer Through the Publishing System
Define Product Type
→ Define Refund Window
→ Define Return Conditions
→ Define Exceptions
→ Define Subscription/Cancellation Rules
→ Define Processing Workflow
→ Generate Refund Policy
→ Review Against Actual Billing Operations
→ Verify Applicable Consumer Requirements
→ Publish
→ Train Support Staff
Confirm all:
Confirm:
Confirm:
Confirm that legal-location references are intentional.
Confirm all:
Privacy Policy, Terms of Service, Disclaimer, and Refund Policy should not contradict one another.
The Legal documents should also be consistent with:
Customer Support, Billing, and Product teams should follow the published rules.
AIUNIFY PROS SUITE currently exposes four active Legal Tools:
Privacy Policy and Terms of Service carry Pro Sidebar metadata, while Disclaimer and Refund Policy do not. All four are marked New in the current Sidebar configuration.
None of the four active Legal tools uses a specialized legal wizard in the current subscriber source.
They use AIUNIFY's shared Standard ToolPage, which provides:
Input → Generate → Streaming Markdown Output → Copy → TXT Download
Standard ToolPage instructs the AI using the Tool's Title and Description:
“You are a helpful AI assistant for the tool: [title]. [description]”
and passes the subscriber's Prompt with the Tool ID.
Consequently, detailed and accurate subscriber input is especially important.
Privacy Policy Generator is designed to create comprehensive Policies for Websites or Apps.
Its Prompt guidance specifically asks the subscriber to describe:
and includes examples for E-Commerce, SaaS/GDPR, and Mobile Fitness applications. Its current Base Reference is 30 Tokens and the Sidebar marks it Pro.
The Tool does not scan a Website, inspect Cookies, map Data flows, determine all applicable privacy laws, certify compliance, or implement consent-management functions.
Terms of Service Generator creates AI-drafted Terms for a Platform.
Its Prompt guidance requests:
and includes examples for SaaS, Social Media, and Online Marketplace platforms. The current Base Reference is 30 Tokens and the Sidebar marks Terms of Service Pro.
The Tool does not implement clickwrap acceptance, store version acceptance records, inspect billing configuration, execute arbitration, or guarantee clause enforceability.
Disclaimer Generator creates Website/content Disclaimer drafts.
Current built-in examples specifically include:
Its current Base Reference is 15 Tokens.
The Tool does not audit underlying content, determine all required disclosures, validate medical/financial claims, or automatically place disclosures into published content.
Refund Policy Generator creates Refund, Return, and Cancellation Policy drafts.
Current examples include:
Its current Base Reference is 15 Tokens.
The Tool does not issue Refunds, cancel subscriptions, generate Return Authorizations, create shipping labels, modify inventory, or verify every consumer-law requirement.
The Legal category currently uses:
The feature catalogue and individual Route values currently agree.
For Standard ToolPage, live Tool settings can still override the catalogue value, and the page applies its OpenAI Model display multiplier when applicable.
Although the source contains commented feature references for:
those features are not part of the active subscriber Legal Sidebar in the current version and should not be presented as available Tools.
The central operating principle for Chapter 39 is:
AIUNIFY PROS SUITE Legal Tools accelerate the drafting of Privacy Policies, Terms of Service, Disclaimers, and Refund Policies. They do not independently verify the subscriber's business practices, determine every applicable legal requirement, guarantee enforceability or compliance, execute transactions, collect signatures, or publish documents. The final document should accurately reflect the actual business and receive the level of legal or professional review appropriate to its use.