BusinessCollectible prompt

Privacy policy draft based on what your site collects

Get a plain-language privacy policy built from the data and services your site really uses.

ClaudeChatGPTGemini

Curated by Nvoka

Nvoka wordmark logo
Nvoka wordmark logoBusiness

Privacy policy draft based on what your site collects

Act as a privacy writer who drafts website policies for small businesses. Draft a privacy policy for {{business_name}} at {{website_url}}. This is a starting draft to review with a lawyer, not legal advice. Before writing, ask me: 1. What personal data the site collects, and where: contact forms, accounts, bookings, payments, newsletter, uploads, analytics, cookies 2. Every service that touches that data, such as hosting, database, email, payments, analytics and support chat. What I know so far: {{integrations}} 3. Where we're based and where our visitors live, since that decides which laws apply, such as GDPR, UK GDPR or US state privacy laws 4. Whether children might use the site, and whether we sell or share data for advertising Then write it with: - A short plain-words summary at the top, then the full policy - Who we are and how to contact us about privacy - What we collect, grouped by source, and why, with the legal basis where GDPR applies - Who we share it with, naming each processor and what it does - International transfers, if any - How long we keep each kind of data, as real periods - People's rights and exactly how to use them, with a response time - Cookies, linking to a separate cookie policy - Security in honest terms, children, changes to this policy, and an effective date Rules: - Never invent a practice, a certification or a promise like "we never share your data" unless I've confirmed it - Mark anything you had to assume with TO CONFIRM so I can find it - Short sentences, around an eighth-grade reading level Also give me the page layout: an H1, a linked table of contents, H2 sections with anchor links, the last-updated date near the top, and a footer link on every page.
Businessnvoka.com/library/nvoka-privacy-policy-draft-for-your-websiteScan to open
Business

Privacy policy draft based on what your site collects

Get a plain-language privacy policy built from the data and services your site really uses.

Nvoka logo

Curated by Nvoka

ClaudeChatGPTGemini
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 3 filled

Your prompt

Act as a privacy writer who drafts website policies for small businesses. Draft a privacy policy for {{business_name}} at {{website_url}}. This is a starting draft to review with a lawyer, not legal advice. Before writing, ask me: 1. What personal data the site collects, and where: contact forms, accounts, bookings, payments, newsletter, uploads, analytics, cookies 2. Every service that touches that data, such as hosting, database, email, payments, analytics and support chat. What I know so far: {{integrations}} 3. Where we're based and where our visitors live, since that decides which laws apply, such as GDPR, UK GDPR or US state privacy laws 4. Whether children might use the site, and whether we sell or share data for advertising Then write it with: - A short plain-words summary at the top, then the full policy - Who we are and how to contact us about privacy - What we collect, grouped by source, and why, with the legal basis where GDPR applies - Who we share it with, naming each processor and what it does - International transfers, if any - How long we keep each kind of data, as real periods - People's rights and exactly how to use them, with a response time - Cookies, linking to a separate cookie policy - Security in honest terms, children, changes to this policy, and an effective date Rules: - Never invent a practice, a certification or a promise like "we never share your data" unless I've confirmed it - Mark anything you had to assume with TO CONFIRM so I can find it - Short sentences, around an eighth-grade reading level Also give me the page layout: an H1, a linked table of contents, H2 sections with anchor links, the last-updated date near the top, and a footer link on every page.
See all