Generate a Markdown privacy policy draft for a SaaS from a few questions about what data you collect and which services you use. A starting point, not legal advice.
How to use the Privacy policy generator
- Answer the questions about data, analytics, payments and email.
- Review the draft.
- Have it checked for your jurisdiction, then publish it.
What a SaaS policy covers
What you collect and why, the legal basis, the processors you share data with (hosting, analytics, payments, email), how long you keep it, and how people can access or delete their data.
What the draft includes
The policy is built from your answers. It always covers the information you collect, how you use it, sharing, retention, people's rights, children, changes and contact. Ticking analytics, payments, AI providers or ads adds the matching data types and processors; ticking AI providers adds a section on AI features. The retention section says data is kept while the account is active and up to 12 months after, the rights section promises a reply within 30 days, and the children section uses the minimum age you choose. The date at the top is today's.
Before you publish
Read every line against what your product really does. List your actual processors by name if your market expects it (GDPR readers often do), such as your host, email provider and payment processor. Check the retention period and response time match what you can deliver. If you send product data to AI providers, confirm their terms really bar training before keeping that sentence. Make sure the contact email works. Link the policy from your footer and sign-up form, and update the date whenever you change it.