Last updated: June 30, 2026
This page explains how to request data processing, subprocessor, and transfer review for getuserfeedback.com.
If your team needs a data processing agreement (DPA), send us a request and we'll review your rollout, the data categories involved, and any DPA language your procurement or legal process needs us to confirm.
You can also email hello@getuserfeedback.com if your review needs attachments or a longer explanation.
For feedback, survey, form, widget, and respondent data collected through your workspace, your team usually decides why and how that data is used. getuserfeedback.com processes that data to provide the service.
Some account, security, billing, support, and service-operation data may be handled for getuserfeedback.com's own operational purposes.
Core providers support the service for every workspace. Optional providers only apply if your workspace uses that feature or integration.
Tell us before production rollout if your DPA needs a provider excluded, region-limited, or described in a specific way.
The current getuserfeedback.com subprocessor and supporting-provider list is below. Some providers only apply when the related feature is enabled for your workspace. This list does not include tools your team connects with your own accounts.
| Provider | Used for | Data that may be involved | Scope |
|---|---|---|---|
| Vercel | Hosting the product, API, and widget. | Workspace data, respondent data, request metadata, logs, and operational records. | Core service. |
| Neon | Postgres database storage for the service. | Workspace data, respondent identity data, response content, response metadata, and operational records. | Core service. |
| Clerk | Account sign-in, workspace access, and authentication. | Account user identity, workspace membership, and authentication metadata. | Account users and workspace admins. |
| Amazon Web Services | Email delivery and supporting service infrastructure. | Email addresses, message content, delivery state, provider event metadata, and operational records. | Email and infrastructure workflows. |
| Customer.io | Customer messaging and lifecycle email. | Account contact details, message content, delivery state, and subscription or preference metadata. Link tracking can also include tracking URLs, query values, IP address, user agent, and related HTTP request metadata. | Customer communications. |
| Sentry | Error monitoring and service diagnostics. | Error context, request metadata, logs, and limited support/debug traces. Browser session replay telemetry may be sampled for service diagnostics. | Service monitoring and support. |
| Segment | Product analytics and event delivery. | Usage events, identifiers, customer-entered AI prompts, device or request metadata, and integration delivery state. | Analytics or configured delivery workflows. |
| Mixpanel | Product analytics. | Usage events, identifiers, product analytics properties, device or request metadata, and related analytics state. | Product analytics. |
| GitHub | Engineering issue tracking and operational follow-up. | Minimized support context, issue metadata, logs, reproduction details, or operational records when needed. | Support and engineering operations. |
| Google Fonts | Font catalog search, theme previews, and theme font loads. | Font family queries, stylesheet requests, font file requests, IP address, user agent, and related HTTP request metadata. | Theme and font workflows. |
| OpenAI | Optional AI-assisted generation, summarization, analysis, or agent-assisted work. | Prompts, generated output, response content, or metadata when included in the workflow. Response-analysis workflows redact common identifiers in response and activity text, such as email addresses, phone numbers, URLs, IP addresses, cards, API keys, and tokens, before model calls. | AI-assisted product, support, or operations workflows. |
| Anthropic | AI-assisted support, operations, and review workflows. | Minimized, redacted, or anonymized prompts, generated output, support context, or operational metadata when included in the workflow. | AI-assisted support and operations workflows. |
| Cursor | AI-assisted engineering, support, and operations work. | Minimized, redacted, or anonymized support context, operational context, code context, prompts, and generated output. | AI-assisted engineering and operations workflows. |
Where we use AI tools for support, operations, or privacy-request management, we minimize the context and use redacted or anonymized summaries where practical. Some product AI workflows can include customer-provided text, so we review AI-assisted processing as part of DPA or security questions. These tools may help organize, summarize, or route work, but they do not replace the privacy-request review and approval process.
Customer-configured integrations can add other services to your data flow. Your connected accounts are usually part of your own vendor stack rather than getuserfeedback.com subprocessors. We can review what getuserfeedback.com sends or receives for an integration.
If you need vendor-by-vendor detail for a DPA or security review, send us your questions. We'll confirm what is in scope for your rollout and what needs separate terms, exclusions, or regional handling.
We review material changes to supporting systems that may affect covered data, regions, processing purpose, or workspace-specific terms. If a change affects your rollout, we'll confirm what changed and whether your DPA, subprocessor, transfer, or residency terms need to be updated.
We may process or store information in countries other than where you live. If your review needs EU, UK, or other transfer terms, contact us before sending production data so we can confirm the covered data, regions, subprocessors, and exclusions.
For the fastest review, include:
For DPA, subprocessor, or transfer questions, contact us at hello@getuserfeedback.com.