Answer a few questions about your website or app and get a clear privacy policy and terms of use that match what you actually do. Copy them as Markdown or HTML, or download them. It is free, and your answers stay on this device. This is a starting template, not legal advice.
How to make a privacy policy, step by step
- Enter your business or app name, whether it is a website, an app or both, the date, your address and a contact email.
- Choose the information you collect, such as email addresses, accounts, payments, analytics, cookies, location or photos and files.
- Choose the third-party services you use, such as analytics, payments, crash reports, advertising or sign-in.
- Tick the boxes for children, EU or UK users and California users if they apply.
- Switch between Privacy policy and Terms of use, read each one, then use Copy as Markdown, Copy as HTML or Download .md.
Do I need a privacy policy?
Almost certainly, if you collect any personal information at all, including email sign-ups, analytics or cookies. Laws such as the GDPR in Europe and the UK and the CCPA in California expect one, and the Apple App Store and Google Play ask for a privacy policy link for every app. Even a site that collects nothing benefits from saying so plainly.
Make it match what you really do
A policy is only useful if it is true. Before publishing, check every service you use, including analytics scripts, embedded videos, fonts, chat widgets and payment buttons, since many of them collect data. If you add a new service later, update the policy and the date at the top.
Where to put it
Publish each document on its own page, such as /privacy and /terms, and link to both from your site's footer, sign-up form and app settings. App stores ask for the privacy policy address when you submit an app, so keep it at a stable link.
When to get professional advice
The result is a plain-English starting point. It cannot know everything about your business or the laws where you and your users live. Read it carefully, change anything that does not fit, and have a qualified professional review it if you collect sensitive data, take payments or serve children. Services for children have strict rules, such as COPPA in the US.
Who uses it
Bloggers, shop owners, app makers, freelancers with a portfolio, and anyone preparing a launch. Check your site afterwards with the pre-launch scan.
Questions
Is this legal advice?
No. It is a starting template. Get professional advice for anything high risk.
Is my information sent anywhere?
No. Your answers stay on this device.
Do I need terms of use as well?
They are a good idea for most sites and apps, because they set out the rules for using your service. The tool makes both.
How often should I update my policy?
Whenever you add a service, collect new information or change how you use it, and update the date at the top.