Subprocessors
Last updated: July 2026
Reagent, operated by ReaperAgent, LLC, uses the third-party subprocessors below to provide the Service. This page is the authoritative, versioned list; it is referenced by our Privacy Policy. Each subprocessor is contractually bound to protect the data it processes and to use it only to provide services to us. We update this list when we add or remove a subprocessor and revise the "Last updated" date above.
All processing listed below occurs in the United States. We do not currently offer a regional (for example, EU) data-residency commitment.
| Subprocessor | Purpose | Data received | Location | Personal data |
|---|---|---|---|---|
| Supabase | Authentication, application database, and temporary file storage | Account data (email, display name, hashed password), usage and credit records, temporarily uploaded dialogue audio and reference files | United States | Yes |
| Vercel | Application and website hosting, and the AI Gateway that routes model requests | All request data as host; text prompts and transcripts in transit through the AI Gateway | United States | Yes |
| Anthropic | Claude AI models for processing text commands and generating responses | Text commands and REAPER project metadata (e.g. track and item names) | United States | Yes |
| Gemini models for dialogue transcript analysis and translation | Text transcripts only — no audio is sent to Google | United States | Yes | |
| ElevenLabs | Speech-to-text transcription for dialogue-editing features | Dialogue audio, uploaded temporarily and deleted after processing | United States | Yes |
| Voyage AI | Text embeddings for REAPER/Wwise documentation search | Documentation search-query text | United States | Yes |
| WorkOS | Enterprise SAML single sign-on (SSO) | Email and organization membership; the SAML assertion (which may include the user’s name) is processed in transit, though Reagent stores only email and organization | United States | Yes |
| Polar | Subscription management and billing | Name, email, and subscription/billing details | United States | Yes |
| Stripe | Payment card processing, used by Polar | Payment card details (Reagent does not store full card numbers) | United States | Yes |
| PostHog | Product analytics | Usage and behavioral events, IP address, and, for identified users, profile attributes | United States | Yes |
| Resend | Transactional and contact-form email delivery | Email address and message content | United States | Yes |
| Mintlify | Documentation site hosting | Documentation-site visitor logs (IP address, page views) | United States | Infrastructure only |
| GitHub | Desktop application update distribution and avatar image delivery | Application version and IP address on update checks | United States | Infrastructure only |
Enterprise data handling
For enterprise (SSO) organizations, model traffic is routed to the customer's own model endpoint rather than through the subprocessors above, and the transcription, feedback, and documentation-search features that would contact our servers are disabled. See the Privacy Policy for details.
Data Processing Agreement
Enterprise customers who require a Data Processing Agreement (DPA) can request one through our contact page.