AudioToNotes

Security & Privacy

How we handle the audio you upload. Plain language, no marketing claims we can't back up.

No meeting bots

We never join your Zoom, Teams, Google Meet, or Webex call. There is no account to invite, no Calendar OAuth, no third-party participant in the room. You record on the host platform (where every participant gets a recording disclosure), download the file, and upload it to AudioToNotes when you choose.

No training on customer audio

Your uploaded audio, generated transcripts, and notes are not used to train AudioToNotes' foundation models. We do not aggregate customer audio for cross-tenant model improvement. Period.

Encrypted in transit

All uploads travel over TLS. Audio is processed inside our infrastructure and the structured output is delivered back to your account. We do not stream raw audio over insecure channels.

You control retention

After processing you can delete the upload immediately, or keep it in your account for later reprocessing. Default retention is short-window processing storage. You always have a delete button.

What AudioToNotes does not do

  • We do not auto-join your meetings via calendar integration.
  • We do not request OAuth on Zoom, Teams, Google Meet, or Webex accounts.
  • We do not run a meeting-bot account that gets invited to your calls.
  • We do not use your audio, transcripts, or notes to train our foundation models.
  • We do not sell customer data, share it with advertisers, or hand it to LLM providers that retain training data.

Frequently asked

Does AudioToNotes integrate with my Google Calendar, Outlook, or Zoom calendar?

No, and that's deliberate. Auto-join calendar integrations are the source of most "AI notetaker" trust problems. AudioToNotes is explicitly user-initiated: you choose which recording to process. There is no calendar scope to grant.

Is AudioToNotes HIPAA-compliant? Can you sign a BAA?

We are not currently signing BAAs. AudioToNotes is in early access; BAA support is on the roadmap and we'll publish a clear position before that's available. If your workflow requires a signed BAA today, do not transmit PHI through AudioToNotes — use a vendor that has one. Email team@audiotonotes.com to discuss timing.

Where is my audio processed?

Audio is processed in the cloud region you select in your account settings. We don't move customer audio across regions silently. Specific provider and region details are available on request to enterprise prospects.

What happens to a file after I delete it?

Deletion removes the file from your account and from active processing storage. Operational backups follow normal cloud-provider retention windows (typically 7–30 days) before being purged.

Does AudioToNotes share customer data with third parties?

We use cloud infrastructure providers for storage and compute, and Whisper-class speech models running inside that infrastructure. We do not sell customer data, do not share it with advertisers, and do not feed it to third-party LLM providers that retain training data.

Can my organization audit your security posture?

Enterprise security questionnaires and architecture reviews are handled on request. Email team@audiotonotes.com with your scope and we'll respond.

Security questions or vulnerability reports

Email team@audiotonotes.com for security questionnaires, architecture reviews, or to responsibly disclose a vulnerability. Include “Security” in the subject and we'll route it to the right person.

Get early access

Join the waitlist — no calendar bot, no spam, no surprises in your meetings.

Join the waitlist

Last updated: 2026-05-11