Replace boilerplate with a fillable structure
The original was entirely reassurance — importance of privacy, strict measures — with nothing actionable. It becomes five sections: what, why, how long, who, and your rights.
Describe your business and how you handle data, and get a structured first draft of a privacy policy or terms of service. Entity name, jurisdiction, retention periods, and contact details are left as explicit slots — this is a drafting starting point, not a publishable legal document.
We map what you collect, why, how long you keep it, and who you share it with, leaving only-you-can-answer fields as slots.
SAMPLE OUTPUT
This is the complete output for the source text in the demo above: a completeness score, drafting notes, information for you to complete, and the policy draft. It is a demonstration, not a customer case.
The original was entirely reassurance — importance of privacy, strict measures — with nothing actionable. It becomes five sections: what, why, how long, who, and your rights.
The legal entity, registered address, and retention periods are absent from the source, so they become TODO slots you complete and stand behind.
“In accordance with relevant laws and regulations” implies a compliance finding nobody made. It becomes an explicit note that applicability needs professional judgement.
# Privacy policy (first draft) **Operator**: TODO legal entity name **Registered address**: TODO **Contact**: TODO ## What we collect - Account data: email address, used to identify your account and sign you in. - Content you submit: the text you paste into the workspace, processed for the single request and not intentionally stored. TODO: confirm whether any logs or backups retain it. ## Why - To operate the service and to prevent abuse. ## How long - Account data: TODO retention period - Submitted content: TODO retention period ## Sharing - Payment processing is handled by Paddle, which acts as Merchant of Record. TODO: list any other processors. ## Your rights - Access, correction, deletion: TODO describe the route and response time **Note**: this is a first draft. It is not legal advice and does not state compliance with any law. Have a qualified professional review it before publishing.
WHAT THE DRAFT DOES
What is collected, why, how long, who it goes to, how to withdraw — five things stated clearly beat ten pages of boilerplate.
Entity name, jurisdiction, retention periods: only you know these. A slot is far safer than a plausible value.
We do not assess which regulations apply to you and will not write “this policy complies with X”. That would let you skip the review you actually need.
WHY IT IS WORTH DOING
A meaningful share of a lawyer's fee goes into producing the structure. Hand over a skeleton first and the review costs noticeably less.
Missing “how long you keep data” or “how to delete an account” is far worse than inelegant phrasing. Structure prevents omissions.
An invented entity name or jurisdiction makes the whole document unusable. A blank is at least visibly incomplete.
Note: requirements for privacy policies and terms depend on business type, user location, and data handling — GDPR, CCPA/CPRA, PIPL, and others. This site does not determine which apply to you and provides no legal advice. Have a qualified professional review the draft before publishing.
REWRITE DEMO
Privacy Policy We attach great importance to the protection of user privacy. We will take strict security measures to protect your personal information in accordance with relevant laws and regulations. We may collect and use your personal information when necessary in order to improve our service quality. Thank you for your trust and support.
# Privacy policy (first draft) **Operator**: TODO legal entity name **Registered address**: TODO **Contact**: TODO ## What we collect - Account data: email address, used to identify your account and sign you in. - Content you submit: the text you paste into the workspace, processed for the single request and not intentionally stored. TODO: confirm whether any logs or backups retain it. ## Why - To operate the service and to prevent abuse. ## How long - Account data: TODO retention period - Submitted content: TODO retention period ## Sharing - Payment processing is handled by Paddle, which acts as Merchant of Record. TODO: list any other processors. ## Your rights - Access, correction, deletion: TODO describe the route and response time **Note**: this is a first draft. It is not legal advice and does not state compliance with any law. Have a qualified professional review it before publishing.
Demo sample: boilerplate becomes a fillable structure, entity and retention stay blank, and the no-compliance-claim note is explicit. Paste your business description to get your version (sign-in required; one credit per run).
WHY YOU CAN TRUST IT
We do not assess which regulations apply to you. Any compliance statement could convince you to skip a review you actually need.
Legal entity, registered address, jurisdiction, retention periods, and contact details are all left as slots — never plausible values.
Each output ends with an explicit note that it is a starting point requiring a qualified professional before publication.
Submitted text is used for this single AI request and is not intentionally persisted. See the Privacy Policy.
FAQ
No. It is a structured first draft that a qualified professional must review before use. It is not legal advice.
No. Applicable law depends on your business type, user locations, and data handling, and is a professional judgement.
Because only you know them. A plausible value would build the whole document on a false premise; a blank is at least visibly incomplete.
One credit per run, usually done in seconds, returning the draft, drafting notes, and slots to complete.
No. Credits never expire — whatever you do not use carries over to the next cycle instead of resetting.
Not yet. Each run processes one document and consumes one credit; there is no bulk upload or API today. Email us with your use case and we will assess it.
Not intentionally. Text is used for this single AI request only. See the Privacy Policy.
Solo developers, early teams, and founders who need a skeleton to hand to a lawyer — anyone starting a policy document from a blank page.
SIMPLE PRICING
For an occasional publishing cadence, with a focused monthly credit allocation.
For frequent publishers who iterate on content continuously.
Our largest monthly credit allocation, for the heaviest continuous usage.
Credits never expire: unused credits carry over instead of resetting. Credits apply to this site only and are not shared with other sites.
Prices shown are USD baselines; final currency, taxes, and discounts are determined by Paddle for the checkout location.