Legal
Sub-processor List
Revision 3
Effective: October 20, 2026
Versions
- Revision 3 · October 20, 2026 · Current
Clarifies provider roles, optional features, sign-in providers, processing regions, deletion limits, diagnostics, and the scope of vendor BAAs.
- Revision 2 · September 3, 2026 · Previous
This list describes providers used by LW Agency Limited (Hushscript) across the website, application, API, MCP server, and optional Chrome extension. A provider receives data relevant to its role and the features you use. Some also act independently for their own purposes; listing them here does not mean they are a processor for every activity.
We use contractual and technical safeguards appropriate to those roles. The Privacy Policy explains purposes, choices, retention, and rights; the Cookie Policy explains optional measurement. Processing regions below do not guarantee that every support, security, or administrative operation stays in one country. We give advance notice of material provider changes where required by law or an applicable agreement.
Cloudflare
- Role: Website and application hosting, content delivery, storage, computing, DNS, bot protection, and diagnostic relays.
- Data: IP addresses and request metadata; account and usage data; processing audio; encrypted stored transcript content; aggregate Audio Self Check results; relayed error reports. Free browser-tool files remain local unless you separately choose an upload feature.
- Region: Global infrastructure, with regional application storage and processing. European routing does not cover every Service function or provider.
- Provider: cloudflare.com
AssemblyAI
- Role: Speech recognition for account transcription and optional website/in-app previews.
- Data: Submitted audio or preview clips, transcription options, and resulting transcript text. A chosen in-app preview sends up to 5 minutes before payment. The rest of a file waiting for credit is not sent for full transcription until that job starts.
- Retention: We remove our processing audio after completion or failure and request deletion of provider transcript records. Deletion and expiry cleanup can require retries. Unstarted waiting files are scheduled for deletion within 4 hours.
- Region: EU infrastructure for EU/EEA/UK/Swiss users’ speech recognition; United States for other users.
- Agreement: AssemblyAI processes audio and transcripts under a signed HIPAA Business Associate Agreement (BAA) with us, including an opt-out from its model-improvement program. See the limits below.
- Provider: assemblyai.com
OpenAI
- Role: Optional Insights, cleaned-up transcripts, and translations, including generation enabled in your settings.
- Data: Transcript text, timestamps, and speaker labels/names. Requests do not attach audio, account email, or account identifiers; the submitted text itself may contain personal data.
- Retention and training: Requests disable provider-side response storage and are subject to no-training terms. Disabling response storage does not by itself establish zero data retention.
- Region: United States.
- Agreement: OpenAI processes transcript text under a signed HIPAA Business Associate Agreement (BAA) with us. See the limits below.
- Provider: openai.com
Stripe
- Role: Payment processing, card verification, billing, fraud prevention, and disputes when you use payment features.
- Data: Card and billing details supplied to Stripe, customer and purchase references, payment-method status/fingerprints, and transaction or dispute evidence. We do not receive or store full card numbers. Stripe also processes data for its own legal and financial obligations.
- Region: United States and global infrastructure.
- Provider: stripe.com
Mailgun
- Role: Transactional email, including requested sign-in links and account/service notices.
- Data: Recipient email address and message content. Apple forwards messages sent to an Apple private relay address.
- Region: United States.
- Provider: mailgun.com
Sentry
- Role: Error diagnostics for the website, application, API, MCP server, and optional extension.
- Data: Masked errors, code locations, query-free page addresses/routes where applicable, software/device information, and diagnostic steps. App/API/MCP reports may contain an opaque account identifier and region/workspace tags. Website reports have no account identity. Extension reports may contain the format of an added file, broad size/duration ranges, how far a failed upload got and how long it took, and an upload job reference; extension error reporting can be disabled in its Account screen.
- Safeguards: Diagnostic pipelines filter content and direct identifiers, remove IP addresses before forwarding, and disable IP inference. Free-text masking cannot guarantee detection of every possible identifier. Audio, transcript bodies, and credentials are not intended diagnostic fields.
- Region: United States.
- Provider: sentry.io
Optional analytics and advertising providers
Google Analytics measures website usage and content-free server-confirmed actions. Google Ads receives selected conversions and supports advertising/remarketing. Campaigns may also use Meta, LinkedIn, X, Microsoft Advertising, and LY Corporation, through website tags or server-side conversion reporting where configured.
- Data: Cookie/pseudonymous identifiers, campaign and click IDs, query-free landing/referrer information, content-free events, purchase value/currency, and hashed identifiers where conversion reporting uses them. Hashing does not make an identifier anonymous. These events exclude recording and transcript content.
- Choice: Prior consent where required; otherwise enabled by default until changed. Cookie settings controls optional analytics and advertising. Global Privacy Control opts out of advertising. The application has no browser analytics or ad scripts.
- Regions: United States/global infrastructure; LY Corporation: Japan.
- Providers: Google, Meta, LinkedIn, X, Microsoft Advertising, LY Corporation.
Optional sign-in providers
Apple and Google sign-in are optional alternatives to email sign-in. They operate their own accounts under their own privacy policies and are not engaged to process your recordings.
- Apple: We receive a user identifier, email or private relay address, verified-email status, and relay status. We keep an encrypted token for revocation and send it to Apple when revoking a connection. Apple may send account/relay status notices.
- Google: We receive a user identifier, email address, and verified-email status. We do not keep a Google token.
- Regions: Global infrastructure.
- Providers: Apple, Google.
Limits of vendor agreements
We have signed HIPAA Business Associate Agreements (BAAs) with AssemblyAI and OpenAI for their respective processing. These agreements do not cover the whole Hushscript service: we have no BAA with other providers, including Cloudflare, Sentry, and Mailgun. For that reason, Hushscript does not sign BAAs with customers at this time; covered entities should not rely on it for protected health information under HIPAA. Please do not submit protected health information if your use requires a BAA with us. Vendor BAAs alone do not establish HIPAA or GDPR compliance for your use or replace other required data-processing or transfer agreements.
If you have questions about a provider or a requirement for your content, please contact support@hushscript.com.