Skip to content
Technical7 min read

How do I write a privacy policy and comply with data-protection law like PDPL?

What a privacy policy should say, when you need consent, and how Saudi PDPL, GDPR, KVKK and India's DPDP Act differ. General info, not legal advice.

The moment your site has a contact form, analytics, a newsletter or a checkout, you process personal data. Most modern laws then expect you to tell people clearly what happens to it. A copied policy that does not match what your site does can be worse than none.

This is general information, not legal advice. For the final text, especially for shops, health, finance or children, ask a qualified lawyer in your country. The laws below are a map, not a verdict.

A privacy policy must honestly say what personal data you collect, why, who receives it, how long you keep it and how people can exercise their rights. Match it to your real practice and to the law of the countries your visitors live in.

What every policy needs

Whatever the country, the same building blocks recur:

  • Who you are and how to contact you about privacy.
  • Which data you collect: forms, payments, cookies, analytics, logs.
  • Why you use it and on what basis, such as consent or a contract.
  • Who receives it: payment processors, email tools, hosting, analytics providers.
  • How long you keep it, where it is stored, and how people can access, correct or delete it.

Saudi Arabia: PDPL and SDAIA

The Personal Data Protection Law (PDPL) is overseen by SDAIA and is built around transparency, a defined purpose, data minimisation and the rights of the individual. In practice that means a clear privacy notice, collecting only what you need, honouring access and deletion requests, and care when transferring data outside the Kingdom. Check the current implementing regulations, because details on transfers and registration have been updated over time.

Other markets in one view

If you serve visitors elsewhere, their law may apply to you too. The following are rough pointers only:

  • EU (GDPR): needs a legal basis, rights of access and erasure, and prior consent for non-essential cookies; France adds CNIL guidance and Germany requires an Impressum.
  • Turkey (KVKK): an information notice, explicit consent for some processing, and the VERBIS registry for certain controllers.
  • India (DPDP Act 2023): consent-based processing with notice, plus rights and duties that are phased in by rules.
  • Pakistan and Bangladesh: no broad law applied across the board today, but good practice is the same and rules are evolving, so keep your policy honest and current.

Cookies and analytics

Essential cookies usually need no consent; analytics and advertising often do under European-style rules. If you use them, show a clear choice, do not load those scripts before the visitor agrees, and describe each tool in the policy.

Drafting it with Uttra

You can ask Uttra to add a privacy page and a footer link, then edit the wording by chat. A prompt:

"Add a privacy policy page in Arabic and English, linked from the footer and from the contact form. List the data we collect: name, email and message from the form, and anonymous analytics. Add a contact address for privacy requests and a note that it is a draft for legal review."

Have a professional review it, and update it whenever you add a new tool that touches visitor data.

Common questions

Yes, in most places. A form collects names and emails, so you should explain what you do with them and how to reach you.

It is risky. It may describe tools and practices you do not have, and it can carry copyright. Use it only as a checklist and write your own.

No. Compliance depends on how you collect and use data and on your legal texts. A builder can help you create the pages, but responsibility stays with you.

Try it on your own project

Describe what you want in your own words and watch your site or system get built — then change it by chatting.

Start free