Legal
Suppliers
The companies that process personal data for Vela Coach, what each one gets, and where. Each works under its own data processing terms and may not use the data for its own purposes. Questions: hello@velacoach.tech.
Who processes data for us
Google Cloud
Hosting, database, server functions, sign-in, backups and logs
- What it gets
- Everything Vela stores, and everything that passes through our server on its way to the AI model: account details, transcripts, reports, direct reports’ names, emails and feedback, company policies, usage counts, and IP addresses in server logs.
- Where
- Stored in the European Union, in Google’s eur3 region (Belgium and the Netherlands), with the backups. Our server functions run in the United States (Iowa): data passes through them to be processed and is not stored there. Sign-in and page delivery are global.
- Its terms
- Google Cloud Data Processing Addendum. Transfers out of the UK and EU use the Data Privacy Framework, or the Standard Contractual Clauses where that does not apply.
Anthropic
The AI model that reads a 1:1 and writes the feedback
- What it gets
- Only the text each request needs: a transcript and the names in it, a direct report’s feedback when a report is written, coaching and practice conversations, and your company’s values, policies and behaviours.
- Where
- United States.
- How long
- Anthropic deletes API requests and replies within 30 days under its standard policy, and does not train its models on them. We keep nothing at Anthropic.
- Its terms
- Anthropic Data Processing Addendum, which includes the Standard Contractual Clauses and the UK International Data Transfer Addendum.
Stripe
Billing
- What it gets
- The payer’s name and email, the organisation’s name and the number of seats. Card details are typed into Stripe’s own pages and never reach Vela.
- Where
- European Union and United States.
- Its terms
- Stripe Data Processing Agreement and its Data Transfers Addendum.
Zoho Mail
Service emails: invitations, feedback requests, account and billing notices, 1:1 Health Check results
- What it gets
- The recipient’s name and email address, and the email itself.
- Where
- European Union.
- Its terms
- Zoho’s data processing addendum, from Zoho Accounts.
Also involved, but not our processors
Google and Microsoft sign-in
Your own account, not our supplier
- What happens
- When you sign in with Google or with a Microsoft work or school account, that provider tells us your name, email address and account identifier. We send it nothing.
Google (gstatic.com)
The sign-in code libraries
- What it gets
- Your IP address and browser details when your browser fetches the Firebase sign-in code. No account details and nothing you write. The typefaces and the handbook document readers are served from our own pages.
Your browser’s speech recognition
The microphone button
- What happens
- Your browser turns speech into text. In Chrome the audio goes to Google, in Safari to Apple, under your browser’s own terms. Vela only ever receives the text.
Changes
We email a Team customer’s administrators at least 30 days before we add or replace a supplier, and update this page the same day. How we handle personal data is in our privacy policy.