legal
Sub-processors
The companies that process form submission data on behalf of Un-static Forms, what each one does, where, and under which transfer safeguard
Last updated: 20 November 2026 (register version 2026-11-20)
Un-static Forms is a service of Newmatter B.V., trading as Un-static. When you collect submissions through our form endpoints, you are the controller of that data and we process it for you. This page lists the suppliers we use to do that, our sub-processors. It is the public register that our Data Processing Agreement refers to.
How to read this register
- Always means the data of every customer reaches the supplier.
- Conditional means the supplier is only involved when the stated feature or event applies.
- A captcha provider is on this list only for forms that use our own captcha key. If you enter your own captcha keys on a form, you contract with that provider yourself and it is your processor, not our sub-processor.
- A captcha provider may also use visitor signals for its own purposes, for example to improve its service. For that use it is an independent controller, not our sub-processor.
- Mailboxes, webhook endpoints and integrations that you configure are destinations you chose. They are not sub-processors.
Changes to this register
We announce the addition or replacement of a sub-processor on this page at least 7 days before it takes effect. Customers who signed a Data Processing Agreement with us also get the notice by e-mail and can object within that period. Every change is recorded in the version history at the bottom of this page.
Hetzner Online GmbH: cloud servers
Industriestr. 25, 91710 Gunzenhausen, Germany
- When: Always.
- Function and data: Hosting of the application, the database, the logs and attachments in transit. Hetzner also hosts the operator server and the internal code and records host we use for support and abuse handling. All submission data passes through or is stored on these servers.
- Processing locations: Germany (Falkenstein: production application and database). Finland (Helsinki: operator server and internal Git host).
- Transfer safeguard: Not required, the data stays in the European Economic Area.
Hetzner Online GmbH and TransIP B.V.: database backups
Gunzenhausen, Germany, and Leiden, the Netherlands
- When: Always.
- Function and data: Encrypted backups of the production database. They hold all submission data that is stored in the database. A backup expires after at most 12 months.
- Processing locations: Germany and the Netherlands.
- Transfer safeguard: Not required, the data stays in the European Economic Area.
Cloudflare, Inc.: R2 object storage
San Francisco, United States
- When: Conditional: forms that accept file uploads (paid plans).
- Function and data: Storage of uploaded files under random keys, read back through our own servers. File contents only; the file name, type and size are stored in our own database. If we preserve an account’s data because of suspected abuse or unlawful use, or for legal claims, its uploaded files stay on R2 while that preservation lasts.
- Processing locations: Storage in the European Union (R2 EU jurisdiction). Cloudflare’s global network may carry the traffic.
- Transfer safeguard: EU-US Data Privacy Framework (Cloudflare, Inc.), with the standard contractual clauses in the Cloudflare data processing agreement as fallback.
AC PM LLC (Postmark): transactional e-mail
Chicago, United States. Postmark is an ActiveCampaign, LLC company.
- When: Always.
- Function and data: Sending notification e-mails (the full submission except the honeypot field, with the names and sizes of attachments and signed download links to forms.un-static.com), auto-responses to the submitter’s address, copies to additional recipients, the reply-to address, and error reports to Un-static. Receiving bounces, complaints and replies to the default reply-to address. Open tracking is switched off.
- Processing locations: United States.
- Transfer safeguard: EU-US Data Privacy Framework (ActiveCampaign, LLC, covering AC PM LLC).
Google Cloud EMEA Limited: reCAPTCHA
Dublin, Ireland, on Google LLC infrastructure
- When: Conditional: forms that use reCAPTCHA with our key (the default captcha).
- Function and data: Bot verification. The visitor’s browser loads the widget from Google on our verification page, and Google collects browser and device signals, the IP address and cookies. Our server sends Google only the verification token. No form content.
- Processing locations: Google’s global infrastructure.
- Transfer safeguard: EU-US Data Privacy Framework (Google LLC) and the Google Cloud data processing addendum.
Cloudflare, Inc.: Turnstile
San Francisco, United States
- When: Conditional: forms that use Turnstile with our key.
- Function and data: Bot verification. Browser signals, IP address, user agent, TLS fingerprint, site key and origin. Our server sends Cloudflare only the verification token. No form content. Cloudflare acts as processor for bot detection, and as independent controller when it uses the signals to improve Turnstile.
- Processing locations: Cloudflare’s global network.
- Transfer safeguard: EU-US Data Privacy Framework (Cloudflare, Inc.) and the standard contractual clauses in the Cloudflare data processing agreement.
Intuition Machines, Inc.: hCaptcha
Miami, United States
- When: Conditional: forms that use hCaptcha with our key.
- Function and data: Bot verification. IP address, browser and device data, interaction signals and cookies. Our server sends hCaptcha only the verification token. No form content.
- Processing locations: United States, and other countries where Intuition Machines or its service providers have facilities.
- Transfer safeguard: EU-US Data Privacy Framework (Intuition Machines, Inc.).
Kickbox, Inc.: e-mail address verification
New York, United States
- When: Conditional: only for a notification address that was suppressed after bounces or complaints. The address is checked by a nightly run before the forms that use it are paused or closed, and when the owner or our staff retry it.
- Function and data: A deliverability check of that single recipient address.
- Processing locations: United States.
- Transfer safeguard: Standard contractual clauses in the Kickbox data processing agreement. Kickbox no longer takes part in the EU-US Data Privacy Framework.
Slack Technologies Limited: internal alerts
Dublin, Ireland (Salesforce group)
- When: Conditional: when a form is activated, reaches a limit, is deleted, has its notification address suppressed or its submissions redelivered, and on application errors.
- Function and data: Internal operations alerts. They carry notification recipient addresses, form titles and success-redirect URLs, and error context that can include an e-mail address. No submission content by design.
- Processing locations: United States.
- Transfer safeguard: EU-US Data Privacy Framework (Salesforce, covering Slack Technologies, LLC).
Proton AG: Un-static mailboxes
Geneva, Switzerland
- When: Conditional: when a submission hits an unhandled error (error reports), and on support e-mail.
- Function and data: Our own mailboxes. They receive support e-mail and automatic error reports, delivered through Postmark, which carry the request of the failing submission: the posted form fields, the IP address, the user agent and the request headers.
- Processing locations: Switzerland.
- Transfer safeguard: Adequacy decision for Switzerland.
HelpSpace GmbH: support desk
Bad Vilbel, Germany
- When: Conditional: when you or we handle a request through support.
- Function and data: Support tickets for [email protected], including instructions you give us, requests of people who submitted a form, and any submission data or addresses quoted in a ticket.
- Processing locations: European Union (as stated by HelpSpace).
- Transfer safeguard: Not required: HelpSpace states that it hosts all data in data centres in the European Union.
Anthropic Ireland, Limited: AI operations assistance
Dublin, Ireland, on Anthropic PBC infrastructure
- When: Always, for the purposes stated here.
- Function and data: AI models that our operators use, under our instruction and supervision, to investigate abuse and spam, handle support and deletion requests, and diagnose delivery faults. They read submission content, submitter IP addresses and referrers, recipient addresses and support tickets as far as the task needs it. Inputs are not used to train models.
- Processing locations: Processing in the United States, Europe, Asia and Australia. Storage in the United States.
- Transfer safeguard: Standard contractual clauses in the Anthropic data processing addendum (Commercial Terms).
Planned: OOPSpam LLC, spam scoring
Minneapolis, United States
- When: Not active. OOPSpam will only process data after the notice described under “Changes to this register”.
- Function and data: The submission text and the submitter’s IP address and e-mail address, to return a spam score. OOPSpam does not store them by default. The submission text, without IP address or e-mail address, may go to OpenRouter, Inc. (United States) for contextual detection.
- Processing locations: Germany (Frankfurt) normally, with fallback to the United Kingdom, the United States, Brazil or Australia, through Cloudflare.
- Transfer safeguard: Standard contractual clauses in the OOPSpam data processing agreement.
Not on this register
Our payment provider is the merchant of record for our own billing and does not process form submission data. The same goes for our DNS and build providers and the statistics of this website. Our privacy policy describes how we handle your account and billing data, and Where your data lives gives the short version of this register.
Version history
| Version | Change |
|---|---|
| 2026-11-20 | First published version. |
Questions about this register can go to [email protected] or through our contact page.