For professionals handling client material, this page sets out how AudioBrief Studio processes the content you submit.
Last updated 30 August 2026
When you submit a voice note, you decide what is recorded and why. AudioBrief Studio processes that content in order to transcribe it, generate a brief and store the result in your workspace.
[To be completed] The formal controller/processor designation and the executable contractual clauses are being prepared with legal counsel.
Audio recordings you make or send, the transcripts derived from them, the structured briefs generated from those transcripts, your account email address, and — if you connect WhatsApp — the phone number you verify and the sender names you assign to notes. Whatever is spoken in a recording is processed as part of that recording.
Data is transmitted over encrypted HTTPS connections. Access to briefs, folders, stored audio and account records is restricted per-user at the database and storage layer, so one account cannot read another's content. Inbound WhatsApp webhooks are signature- verified before any message is processed. Payment card data is handled by Stripe and never reaches our systems.
Delivering the product requires third-party providers for hosting and database, speech- to-text and language models, WhatsApp message delivery, payments, and product analytics.
[To be completed] A named sub-processor list with entity names, purposes, hosting locations and a change-notification commitment will be published here before general availability.
You can delete an individual brief from the app at any time, and copy or export brief content for your own records. Account-level deletion requests are handled by support@audiobriefstudio.com.
If your firm requires a countersigned data processing agreement before onboarding, contact support@audiobriefstudio.com and we will work through your template.