Submissions and files are stored in Germany.
Formspring stores core submissions and uploaded files in Germany, encrypted in transit and at rest, with sensitive fields encrypted on top. This is the default for every customer on every plan, not a paid add-on. Sending email, delivering push notifications, optional AI features and the integrations you connect may involve processing in other countries. Where something does leave the EU, it is named with its region on the sub-processors page rather than glossed over here.
Two routine paths leave the EU, and we’d rather say so here. The email that notifies you of a submission is sent through a provider outside the EU/EEA, under Standard Contractual Clauses. Push notifications to the mobile app go through a provider in the United States and can include a short preview of the submission.
- Data residency
- Core storage in Germany
- Encryption
- TLS 1.2+ in transit, AES-256 at rest
- Sensitive fields
- Encrypted again with a per-workspace key
- Signed downloads
- File links expire after 15 minutes
What happens to one submission
Four steps, from the visitor’s browser to encrypted storage. Pick a step to see what is checked there.
Visitor submits
A respondent sends a form, survey, or funnel response from their browser or via the API.
Browser submissions are checked against the form’s allowed origins. Up to 5 files of 10 MB each per submission.
Controls you set per form
Spam never triggers notifications or webhooks. A screening step that can’t reach its provider releases the submission rather than swallowing it.
- Allowed origins
- Per-form allow list rejects browser submissions from unexpected domains at the edge.
- BYO captcha & spam keys
- hCaptcha and Akismet keys are stored encrypted and never proxied through a shared key.
- Retention windows
- Configure how long submissions are retained per form; expired submissions are purged with their attachments.
- AI moderation toggle
- Optional content classification with full opt-out and audit logging.
- Webhook signing secrets
- Rotate per-webhook secrets without dropping deliveries. Receivers verify in constant time.
- Scoped API tokens
- Personal-access tokens with explicit abilities; team-plan role-based access on top.
Who else touches the data
Described by role. The sub-processors page names each vendor for your Article 28 review.
Sub-processors by name| Role | What it does | Region |
|---|---|---|
| Application hosting & object storage | Runs the application and stores submissions and uploaded files | EU (Germany) |
| Transactional email delivery | Sends submission notifications, autoresponders, and account email | Outside the EU/EEA (Standard Contractual Clauses) |
| Payment processing | Subscription billing and invoicing | EU (Ireland) |
| Spam content scoring optional | Optional submission spam classification; bring-your-own key supported | US (Standard Contractual Clauses) |
| Bot challenge optional | Optional captcha challenge on public forms, with the keys you supply for the form | US (Standard Contractual Clauses) |
| SMS delivery optional | Sends the SMS automation step and link-in-bio signup confirmations | US (Standard Contractual Clauses) |
| Mobile push notifications optional | Delivers push notifications to the mobile app for people who install it; a notification can include the form name and a short preview of the submission | US (Standard Contractual Clauses) |
| Custom-domain edge TLS optional | Terminates TLS and proxies traffic for a custom domain you configure yourself | Global anycast; the serving location follows the visitor |
| AI moderation & summaries optional | Optional AI moderation, summaries, and autoresponder drafts on paid plans; off unless the feature is switched on | US (Standard Contractual Clauses) |
| Calendar and meeting tools you connect optional | Reads availability and writes booking events to your calendar, and adds a meeting link, when you connect your own account | Set by the service you choose |
| Services you connect optional | Receives the submission data you map to a CRM, spreadsheet, chat tool, or webhook that you connect | Set by the service you choose |
Where each kind of data goes
Submissions and files are stored in Germany. Email, push notifications, AI features and the services you connect may process data elsewhere, as listed here.
| Data | Provider category | Purpose | Region | What you control |
|---|---|---|---|---|
| Submissions and uploaded files | Application hosting & object storage | Stored so you can read, export and act on them | EU (Germany) | Always on. Set retention per form, export at any time, delete on demand |
| Short-link click details (approximate location, device, referring site, a one-way hash of the IP address) | Application hosting & object storage | Link analytics. The IP address itself is not stored | EU (Germany) | Delete the link or the workspace. Your plan sets how far back you can view them |
| Notification and autoresponder email, which can contain submission content | Transactional email delivery | Delivering the email you set up | Outside the EU/EEA (Standard Contractual Clauses) | You choose who is notified and whether a form sends an autoresponder |
| Push notification text: the form name and a short preview of the submission | Mobile push notifications (optional) | Alerting you on your phone | US (Standard Contractual Clauses) | Optional. Only if you use the mobile app and switch its notifications on |
| Submission content sent to AI features | AI moderation & summaries (optional) | Moderation, summaries and drafted replies | US (Standard Contractual Clauses) | Off unless you switch the feature on, on paid plans |
| Submission content sent for spam scoring | Spam content scoring (optional) | Spam classification | US (Standard Contractual Clauses) | Optional per form, with your own key |
| Visitor details sent for the bot challenge | Bot challenge (optional) | Telling people from bots | US (Standard Contractual Clauses) | Optional per form, with the keys you supply |
| Phone numbers and message text | SMS delivery (optional) | Sending SMS from an automation or a link-in-bio signup | US (Standard Contractual Clauses) | Optional. Used only when you add the step or block |
| Billing details and payment data | Payment processing | Charging for your plan and issuing invoices | EU (Ireland) | Needed only for a paid plan. The Free plan asks for no card |
| Booking details and your calendar events | Calendar and meeting tools you connect (optional) | Reading your availability and writing booked events | Set by the service you choose | Only after you connect your own account. Disconnect at any time |
| The submission fields you map to a connected service | Services you connect (optional) | Sending data to the CRM, sheet, chat tool or webhook you chose | Set by the service you choose | You pick the service and the fields. Remove the connection to stop it |
| Traffic for a custom domain | Custom-domain edge TLS (optional) | Terminating TLS for a domain you configure | Global anycast; the serving location follows the visitor | Only if you set up a custom domain |
Vendors are named on the sub-processors page. Sub-processors by name
How long we keep submissions
| Plan | Retention |
|---|---|
| Free | 30 days, automatic purge |
| Pro | Until manually deleted; per-form override available |
| Team | Until manually deleted; per-form override |
| Scale | Custom retention policy with per-team controls |
Found a vulnerability?
Coordinated disclosure, please. We credit reporters who ask to be credited.
Email security@pixelandprocess.de- In scope
- Production endpoints under formspring.io and ingestion under f.formspring.io
- Out of scope
- Third-party integrations and webhook receivers you control
- Acknowledged
- Within 2 business days
- Triage and timeline
- Within 5 business days
