Data residency
How EU data residency and regional processing requirements work for customer rollouts.
- Last reviewed
Data residency
Use this page when your team needs to launch getuserfeedback.com with an EU data residency requirement or another regional processing requirement.
GDPR support and EU data residency are related, but they are not the same commitment. We support privacy-rights requests and consent-aware widget configuration separately from any promise that all data stays in one region.
What we support today
If your team needs EU data residency, tell us before production rollout. We can review the requirement with you and confirm what is covered for your workspace.
Email hello@getuserfeedback.com with your workspace name, expected launch timeline, and the data categories that must stay regional.
Before you send production respondent or workspace data, we should agree on:
- the workspace or account covered by the requirement
- the data categories that must stay regional
- whether backups, exports, support access, and operational copies are included
- whether subprocessors, email, telemetry, analytics, or AI-assisted workflows need special handling
- whether your data processing agreement or procurement review needs extra language
Do not assume EU-only processing is enabled by default. Treat residency as a rollout requirement to confirm with us first.
What residency usually covers
For product data, an EU residency commitment usually starts with:
| Area | Expected coverage |
|---|---|
| Workspace data | Organization, account, flow, and configuration data needed to run the workspace. |
| Respondent data | Survey, form, widget, identity, and response data submitted through customer flows. |
| Operational copies | Backups, database branches, exports, and support copies created for the covered workspace. |
| Fulfillment workflows | Privacy-rights export, deletion, correction, and restriction work for covered data. |
Supporting systems can be different. Email delivery, customer support tools, telemetry, security logs, analytics, subprocessors, and AI-assisted workflows may need separate review before they can be included in the same regional commitment.
Before you launch
Send us the details your team already knows:
- the region requirement, such as EU data residency or EU-only processing
- whether the requirement applies to all product data or only respondent data
- whether support access, logs, email delivery, analytics, AI-assisted workflows, or subprocessors must also stay in the region
- any procurement deadline or DPA language you need us to review
If your request is about access, deletion, correction, portability, objection, restriction, or consent withdrawal, see Privacy rights and requests.
If your request is about cookie banners, consent mode, or non-essential widget storage, see Compliance & consent.