All resources
Concepts & fundamentals

GDPR and Your Contact Form: What You Owe, and What “Delete It” Actually Reaches

You are the controller of your contact form data; your form backend is the processor. That decides who answers a deletion request, whether you need a consent checkbox, and why deleting a submission usually leaves three copies behind.

The ShipMyForm team

· 9 min read

You are the controller of your contact form data and your form backend is the processor. That one split decides everything else: deletion requests come to you, a consent checkbox is probably the wrong tool, and the moment you forward submissions to Slack or a spreadsheet, deleting the original stops being the same thing as deleting the data.

Full disclosure: ShipMyForm is our product, and it is a processor for the submissions our customers collect. Where we name our own defaults below it is as a worked example, not a recommendation to buy. This is a practical guide from the processor's side of the table, not legal advice — for an actual compliance position, talk to someone qualified in your jurisdiction.

The split that decides everything

GDPR gives two roles to anyone handling personal data, and almost every confusing question about forms resolves once you work out which one you are in.

  • The controller decides what is collected and why. That is you. You chose to put a form on your site, chose the fields, and decided what you would do with the answers.
  • The processor handles that data on the controller's instructions and for no purpose of its own. That is your form backend, your email provider, and every connector you forward submissions to.

The consequence people miss: a visitor's rights are exercised against you. If somebody who filled in your contact form asks to see or delete what you hold, that request lands with you. You cannot forward it to your form backend and consider it handled, any more than you could forward it to your email provider. Your processor's job is to give you the means to act — not to act in your place.

This is also why a data processing agreement matters. Article 28 requires one between controller and processor, and it is where the processor commits to only act on your instructions, to keep the data secure, and to tell you about sub-processors. If a form backend cannot produce one, you have a gap you cannot close by yourself.

This is the single most common thing people add, and in most cases it is both unnecessary and counterproductive.

Consent is one of six lawful bases, not the default one. For a contact form the relevant question is: what is the person actually asking for? They typed a message asking you to reply. Processing their name and email to reply to them is the thing they just requested. That is normally legitimate interest, and sometimes steps taken at the request of the data subject prior to entering a contract.

So a checkbox reading "I consent to my data being processed" adds a field, costs you completions, and does not make you more compliant. Worse, consent must be freely given and as easy to withdraw as to give — if you make it a condition of sending the form, it is not freely given, and you have built something weaker than the basis you already had.

The line that actually matters:

Consent is for what they did not ask for. If you want to add a form submitter to a newsletter, that is a separate, specific, unticked checkbox — and the form still has to work if they leave it alone.

What you do owe them is transparency: say who you are, what you are collecting, why, how long you will keep it, and who else sees it. A short privacy line under the submit button with a link to your privacy notice does more for compliance than any checkbox.

The four things you have to be able to do

Strip away the vocabulary and a contact form puts four operational requirements on you.

  1. Tell them. Articles 13 and 14 — at the point of collection, in plain language.
  2. Limit how long you keep it. Storage limitation. No fixed number is specified; you pick a period you can justify and stick to it.
  3. Act on a request. Access, correction, deletion, portability, objection — within one month under GDPR, or 45 days where US state laws apply.
  4. Not surprise them with where it goes. If submissions are forwarded to a third-party tool or another country, that belongs in your notice.

Numbers two and three are where most small sites quietly fail, and they fail in the same way: not through bad intent but because nothing automatic enforces them. A retention policy in a privacy notice that no system implements is a written promise your database is breaking.

What “delete it” actually has to reach

Here is the part that general GDPR advice skips, and it is the one that bites hardest for form owners.

A form submission is rarely stored in one place. A typical setup looks like this:

Where a copy livesWho can delete itDeleted when you delete the submission?
Form backend databaseYour form backendYes
Uploaded files in object storageYour form backendOnly if it cleans up blobs, not just rows
Notification email in your inboxYouNo
Slack or Discord messageYouNo
Google Sheets row, Notion page, CRM recordYouNo
Your backend's database backupsYour form backendNot immediately

Pressing delete in a form backend removes the first row of that table. It cannot touch the rest, and no vendor can honestly claim otherwise — nobody can reach into your Slack workspace and retract a message.

That is not a reason to avoid connectors. It is a reason to decide, before you wire one up, who deletes each copy and how. Two practical moves make this manageable:

  • Forward less. A notification that says "new enquiry from Jane, open it here" leaks far less into your inbox than one that pastes the whole message body. Some backends, ours included, let you send a notification without the submission content.
  • Prefer one durable copy. If the form backend is the system of record and everything else is a pointer to it, a deletion request has one target rather than five.

The awkward corner is backups. Erasure extends to them, but nobody rebuilds a backup to remove one row. The accepted practice is that deleted data persists in backups until they rotate out, and your notice should say so with an actual period. If a vendor's privacy policy is silent on backups, that is not the same as them not having any.

Deleting an account, as a worked example

Deleting one submission is the easy half. Deleting a whole account is where the edge cases live, and they are worth seeing because they are the same edge cases in any multi-user tool.

We shipped self-serve account deletion this month, and the design decisions were almost entirely about what survives:

  • Confirmation is a code by email, not a checkbox. An irreversible action triggered by a single click in a hijacked session is a bad trade.
  • A short, cancellable window. We use 24 hours. GDPR's one month and CCPA's 45 days are both ceilings, not floors — nothing requires a grace period at all, and shorter is the safer direction. What it buys you is a chance to undo a decision made in anger; what it costs is some protection against a takeover.
  • A shared workspace is not deleted. If you are the only member, it goes with you. If colleagues remain, ownership passes to the longest-standing one and you are simply removed. Erasing one person's account must not erase other people's data — and refusing the erasure because a colleague exists is not an option either.
  • Some things are deliberately kept. We keep the email address on a suppression list, because that record is what stops us ever emailing you again. Removing it would mean resuming mail to someone who asked us to stop. That is a legitimate-interest retention, and the right move is to say so in the privacy notice rather than do it quietly.
  • Deletion does not cancel billing. Our payment providers are merchants of record, so a subscription outlives the account row and we cannot cancel it on your behalf. Saying that loudly beats letting someone discover it on their next statement.

None of that is special to us. If you are evaluating a form backend, these are exactly the questions whose answers reveal whether erasure was built or improvised.

Retention defaults are a compliance decision

A form backend's default retention is not a feature-list number, it is the storage-limitation choice it made on your behalf until you change it.

It is worth knowing what yours is, and worth noticing which direction a vendor's defaults lean. "Forever" is the friendliest-sounding default and the hardest to defend under storage limitation. A finite default that you can shorten is the easier position, and the useful question is whether you can shorten it — and whether a shortened window is actually enforced by something that runs, or just recorded as a preference.

For reference, ShipMyForm keeps submissions for 180 days on the free plan and a year on Starter, with Business keeping them until you say otherwise, and any plan can set a shorter window that a sweeper enforces. Figures are our own as of 10 November 2026; check any vendor's current pricing and policy pages before relying on them.

The related decision is IP addresses. An IP is personal data, and you almost certainly want something IP-shaped for rate limiting and spam defence. Storing a salted hash rather than the address — with the salt rotating, so old hashes stop being linkable — keeps the anti-abuse signal and drops the identifier. It is a materially easier thing to justify than raw addresses kept indefinitely.

What to ask a form backend

Five questions. The answers separate vendors who have thought about this from vendors who have a compliance page.

  1. Will you sign a DPA? Article 28 requires it. A "no" or a long silence is disqualifying.
  2. Where is the data, and who are your sub-processors? You have to disclose onward transfers, which means you have to know them.
  3. What is the default retention, can I shorten it, and what enforces it? A setting that nothing acts on is not retention.
  4. Can I delete a single submission, including its uploaded files? Row deletion that orphans files in object storage is a half-deletion.
  5. Can I delete my entire account myself? If the answer is "email support", erasure has not been built — and a right that depends on somebody reading their inbox is a right with an SLA you did not agree to.
Verify before you commit:

Retention periods, sub-processor lists and deletion behaviour change. Every figure here was read from our own system on 10 November 2026. For any vendor including us, check the current privacy policy and DPA rather than a blog post — including this one.

The short version

You are the controller; your form backend is the processor; requests come to you. Skip the consent checkbox on an enquiry form and write a clear privacy line instead. Pick a retention period something actually enforces. And before you forward submissions anywhere, count the copies you are creating, because you are the one who has to delete them all.

If you want to see how this looks in a product, our privacy policy states the retention defaults, the deletion window and what we deliberately keep. If you are earlier than that and still working out what a form backend even is, start with what is a form backend.

Frequently asked questions

Do I need a consent checkbox on my contact form under GDPR?
Usually not. Consent is one of six lawful bases, and it is the wrong one for an enquiry form. When somebody fills in your contact form asking you to get back to them, you are processing their data to do the thing they just asked for — that is legitimate interest, or arguably contract. A checkbox that says “I agree to my data being processed” adds friction and is not what makes you compliant. You do need consent, separately and unticked, if you also want to add them to a marketing list. The rule of thumb: consent is for what they did not ask for.
Who is responsible for GDPR when I use a form backend — me or them?
You are the controller and they are the processor. You decide what data is collected and why; they handle it on your instructions. The practical consequence is that a visitor's access or deletion request goes to you, not to your form backend, and you are expected to be able to act on it. A processor's job is to make that possible, to not use the data for its own purposes, and to have a data processing agreement with you. If a vendor cannot produce a DPA, that is your problem as well as theirs.
How long can I keep contact form submissions under GDPR?
There is no fixed number in the regulation. The requirement is storage limitation: keep it no longer than you need it for the purpose you collected it for, and be able to say what that period is. For a one-off enquiry that is usually months, not years. The practical move is to pick a period you can defend, write it in your privacy notice, and then actually enforce it automatically — an unenforced retention policy is worse than a short one, because you have written down a promise your database is not keeping.
If I delete a form submission, is the data really gone?
Usually not, and this is the part most guidance skips. The moment you forward submissions to email, Slack, Google Sheets, Notion or a CRM, each of those holds its own independent copy. Deleting the submission in your form backend deletes one of them. Nobody can reach into your Slack workspace and remove the rest. Before you wire up a connector, decide who is responsible for deleting each copy — because under GDPR that responsibility is yours, not the form backend's.
What should I ask a form backend about GDPR compliance?
Five things. Will you sign a data processing agreement? Where is the data stored and which sub-processors touch it? Can I set a retention period that is actually enforced, and what is the default? Can I delete a single submission, including any uploaded files, on request? And can I delete my whole account myself, without emailing support? A vendor that answers the last one with “contact us” has not built erasure, it has built a support queue.
Do I need to hash or avoid storing IP addresses from my form?
An IP address is personal data under GDPR, so if you store it you have to justify and disclose it. You generally do want something IP-shaped for spam defence and rate limiting, which is a legitimate interest. The middle path is to store a salted hash rather than the address itself, with the salt rotating so the hash stops being linkable after a period. That keeps the anti-abuse signal and drops the identifier, which is a much easier position to defend than keeping raw addresses indefinitely.

Related guides