Practical guide

GDPR form backend: 7 checks before you choose

No form service is GDPR compliant on its own. Here is what to check in its DPA and settings, and how the EU-hosted options compare.

The short answer. A form backend cannot make your form GDPR compliant by itself: you are the controller and the service is your processor. Choose one that offers a data processing agreement under Art. 28, says where submissions are stored, lists its sub-processors, lets you set retention and delete data, and is clear about extras such as Telegram or AI that may leave the EU. Then name it in your privacy notice.

FormgongUpdated

GDPR form backend: 7 checks before you choose
GDPR form backend: 7 checks before you choose

Who is responsible: you or the form service?

A contact form collects personal data: a name, an email address, often a phone number. Under the GDPR, you decide why that data is collected, so you are the controller. The form backend stores and forwards the data for you, so it is your processor.

That split matters. Art. 28 requires a contract with every processor, usually called a DPA. It also means the service can help you comply, but it cannot do it for you. You still need a legal basis, a privacy notice and a sensible retention period.

Marketing pages that say “100% GDPR compliant” are a starting point, not an answer. The checks below tell you what is behind the claim.

Seven checks for a GDPR-friendly form backend

  1. A DPA you can accept. Look for an Art. 28 agreement, either signed in the dashboard or included in the terms. No DPA means no lawful basis for the processor relationship.
  2. Where submissions are stored. EU or EEA storage is simplest. Storage in the US can still be lawful: the EU–US Data Privacy Framework has been in force since July 2023, and standard contractual clauses also work. An appeal against the framework is pending at the EU Court of Justice (as of 03.10.2026), so EU storage is the lower-risk option.
  3. A sub-processor list. Hosting, email delivery, captcha and AI providers should be named, with a way to learn about changes.
  4. Retention and deletion. You should be able to set how long submissions are kept, delete single entries and export data for access requests.
  5. Extras that leave the EU. Chat apps such as Telegram or Slack process messages under their own terms, often outside the EEA. So do many AI features and Google reCAPTCHA. Turn them on only if your privacy notice covers them.
  6. Data minimisation. Does the service store raw IP addresses or set tracking cookies in your visitors' browsers? Less collected means less to explain.
  7. Security and breach notice. HTTPS, access control and a promise to tell you about a breach without undue delay are the basics.

EU-hosted options compared

These services say they store submissions in the EU. Facts come from their public pages, checked on 03.10.2026. Prices change, so check before you buy.

  • Formgong (we build it). Submissions in Cloudflare D1 with EU jurisdiction; email through UniOne in the EU, with our own mail server in the EU as the fallback; raw IPs are not stored. A public DPA is part of the terms. Free plan: 250 submissions a month. Telegram delivery is optional and can process data outside the EU, as can some other optional features listed on the data page.
  • Formward. Hosting and database in Sweden, AI by Mistral in France, hashed IPs. The DPA is accepted in the dashboard. Free plan: 100 submissions a month; paid plans from €15 a month.
  • FormPost. Servers at Hetzner in Germany, a DPA you sign in your account, and its own arithmetic question instead of reCAPTCHA. Free plan: one form and ten notification emails a day; Pro costs €17.85 a year including VAT.
  • Forminit (formerly Getform). Based in the UK, with form data in AWS EU regions. Its DPA is accepted with the terms.

US-based services such as Formspree say data may be processed in the United States and other countries. That can be lawful with a DPA and a transfer tool, but it is more paperwork. For a Formspree-focused comparison of EU-hosted options, see EU / GDPR Formspree alternatives. Our form backend comparison covers plans and features side by side.

Where a notification email actually goes

On 8 November 2026 we sent a test submission to a Formgong form and opened the headers of the notification that reached a Gmail inbox. Two Received lines show the route:

Received: by smtp283.emlmind.com (envelope-from <postman…@link.formgong.com>); Sun, 8 Nov 2026 15:41:32 +0000
Received: from smtp308.emlmind.com ([87.246.182.59])
        by mx.google.com with ESMTPS (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256)

The message was sent by UniOne from its EU platform (emlmind.com is UniOne's sending network; this server's address is in Riga, Latvia) and handed straight to Google over TLS 1.2. Gmail recorded spf=pass, dkim=pass for formgong.com and dmarc=pass. It arrived 14 seconds after the form was sent. If UniOne fails, our own mail server at Contabo in France sends instead.

The test also showed something you should know. UniOne routed the links in the email through a click tracker on link.formgong.com and added a 1-pixel open tracker, although our code asks for both to be off. We asked UniOne to switch it off for our account, and they did. In a repeat test on 10 November 2026 every link in the notification pointed straight at formgong.com and the open pixel had no address, so neither opens nor clicks are recorded.

An earlier test on 12 October 2026 went through ZeptoMail's EU servers over TLS 1.3, in 12 seconds. From 26 October to 1 November 2026 notifications left through our own server.

From that point the copy lives wherever the recipient's mailbox provider keeps mail. That part is your choice, not the form backend's: if submissions must stay in the EU, send notifications to an EU-hosted mailbox, or read them in the dashboard only.

What your privacy notice should say

Once you pick a service, your privacy notice needs a few lines about it. Name the form service as a recipient, say where it stores data, and state how long you keep submissions. Mention Telegram, email providers or other optional extras if you use them.

Put a short notice next to the form and link to the full text. A checkbox is not needed just to reply to a message; consent is needed for marketing. Our GDPR contact form guide has a ready notice template and a form with an optional marketing checkbox.

HTML
<form action="https://formgong.com/submit" method="POST">
  <input type="hidden" name="access_key" value="fk_your_access_key">
  <input type="hidden" name="_lang" value="en">
  <label>Email <input type="email" name="email" required autocomplete="email"></label>
  <label>Message <textarea name="message" required></textarea></label>
  <p>We use your details only to reply to you. <a href="/privacy">Privacy notice</a>.</p>
  <div aria-hidden="true" style="position:absolute;inset-inline-start:0;top:0;width:1px;height:1px;overflow:hidden;clip-path:inset(50%)">
    <input type="text" name="botcheck" tabindex="-1" autocomplete="off">
  </div>
  <button type="submit">Send</button>
</form>

Setting up Formgong with GDPR in mind

  1. Create a form on formgong.com. The DPA applies from account creation; read it and the where data lives page.
  2. Set retention in the form settings. Free keeps submissions for 30 days, or deletes them as soon as they are delivered if you pick “Don't keep”. Starter adds 90 and 365 days; Pro can also keep them until you delete them.
  3. Decide on extras. For EU-only processing, use email and keep Telegram and other optional extras off. If you turn them on, add them to your privacy notice.
  4. Ask only for fields you need. Name, email and message are enough for most contact forms.

Plans and limits are on the pricing section.

Frequently asked questions

Is any form backend GDPR compliant on its own?

No. The service is your processor. It can offer a DPA, EU storage and deletion tools, but you still need a legal basis, a privacy notice and a retention period.

Do I need a DPA with a form backend?

Yes. Art. 28 GDPR requires a contract with every processor that handles personal data for you. Many services include it in their terms or let you accept it in the dashboard.

Can I use a US form service under the GDPR?

Yes, if the transfer is covered, for example by the EU–US Data Privacy Framework or standard contractual clauses. An appeal against the framework is pending at the EU Court of Justice, so EU storage carries less risk.

Is sending form leads to Telegram GDPR-friendly?

It can be, but Telegram processes messages under its own terms, often outside the EEA. Mention it in your privacy notice, or use email only if you need EU-only processing.

Does Formgong sign a DPA?

Formgong publishes a standard DPA under Art. 28 that is part of the terms and is accepted when you create an account. No separate signature is needed.

Sources and documentation

Official references for this guide: GDPR (EUR-Lex), EDPB Guidelines 07/2020 on controller and processor, European Commission: EU–US data transfers, Formward, Formward DPA, FormPost, Forminit GDPR, Formspree privacy policy. Formgong DPA, where data is stored.

Rate this guide

Your rating

We read every rating. A comment appears here only after we approve it.

← Back to the blog