Privacy

Local-first, with clear boundaries.

AutoDoc is designed so recordings, transcripts, notes, and search stay on your machine. Calendar access is optional, and analytics are off unless you choose to enable them.

How it works

What stays where.

Your machine
Meeting recordings, including screen, microphone, and system audio
Transcripts, speaker labels, summaries, and search index
Meeting metadata and app preferences
Local AI processing for transcription and note generation
Encrypted local storage for sensitive app data where supported
Optional external services
Google or Microsoft calendar APIs, only if you connect an account
OAuth routing to complete calendar sign-in
Opt-in analytics and crash reporting, if enabled by you
Summary

What we collect, and why.

1
Meeting content stays local
AutoDoc is built so your recordings, transcripts, summaries, and search history remain on your device instead of being uploaded for cloud processing.
2
Calendar access is optional
If you connect Google Calendar or Microsoft Outlook, AutoDoc reads event details like title, time, attendees, and meeting links so it can show upcoming meetings and organize recordings.
3
Analytics are opt-in
Usage analytics and crash diagnostics are off by default. If you enable them, AutoDoc may send anonymous product and reliability data such as feature interactions, app version, and stack traces.
4
Meeting content is not analytics payload
Meeting recordings, transcripts, summaries, participant names, and calendar contents are not intended to be sent as analytics or crash-report payloads.

A note about calendar connections.

Google Calendar and Microsoft Outlook connections are optional. They exist to show upcoming meetings, title recordings, attach related meeting metadata, and support per-meeting recording controls. They are not required to use AutoDoc's local recording and note-taking features.