Privacy policy

Your privacy policy tells people how you handle their personal data. Privacyboard assembles it from your company profile, processing activities, vendors and security practices, so each section describes your situation and not an average one.

#What it contains

• Who is responsible. Your company identity and privacy contact.
• What you do with data and why. The purposes and legal basis of each activity from your processing register.
• What data and whose. The categories of data and of people concerned.
• Who receives it. Your vendors appear as recipients.
• Transfers outside the EEA. If a vendor processes data outside the EEA, the policy asks how the transfer is protected.
• How long data is kept. From your retention answers and activities.
• Security practices. Only the practices you answered.
• People's rights and how to use them. And their right to complain to an authority.
• Cookies. Written from your live cookie banner, once it is published, so the two cannot disagree.
• Automated decisions. If you take decisions based only on automated processing, three short questions describe the decision, its logic and its effect.

#What the GDPR asks for

Article 12 asks for concise, intelligible and easily accessible information in plain language. Articles 13 and 14 list what must be said: who you are, the purposes and legal basis, the recipients, transfers, retention and people's rights. Article 22 adds information about the logic of automated decisions with significant effects. This is a summary, not legal advice.

#Keeping it current

When you add a vendor, change an activity or update a practice, a validated policy is marked as changed since validation. You read the update, correct it if needed and validate again, so the approved version always matches what you do.

#Publishing

A validated policy can be downloaded as a PDF or shown in your privacy center. A draft is never public.

#FAQ

#Is a privacy policy mandatory under the GDPR?

If you process personal data of people in the EU, you must give them the information listed in Articles 13 and 14. A privacy policy that is easy to find, for example linked from your website footer and sign-up forms, is the usual way to do it.

#Is the policy generated by AI?

No. It is assembled from your answers and the vendor information in your workspace with fixed, reviewed text.

#Does Privacyboard make me compliant?

No tool can. It helps you state accurately what you do. Whether your practices comply remains your responsibility. See Scope and limits.

#Can I add my own text?

Yes. You can edit the draft before validating it.