AutoDoc is designed so recordings, transcripts, notes, and search stay on your machine. Google Calendar access is optional, limited to scheduling features, and backed by local encryption and clear deletion controls.
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.
Last updated: May 15, 2026
AutoDoc is a local-first desktop application that helps users record meetings, transcribe meeting audio on-device, and generate meeting notes locally. This Privacy Policy explains what information AutoDoc processes, how that information is used, and the choices users have.
1. Information AutoDoc may process. Depending on which features you enable, AutoDoc may process meeting recordings, transcripts, speaker labels, summaries, notes, search indexes, local settings, and optional diagnostics data if you opt in to analytics or crash reporting. If you connect Google Calendar, AutoDoc may also process Google user data including your primary calendar email address, calendar event titles, start and end times, attendee email addresses, meeting links, recurring event identifiers, and OAuth tokens needed to maintain the optional calendar connection.
2. How AutoDoc uses information. AutoDoc uses information only to provide the app's features, including recording meetings, generating local transcripts and notes, showing upcoming calendar events, matching recordings to events, titling recordings, suggesting speaker names, and maintaining account connectivity for optional calendar integrations. Google user data is used only to provide or improve these user-facing features that you request inside AutoDoc.
3. Protection of sensitive data. AutoDoc uses security procedures designed to protect the confidentiality of sensitive data, including Google user data. Google OAuth flows and Google API requests are made over encrypted HTTPS connections. OAuth tokens are stored locally using platform-backed encryption where available, and AutoDoc encrypts sensitive local meeting data at rest on the device. Access to Google user data is limited to the app functionality that you enable, such as calendar sync, meeting matching, and speaker suggestions.
4. Local-first processing and storage. AutoDoc is designed so meeting content is processed and stored locally on your device. Meeting recordings, transcripts, notes, and related metadata are not intended to be uploaded to AutoDoc-operated servers for cloud processing as part of the core product experience. AutoDoc's AI note-generation workflow runs locally on-device rather than sending meeting content to a hosted model service as part of the core experience.
5. Optional calendar access. If you connect Google Calendar or Microsoft Outlook, AutoDoc accesses only the data needed for its calendar features, such as event title, time, attendees, recurring identifiers, and meeting links. This access is optional and can be removed from the app settings and from the provider's account-permissions interface. AutoDoc does not require Google Calendar access to use its local recording, transcription, or note-generation features.
6. Data retention and deletion. AutoDoc retains Google Calendar connection data only for as long as needed to provide the optional calendar features you choose to use. OAuth tokens and saved connected-account records remain on your device until you disconnect the calendar account or delete local AutoDoc data. Locally synced calendar data may continue to appear in the app until it is refreshed, disconnected, or removed with local app data. If Google Calendar information has already been copied into saved meeting metadata on your device, such as a meeting title, meeting link, attendee-based speaker suggestion, or recurring identifier associated with a recording, that local metadata may remain until you delete the related recording or reset local AutoDoc data. You can delete local AutoDoc data from the app, disconnect the Google account from AutoDoc, and revoke AutoDoc's access from your Google account permissions page.
7. Optional analytics and crash reporting. Analytics and crash reporting are off by default unless you choose to enable them. If enabled, AutoDoc may send anonymous product usage and reliability data, such as onboarding completion, feature interactions, app version, operating system details, and crash stack traces. Meeting content, transcript text, calendar event contents, attendee lists, and OAuth tokens are not intended to be included in those analytics events.
8. Data sharing, transfer, and prohibited uses. AutoDoc is not designed to sell personal information or Google user data. Except as needed to operate the connected services you explicitly use, AutoDoc does not transfer or disclose Google user data to third parties for advertising, data brokering, or generalized model training. AutoDoc does not use Google user data to train, fine-tune, or improve generalized, shared, or third-party artificial intelligence or machine learning models.
9. Third-party services. Some features may rely on third-party services, including Google APIs, Microsoft services, OAuth routing infrastructure, and optional analytics or diagnostics providers. Those services may process data needed to perform their role in the feature you choose to use.
10. Your choices. You can decline optional analytics, disconnect calendar accounts, revoke provider permissions, and delete local AutoDoc data from your device.
11. Open source. AutoDoc is intended to be distributed as open-source software, which helps users review how the app handles data and local processing.
12. Changes to this policy. This policy may be updated from time to time. If material changes are made, the updated version will be posted at this URL with a new effective date.
13. Google API disclosure. AutoDoc's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.