Subprocessors

Last updated: 20 October 2026

Who helps us run Rehearse, what they do, and what data they touch.

Draft — not yet in force. This list is a draft awaiting approval. Anything marked [to confirm: …] is still to be filled in.

1. Our subprocessors

These are the companies that process personal data for us to run Rehearse. Each receives only what it needs for its part.

Name	Purpose	Data involved	Location	Used for
Amazon Web Services	Hosting, database, file storage, sign-in and encryption keys	All account, session, feedback and Rehearse for Teams data	United States (us-east-1, N. Virginia)	App, Teams
OpenAI	The live AI conversation, speech transcription (gpt-4o-transcribe), feedback and scenario safety checks	Live voice audio, transcripts, scenario text, and profile details used to tailor the character	United States	App, Teams
LiveKit	Real-time audio and video transport for live sessions, and hosting of the software that connects a session to the AI	Live audio and video in transit, the conversation while a session runs, session identifiers	—	App, Teams
Anam	Renders the lip-synced avatar face from the AI character’s speech, for face-to-face sessions	The character’s generated speech audio and appearance settings — not the user’s voice	—	App, Teams
ohteapea	Email delivery: sign-in codes, Rehearse for Teams invitations and account email	Email address and the email’s contents	—	App, Teams
RevenueCat	In-app subscription and purchase status	Account ID, purchase history and store receipts	United States	App
Layers	Product analytics in the app, where switched on	Account ID, in-app events, basic device information and, on Android, the advertising ID	—	App
Vercel	Hosting for this website and the Rehearse for Teams portal	Visitors’ IP addresses and request details	United States; served from a global edge network	Website, Teams
Google (Fonts)	Serves the website’s fonts	Visitors’ IP addresses and browser details	United States	Website
Google (Analytics 4)	Website visit measurement — only after a visitor accepts analytics cookies	Pages visited, approximate location, device and browser details, a cookie identifier	United States	Website

“—” means we haven’t confirmed where that provider processes data. [to confirm: processing locations for LiveKit, Anam, ohteapea and Layers]

2. Not our subprocessors

Apple and Google handle app downloads, in-app purchases and refunds through the App Store and Google Play. They do this as independent companies under their own terms and privacy policies, not on our instructions.

Your employer, on Rehearse for Teams, is the controller of its people’s Teams data, not a subprocessor.

3. Changes to this list

When we add or replace a subprocessor, we’ll update this page and the date at the top.

For Rehearse for Teams customers, we’ll also email the company’s admin contact at least [to confirm: notice period, e.g. 30 days] before a new subprocessor starts processing their people’s data, and the company can object as set out in our Data Processing Addendum. To ask about this list, email akil@rehearsenow.app.