Personal data on a site: forms, access and technical measures

A landing form looks harmless until the leads sit in a shared mailbox, a spreadsheet and with the contractor who built the site three years ago. That is already personal data processing. This note does not replace a lawyer: it is about what usually drifts between "a policy in the footer" and the real admin panel. The reference point is the data protection law of your country (GDPR in the EU), not the mood of marketing.

What to tidy around the form

• The purpose sits next to the button, not inside an offer ten screens long.
• The policy says who the operator is, which fields, how long you keep them and how a person can withdraw consent.
• A role sees the leads, not the whole company. A contractor needs access for the job, not forever.
• No more fields than the next call needs. An extra date of birth "just in case" is an extra plane.

Technical measures without which the text is empty

HTTPS, tighter admin rights, care with third-party scripts and with where the form actually sends data. An ad pixel that can see the lead contents often surprises people more than a missing paragraph in the policy. A cookie banner does not replace that review.

A good pass combines texts and engineering: the policy, form fixes and a site audit. Lexora does this together with development, so consent does not live apart from the code that collects it.