A contact-form privacy review that follows every copy of an enquiry
Share
Published
A contact-form privacy review should trace each field from collection to deletion. Keep the fields needed to handle the enquiry, explain their use and check every place the submission is copied, including inboxes, plugins, exports and connected customer systems.
A website can ask for a phone number because an old template included one. It can then email the submission to three people, store it in WordPress and copy it into a marketing list. Removing a field from the page only addresses the first part of that workflow.
For Nigerian SMEs, this is a manageable place to start a wider data review. Choose one live form and follow a fictional submission through the business. You do not need to begin by cataloguing every database the company has ever used.
Give each field a job
Write the form’s immediate purpose in one sentence: for example, to answer requests for a product demonstration. Then ask which information is necessary to do that. An email address may be sufficient for a reply. A delivery address may become relevant later if a purchase involves physical goods.
The NDPC’s published privacy policy describes a principle of limiting personal information to the minimum necessary for its purpose. The UK’s ICO similarly explains data minimisation as collecting enough relevant information without collecting more than the purpose requires. The practical review below applies that idea to form design; it does not replace an assessment of your legal obligations.
| Field | Question for the owner | Possible decision |
|---|---|---|
| Email address | How will we reply? | Required if email is the reply channel |
| Phone number | Is a call needed for this enquiry? | Optional callback field, or remove |
| Home address | Do we deliver anything at this stage? | Collect later when justified |
| Identity document upload | Why is identity evidence necessary here? | Remove from a general enquiry form unless a specific need is established |
| Open message box | Could people send sensitive information unnecessarily? | Add clear guidance and a safer route for sensitive cases |
Follow a test submission
Use an invented name and a clearly labelled test address you control. Do not test by submitting a customer’s real identification document. Record where the submission appears and which accounts can read it.
Check the form plugin’s entry store, notification inbox, email delivery service, CRM integration and automation history. Ask whether failed submissions or delivery errors retain the text elsewhere. A developer may need to help identify logs and integrations that the front-desk team cannot see.
Map the result in a small register: system, purpose, authorised users, owner, retention decision and deletion route. Our customer-data register example shows how to document one process without creating an unmanageable spreadsheet.
Separate the reply from unrelated marketing
Someone asking about a service needs a response to that enquiry. That does not establish permission for every future campaign or for disclosure to an event sponsor. Decide which lawful basis applies to each use, explain it clearly and configure the form to match.
If you rely on consent for an optional marketing use, provide a distinct choice and an effective way to withdraw it. Avoid a required checkbox that bundles several unrelated activities into one sentence. Test what happens when a person declines the optional use: the ordinary enquiry should still follow the intended service process.
The same separation matters for event registrations. Our webinar registration privacy checklist covers attendance records, recordings and sponsor follow-up as separate decisions.
Make the handover usable
Consider a fictional repairs business. Its form asks for a name, email, phone number, address and a photograph of the device. Staff only need the device type and fault description to offer an initial appointment. The revised form postpones the address until collection is arranged and explains when a photograph would help.
The owner also finds that notifications go to a former contractor. They remove that recipient through the authorised administration process and check whether the contractor still has access to the stored entries. The improvement comes from reviewing the whole route, rather than shortening the form alone.
If an enquiry later turns into a physical delivery, use a controlled handover of customer details to the courier. There is rarely a reason to forward the complete original enquiry thread with every attachment.
Set a review and deletion routine
Decide when an unanswered, resolved or abandoned enquiry should be reviewed. Base retention on the business purpose and applicable requirements; there is no single period suitable for every contact form. Document exceptions rather than keeping all entries indefinitely.
Test deletion with the fictional record. Check the plugin entry, notification emails and connected systems. Record any backup limitations and make sure a future restore will not quietly return closed enquiries to active work queues.
Common questions
Does adding a privacy-policy link complete the review?
No. The notice needs to describe the actual processing, and the form, recipients, integrations and retention settings need to follow that description.
Can a phone number be optional?
Yes, where the purpose supports that design. Explain when it will be used and avoid making it functionally mandatory through an error message or follow-up workflow.
Who should own the form?
Name a business owner who understands why the information is collected, supported by the website administrator and privacy lead. Ownership should continue after the page is launched.
Featured image: AI-generated conceptual illustration.
