A privacy policy for a site with a form: what the GDPR requires
If the form on your site asks for a name and a phone number, Article 13 of the GDPR requires you to tell the person, at that same moment, who will get their data, what for and for how long. One page answering six questions and a link to it under the form are enough; with the company's facts to hand, it is an hour's work. Without it, the form is like a stranger in the street who asks for your number and says nothing when you ask "and who are you?"
Almost nobody reads the policy. Whether there is one gets checked by someone who is unsure about leaving their number, and sometimes by a partner or supplier sizing up how carefully you work. For them, a link under the form says "somebody has thought about your number" before anyone opens it.
54.7% of sites had no policy that could be found
In my check, 15,095 of 27,591 Latvian company websites (54.7%) had no privacy policy that could be found. The share is lowest in trade (37.1%) and highest among sports and leisure sites and non-governmental organisations (about 65%). Shops meet the question first: they have a form at every step.
What the GDPR tells you to say to the person
When you get data from the person themselves (a form, an enquiry, a newsletter sign-up), Article 13 of the GDPR requires you to tell them who is collecting the data and how to contact them (paragraph 1), what the data is for and on what legal basis, who else may receive it (same paragraph), how long it is kept, what rights the person has and where to complain (paragraph 2). Article 12(1) adds: concisely, clearly and in plain language (the regulation's words: "concise, transparent, intelligible", "plain language"). The regulation doesn't require a page called "Privacy policy". It speaks of information, and where and how to give it is up to the company. So "not found" doesn't yet mean "no information".
This is not a legal opinion. Whether your text is enough for your form is for a lawyer or the supervisory authority to say; in Latvia that is the Data State Inspectorate (Datu valsts inspekcija).
What to do
- Write a page that answers six questions. Who you are (name, registration number, address, email); what you need the data for (to answer the enquiry) and on what legal basis; who else will receive it, if anyone; how long you keep it; what rights the person has (to see it, correct it, delete it); where they can complain. Those are the main points of Article 13. On an ordinary site with a contact form, I'd estimate such a page fits on one screen.
- WordPress: designate the page as your policy. Settings → Privacy: pick an existing page or click "Create new page". WordPress opens a draft with hints about which sections you need. It isn't a finished policy: you fill in the blanks with your own facts. In site builders, look for "Privacy policy" in the site settings, or just create an ordinary page.
- Put the link where the person enters their data. Article 13 speaks of the moment the data is obtained, and that's the form. Put the link under the "Send" button, not only in the footer; in the footer too, for those who go looking for it. In WordPress with a block theme the footer is edited in Appearance → Editor → Patterns → All template parts → Footer, with a classic theme in Appearance → Customize.
- Add a consent line to the form. "I have read the privacy policy", linking to the page; in most form plugins this is a checkbox field marked "required". That is the answer to "and who are you?" at the moment the person hands over their number.
- Send one sentence to whoever runs the site. "Create a policy page, designate it in the privacy settings, put a link to it under every form and in the footer, and add a required 'I have read the policy' checkbox to the forms." If the site also sets cookies before consent, that's separate work; I wrote a separate article about cookie banners.
Go through your policy against the six questions and tick the ones it already answers:
Twice a year, open your form as a visitor and check that the link under it leads to a live page and not to a "404".
What it buys you
The form stops being a stranger who asks for a number and says nothing. Whether it brings more enquiries nobody can say in advance; you can check by comparing their number in the month before the change and the month after. The other side: Article 13 is an obligation, not a recommendation, and a page with the answers is the cheapest way to meet it. How fully it meets it is, I repeat, for a lawyer to decide. Everything else a customer sees in the first minute can be checked in five minutes.
How I counted
In September 2026, of the 27,591 sites that responded, my tool found no link to a privacy policy on the home page of 15,095. "Not found" means only that: the policy could be elsewhere or under another name. I did not read the texts, so the numbers do not say whether a policy meets the regulation. The sector breakdown uses the ten largest sectors (23,532 sites) and leaves out 1,565 sites with unrecognised activity and four smaller groups, so the reference line (all sites) and the bars are not directly comparable. More: how I checked 27,591 websites.
Sources
- GDPR (Regulation 2016/679): Article 12(1), Article 13.
- Settings Privacy screen in the WordPress documentation: how to designate or create a policy page; the draft contains hints, but the owner has to fill it in.
- My own check, September 2026.
If you'd like me to look at your form and the text next to it and tell you what is missing from the Article 13 list, write to me.
This article is for information only and is not legal advice. For your own situation, ask a lawyer or your data protection authority.