Privacy policy — editable structure
Use this page as a compliance content checklist, then replace it with an accurate policy drafted for the service actually offered.
01. Who operates this website?
Identify the legal entity, trading name, country, registration details, and a verified privacy contact. Replace all example identifiers before publishing.
02. What information is collected?
Describe contact-form details, order/customer records, account data, project files, technical logs and cookies actually used by your deployed website.
03. Why is information processed?
List service delivery, customer support, billing, fraud prevention, analytics and marketing purposes, with a valid lawful basis where applicable.
04. Payment information
Identify your actual payment processor; explain that payment card data should be handled by that provider, not stored in static HTML or client-side scripts.
05. AI and uploaded content
Explain whether user prompts or uploaded content reach external AI models and what retention or training controls apply. Do not make promises without verifying the provider terms.
06. Cookies and analytics
List the essential, preference, measurement and marketing technologies you really deploy, and any consent controls required in your market.
07. Sharing and international transfers
Name categories of vendors, hosting regions, subcontractors and relevant cross-border transfer safeguards.
08. Retention and deletion
State real retention periods or objective criteria for contact messages, account records, invoices and backups; document secure deletion processes.
09. Your rights and choices
Explain the rights applicable to your jurisdiction: access, correction, deletion, objection, portability and withdrawing consent; include working request channels.
10. Security and age limitations
Summarize safeguards that are genuinely implemented, incident contact channels and any restrictions on services for children.
11. Policy updates and contact
Provide a real effective date, a revision process, the legal contact and the regulator route if legally required.