Sub-processors and other recipients
Version: 2026-10-25.
A sub-processor is another company that receives personal data from Availies in order to run the service for our customers (the data processing agreement, section 6). The second table lists companies that receive data for which Availies itself is the controller (billing, support mail), and the third lists recipients that are not our sub-processors but are named here so that nothing is hidden.
Sub-processors (data we process for customers)
| Company (legal name) | What it does for us | What it receives | Where it keeps it | Transfer basis (out of the EU) |
|---|---|---|---|---|
| Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA | Hosts the service (Workers), stores its data (D1 database, Durable Objects, R2 files when logos arrive) and checks that a visitor is a person (Turnstile) | Everything the service stores: accounts, members, hosts, bookings, visitor details, routing answers, email records, audit log, encrypted calendar tokens. For the human check: the visitor's network address and browser signals | Database, objects and files are created in Cloudflare's EU jurisdiction and stay there. Requests are handled in the Cloudflare data centre nearest the person, which may be outside the EU | EU-U.S. Data Privacy Framework (Cloudflare is certified), with the EU Standard Contractual Clauses (Decision 2021/914) as fallback (DPA 6) |
| Plus Five Five, Inc. (Resend), 2261 Market Street #5039, San Francisco, CA 94114, USA | Delivers the emails the service sends | The recipient's email address and the content of each email: sign-in codes, invitations, booking confirmations, changes, reminders and cancellations (which name the people in the meeting and its time), and notices to account owners | Emails are sent from Resend's EU region (Ireland, eu-west-1). Resend's own records of each email (recipient, subject, delivery status, logs) are stored in the United States whatever the sending region | EU-U.S. Data Privacy Framework (Resend is certified, DPA 11.1), with the EU Standard Contractual Clauses of its DPA (6.2) as fallback |
| Functional Software, Inc. (Sentry), 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA | Receives reports of failures nobody planned for | The kind of error and its message, the lines of the service's own code around it, the request's method and address (host and path) without the query string, the request's id, the account's id, and for some failures other internal ids (a lookup endpoint, an assistant connection, a background job). Scrubbed before sending: no person, cookie, header, body or query string, and every email address, network address, credential and token the scrubber recognises is replaced. Listed because a path can name an account's handle or a record's id, and a message can hold other words | Our project is in Sentry's EU region (Frankfurt, Germany). Sentry keeps organisation and user-account metadata, settings and usage data in the United States whatever the region | EU-U.S. Data Privacy Framework (Sentry is certified), with the EU Standard Contractual Clauses as fallback (DPA Schedule 3) |
Not yet in use but built: Sentry is switched on in milestone B (decisions 7 and 9) and is listed now so that the list need not change at launch.
Recipients for data we control (members, billing, support)
| Company (legal name) | What it does for us | What it receives | Where it keeps it | Transfer basis |
|---|---|---|---|---|
| Stripe Payments Europe, Limited, Dublin, Ireland (the Stripe entity for EEA accounts) | Takes payments for paid plans, holds the subscription and issues invoices | From us: a signed reference to the account and the plan and seat count. From the customer, on Stripe's own pages: name, billing address, email address, VAT number and card details. We never see the card | Stripe's own systems; Stripe states that its processing takes place in the EU and the United States under its own transfer addendum | Stripe's Data Transfers Addendum (Data Privacy Framework and EU Standard Contractual Clauses) |
| Google Cloud EMEA Limited, Dublin, Ireland (Google Workspace, EMEA contracting entity) | Runs the mailbox that receives support@availies.com and privacy@availies.com | Whatever the sender writes to us | Google's data centres, in the EU or elsewhere as Google's Cloud Data Processing Addendum allows | Google's Cloud Data Processing Addendum: adequacy, Google's alternative transfer solution, or SCCs |
| Cloudflare, Inc. (see above) | Forwards mail sent to support@availies.com, which is rewritten to a group address on our other domain and forwarded on by Cloudflare Email Routing | The forwarded support mail, in transit | Transit only | As above |
| Google Ireland Limited (Gmail), Gordon House, Barrow Street, Dublin 4, Ireland | Runs the mailbox where the forwarded support mail is read | The forwarded support mail | Worldwide, including the United States | EU-U.S. Data Privacy Framework for Google LLC transfers; standard contractual clauses where required |
Stripe acts for us as a processor when it takes payments, and as a controller in its own right where it prevents fraud and loss and meets its own legal duties, such as anti-money-laundering and know-your-customer checks; for that part its own privacy policy applies, and the privacy notice says so in Stripe's own suggested words. Google keeps Workspace mail in its own data centres, in the EU or elsewhere; Google is certified under the EU-U.S. Data Privacy Framework, and its addendum adds the other mechanisms named in the table.
The email provider (Resend) gives 14 days' notice of its own sub-processor changes, less than the 30 days this list promises customers; the data processing agreement (section 6) says how such a change is passed on.
Recipients that are not our sub-processors
| Recipient | Why it is listed |
|---|---|
| Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (Google Calendar) | The host's own calendar provider. The host, or their organisation, already has its own agreement with Google and connects the calendar itself. The service writes the booked meetings to that calendar (time, title, the visitor's name and email address, guests), asks Google which times are busy, and reads the changes to meetings it created. Google acts here for the host or the host's organisation under their own agreement, and the service reaches the calendar on the controller's instruction; Google is therefore not our sub-processor. Microsoft will be listed the same way when Microsoft calendars are added. |
| The customer's own systems | Webhook endpoints and lookup systems the customer connects receive bookings and changes. They are the customer's processors or systems, not ours. |
Changes to this list
Customers are told by email to the account's owners at least 30 days before a company is added to or replaced in this list, and may object, as the data processing agreement (section 6) says. A change in one of these companies' own sub-processors is passed on as soon as we learn of it (the email provider gives 14 days' notice), and the right to object stands. This list and its version date are the record.
Sources
Read on 2026-10-22 from each company's own pages. Re-read at publication and note the date here.
- Cloudflare Customer Data Processing Addendum, version 6.4, effective 3 April 2026 (cloudflare.com/cloudflare-customer-dpa): entity Cloudflare, Inc.; SCCs (Decision 2021/914), DPF transfers not treated as restricted (clause 6.4); sub-processor changes 30 days ahead with 10 days to object. EU jurisdiction facts: decision record 0011 and Cloudflare's D1 and Durable Objects data-location pages it cites.
- Resend Data Processing Agreement (resend.com/legal/dpa, dated 2025-12-31): processor Plus Five Five, Inc., "primary processing operations take place in the United States" (6.1), EU SCCs (6.2), DPF compliance (11.1), 14 days' notice of sub-processor changes (4.2), breach notice "without undue delay" (8.6). Regions (resend.com/docs/dashboard/domains/regions): Ireland (eu-west-1) among four; "Region selection controls where your emails are routed and sent from. It does not control where customer data is stored"; account data is stored in the United States regardless.
- Sentry Data Processing Addendum (sentry.io/legal/dpa): processor Functional Software, Inc. d/b/a Sentry; DPF first, SCCs as fallback (Schedule 3); 30 days' notice of sub-processor changes (7.2); breach notice "promptly and without undue delay" (4.2). Data storage location (docs.sentry.io/organization/data-storage-location): US (Iowa) or EU (Frankfurt), chosen at organisation creation and permanent; user accounts, organisation settings, audit logs, DSN keys and usage data stay in the US.
- Stripe Services Agreement, last modified 28 September 2026 (stripe.com/legal/ssa): "Stripe Payments Europe, Limited" for EEA accounts (section 12 table; section 13.10). Stripe Data Processing Agreement, last updated 28 September 2026 (stripe.com/legal/dpa): Data Transfers Addendum covering the Data Privacy Framework and EEA SCCs. Stripe Privacy Center (stripe.com/privacy-center/legal): "Stripe is a data processor where it is providing the Stripe Services to Business Users"; controller for fraud monitoring and for choosing banks and payment methods.
- Google contracting entity (cloud.google.com/terms/google-entity): for Google Workspace, billing address in "EMEA except France, Italy and Poland": Google Cloud EMEA Limited. Cloud Data Processing Addendum (cloud.google.com/terms/data-processing-addendum): Google is processor (4.1); breach notice "promptly and without undue delay" (7.2.1); 30 days' notice of new sub-processors (11.4(a)); transfers under adequacy, an alternative transfer solution or SCCs (Appendix 3, section 4).
- Google Terms of Service, effective 30 July 2026 (policies.google.com/terms): in the EEA, Google services are provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
- Google OAuth scopes (developers.google.com/identity/protocols/oauth2/scopes):
calendar.freebusy"View your availability in your calendars";calendar.calendarlist.readonly"See the list of Google calendars you're subscribed to";calendar.events.owned"See, create, change, and delete events on Google calendars you own". - Google Workspace API User Data and Developer Policy, last updated 2026-09-03 (developers.google.com/workspace/workspace-api-user-data-developer-policy), Limited Use: the required statement, copied into the privacy notice word for word.
- Data Privacy Framework List (dataprivacyframework.gov, read through its public search on 2026-10-23, list data of 2026-10-22): Cloudflare, Inc., Plus Five Five (Resend), Functional Software Inc. (Sentry), Stripe, LLC and Google LLC are active participants for the EU-U.S. Data Privacy Framework. Recheck at publication and at every change to this list.
- Stripe Privacy Center (stripe.com/legal/privacy-center, read 2026-10-23): Stripe is "both" a processor and a controller; the sentence Stripe suggests for its users' privacy notices is used in the privacy notice. Stripe DPA 4.3: the user must give its customers the notices Stripe's processing needs.