Subprocessors
Every third party that can see data you or your respondents give us. This is the question a security reviewer asks first, and the one that is easiest to answer incompletely — so the hosting provider, the database and the AI model path are all on the list, and so is the email provider that receives your respondents' answers.
Acquainto Inc. uses the service providers below to operate the Acquainto service. Each processes data only to provide its service to us, and for no other purpose. We remain responsible to our customers for how these providers handle customer data.
We rely on each provider’s own published data protection terms. We have not signed a bespoke data processing agreement with any of them — see Gaps, where we say so plainly rather than leave you to assume otherwise.
1. Providers that process customer or respondent data
| Provider | What it does | What it processes | Where |
|---|---|---|---|
| Amazon Web Services, Inc. | Production hosting, database, file storage, encrypted backups, security monitoring, system alert email — since 23 September 2026 | All customer and respondent data | United States — us-east-1 (Virginia); encrypted database backups replicated to us-west-2 (Oregon) |
| Railway Corporation | Runs the application and the API in our pre-production environment, used for testing and internal review | Anything created in that environment. It is not where your account or your eFlows run | United States (Oregon) |
| Supabase, Inc. | The database for that same pre-production environment | Anything created in that environment, at rest | United States (West) |
| OpenRouter, Inc. | Routes every AI request to a model provider, under no-training and zero-retention instructions | Conversation content: question text and the answers given so far | United States, then the provider below |
| Upstream AI model providers, via OpenRouter | Serve the AI request | The same conversation content | Depends on which provider the router selects. We do not pin this today. |
| Twilio Inc. (SendGrid) | Sending transactional email: verification, invitations, password resets, completion notifications | Email addresses, names, message content — and respondent answers, because a completion notification contains the full question-and-answer table | United States |
| Google LLC (Sheets and sign-in) | Syncs responses into your own Google Sheet, when you connect it | Response content, for the eFlows you explicitly connect | United States |
Two hosting providers, and which one holds your data. If you signed up atapp.acquainto.com, your account, your eFlows and your respondents’ answers are onAmazon Web Services, and have been since 23 September 2026. Railway and Supabase still run a separate pre-production environment we use for testing and internal review. They are listed because that environment exists and it is real infrastructure — not because your data is in it.
We are naming AWS after the fact, and we would rather say so. The commitment in Changes to this list is 30 days’ notice before a new provider starts processing your data. AWS started on 23 September 2026 and this page names it on 25 September — two days late, not thirty days early. We are not backdating the claim. The notice commitment stands for every future change, and the objection and refund right in that section applies to Amazon Web Services from today, exactly as if we had given it in advance.
On the AI row. We send a per-request instruction not to retain or train on the content. We do not constrain which upstream provider the router selects, so we do not name one here: a named vendor on this page would be wrong the next time it routes somewhere else.
2. Providers that process account, website and operational data, not answers
| Provider | What it does | What it processes | Where |
|---|---|---|---|
| Functional Software, Inc. (Sentry) | Application error monitoring | Operational metadata only — route pattern, HTTP status, stack frames, an account id, the release. Never answers, never a respondent’s label | United States |
| Chargebee, Inc. | Subscription billing and invoicing | Account name, billing contact, billing address, plan | United States |
| Stripe, Inc. | Payment processing | Payment card and billing details, held by Stripe. We keep a reference and the last four digits | United States |
Two providers we are about to add, named here 30 days early. On 26 September 2026 we decided to start measuring how the acquainto.com website is used. That means two new providers on this page: Google LLC, for Google Analytics, and Cybot A/S / Usercentrics, whose Cookiebot service will ask for and record your cookie choice. Neither is running yet and neither will begin before 26 October 2026.
Both are confined to the marketing website. Neither will ever see an eFlow, a question or an answer, and no analytics tag goes on app.acquainto.com, console.acquainto.com or the pages your respondents answer on. This is the notice Changes to this list commits us to, and it is deliberately early: we named Amazon Web Services two days after it began, and said so. The objection and refund right in that section applies to both of these from today.
Why Sentry is in this table and not the one above. Its crash reports arebuilt field by field from an allowlist rather than filtered by a denylist, so a request body, a query string or a cookie is absent because it was never copied across. Tests assert that answer text, tokens and email addresses are absent from the serialized result. That claim is worth exactly as much as those tests: if the allowlist ever grows a field carrying answer content, Sentry moves up a table and this page changes the same day.
3. Services that process data only at a customer’s direction
These run only when a customer turns them on, and they send data to accounts the customer controls. They are your processors rather than ours — listed here because they are a real route for respondent answers to leave our systems.
| Service | What it does | What it processes | Where |
|---|---|---|---|
| Google LLC (Google Sheets) | Exports responses to a spreadsheet the customer connects | Response data the customer chooses to export, and an encrypted access token | United States |
| Customer-configured webhooks | Sends response events to a URL the customer provides | Response data the customer chooses to send | Determined by the customer |
| Completion notification recipients | Emails results to an address the customer nominates per eFlow | The full question-and-answer table for each completed conversation | Determined by the customer |
Deletion cannot reach these, and never will. Once an answer is in your sheet, your endpoint or your inbox, it is a copy in a system we have no access to. Neither a respondent erasure request nor a full account deletion can recall it.
4. Other service providers, with no customer or respondent data
| Provider | What it does |
|---|---|
| Google LLC (Google Workspace) | Company email and sign-in for Acquainto staff, including the staff console |
| GitHub, Inc. | Source code hosting and deployment pipelines |
acquainto.com sets no cookies and runs no analytics. No consent management service, no analytics tag, no advertising or affiliate tag — on any page, checked against the live site. If that changes, this section gains a row and the privacy policy gains a paragraph, on the same day.
Changes to this list
We will post changes here and email account owners who subscribe to updates at least 30 days before a new subprocessor begins processing customer or respondent data. To subscribe, email privacy@acquainto.com.
Within that period you may object to a new subprocessor on reasonable data protection grounds. Tell us the grounds and we will try to address them — and if we cannot, you may terminate the affected subscription and we will refund fees you have paid for the period after termination. You do not need any other agreement with us to exercise that right; it is this paragraph.
Change history
| Date | Change |
|---|---|
| 26 September 2026 | Advance notice, not a change. Google LLC (Google Analytics) and Cybot A/S / Usercentrics (Cookiebot) named as providers we intend to add to the marketing website, no earlier than 26 October 2026. Both are confined to acquainto.com; neither will see an eFlow, a question or an answer. The objection and refund right below applies from this date |
| 25 September 2026 | First published, with every provider above. Two of them appear on a public page of ours for the first time: Amazon Web Services, which has run the production environment since 23 September 2026, and Twilio (SendGrid), which we had previously described by role because we had not confirmed which provider the deployment used. AWS is named two days after it began, not thirty days before; the objection and refund right above applies to it from today |
Gaps we would rather you heard from us
- No signed data processing agreements with any provider on this page. We rely on their published standard terms.
- No model or provider pinning. We do not constrain which upstream serves an AI request, which is why the row above names a role rather than a vendor.
- We hold no security report we have read ourselves for any provider above. We record, per vendor, what we verified and what we take on trust.
- Deletion cannot reach destinations you connect — your sheet, your endpoint, your inbox. See section 3.
- We have not confirmed every provider’s own log-retention window. Where a period is a provider’s policy rather than a number we have read, we do not quote a number.
More detail on any of this: how your data is handled, or write to privacy@acquainto.com.