Effective Date: July 27, 2026 · Last updated: October 28, 2026
myScribe ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our application and services.
Account Information: When you create an account, we collect your name, email address, and authentication credentials. If you sign in with Apple or Google, we receive your name and email from those providers.
Audio & Video Recordings: When you use our recording features, we process audio and video data to provide transcription, summarization, and task extraction services. Recordings are stored securely and associated with your account.
Meeting Data: When you connect myScribe to meeting platforms (Zoom, Teams, Slack, Google Meet), we access meeting audio for transcription purposes only during active recording sessions.
Task & Project Data: We store tasks, projects, notes, and organizational data you create within the app.
Usage Data: We collect information about how you interact with our services, including recording duration, feature usage, and performance data.
Device Information: We may collect device type, operating system, and app version for troubleshooting and optimization.
myScribe sends relevant content to third-party services to provide the features you choose. Google Gemini processes typed assistance, summaries, extraction, search embeddings and selected media. OpenAI processes live voice audio, transcripts and relevant assistant context. Groq, AssemblyAI and Deepgram provide speech-to-text processing. The service used depends on the feature, your saved permissions and service availability.
Other processing services: Recall receives meeting links and captures meeting audio or video when you authorize the meeting assistant. Optional public web search sends queries to Tavily. URL imports send the selected URL to Jina Reader or a YouTube video identifier to YouTube for available captions; extracted content may then be processed by Google Gemini under a separate permission. Photo place lookup sends coordinates to BigDataCloud under its separate location permission. Imported photos and their location metadata may be stored with your account.
Your choices: Open your avatar → Profile → AI sharing to review or change each service's permission. Eligible services have a separate background-processing choice for queued, scheduled or automatic work. Withdrawal blocks later processing under that permission; it does not retract content already sent or confirm that an external job or meeting bot has stopped. Microphone access, billing approval and permission to record other participants are separate.
Provider handling: Providers have different retention and data-use terms, which can depend on the account, region, contract and service. AI-sharing permission does not authorize advertising or model-training sharing and is not a guarantee of zero retention or a provider's training settings. myScribe requests exclusion from Deepgram's Model Improvement Program for transcription requests and sends Jina Reader its do-not-cache-or-log control without requesting generated image captions. These request controls do not delete earlier transfers or establish protections at other providers.
For current provider details, see OpenAI data controls, Gemini API terms, Groq data controls, AssemblyAI retention and model training, Deepgram model improvement controls, Recall storage and retention, Tavily privacy, Jina Reader controls and BigDataCloud reverse geocoding.
This section describes specifically how myScribe accesses, uses, stores, and shares data from Google accounts. It applies whenever you connect a Google account to myScribe.
What we request, and why. myScribe requests only the following Google OAuth scopes, and only after you explicitly choose to connect your Google Calendar:
userinfo.email and userinfo.profile: to identify you, display which Google account is connected, and associate the connected calendar with your myScribe account.calendar.events: to read your upcoming calendar events so myScribe can show your agenda and answer schedule questions, automatically send a notetaker to meetings you have chosen to record, and create Google Meet invitations when you explicitly ask it to schedule a meeting.We do not request access to Gmail, Google Drive, Google Contacts, or any other Google service.
What we store. We store OAuth access and refresh tokens so myScribe can act on your behalf without asking you to sign in repeatedly; these are held with restricted database access and are never exposed to other users. We also cache event details (title, start and end time, attendees, description, and meeting link) so your agenda loads quickly and scheduled meetings can be joined on time.
How Google data is used with AI. When you use myScribe's text or voice assistant for help with your schedule, relevant calendar details may be included as context in a request to Google Gemini or OpenAI under your saved processing permission. myScribe does not use Google user data to train generalized AI or machine-learning models. Processor handling depends on the applicable provider terms and account controls described in AI Processing above; granting AI permission does not waive Google's Limited Use requirements.
Limited Use. myScribe's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, we do not:
Revoking access and deleting your Google data. You may disconnect Google at any time in myScribe under Settings → Calendar → Disconnect, or you may revoke myScribe's access directly in your Google Account at myaccount.google.com/permissions. Disconnecting in myScribe also revokes the grant with Google automatically. When you disconnect, we delete your stored Google OAuth tokens and your cached Google calendar events. Deleting your myScribe account removes this data as described in Data Retention below.
We do not sell your personal information. We may share data with:
Your data is stored securely using Supabase (PostgreSQL) with row-level security policies. We use encryption in transit (TLS) and implement access controls to protect your information. Audio and video files are stored in encrypted cloud storage.
We retain account-linked content while your account is active unless you delete it or an applicable retention process removes it. To request account deletion, open your avatar → Profile → Delete account → Request account deletion, read the notice, type DELETE and submit. This records a request for human handling; it does not mean erasure or billing cancellation is complete. The request notice describes processing within 30 days, except for legally required retention, and completion is confirmed by email. Provider copies, backups and diagnostic records may have separate retention periods. Withdrawing AI permission is separate from deleting stored data.
Depending on your location, you may have the right to:
To exercise these rights, contact us at privacy@myscribe.co.
myScribe is not intended for children under 13. We do not knowingly collect personal information from children under 13. If we discover we have collected such information, we will delete it promptly.
Our app may integrate with third-party services (Stripe for payments, Google Calendar, Slack, Microsoft Teams, Zoom). These services have their own privacy policies, and we encourage you to review them.
We use essential cookies for authentication and session management. We may use analytics to understand app usage patterns. We do not use advertising cookies or trackers.
We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy in the app or via email.
If you have questions about this Privacy Policy, please contact us: