Privacy Policy

Last updated: June 16, 2026

Overview

Transcript is a local transcription and AI recap app for Mac and iPhone. It records meetings, transcribes audio, and helps you bring transcripts to the AI app or provider you choose. There is no Transcript-operated backend, analytics service, ad network, or telemetry pipeline for recordings, transcripts, prompts, or recaps.

Data We Collect

We do not collect, store, or sell your personal data on our servers. The app stores your recordings, transcripts, recaps, prompts, metadata, and settings on your device.

Google User Data

Google integrations are optional. Transcript uses Google user data only for the user-facing feature you turn on in the app. Transcript does not use Google user data for advertising, analytics, profiling, product analytics, training AI models, or selling data.

  • Google account email: used to show which Google account is connected, separate multiple connected accounts, and help identify your own calendar account during meeting matching.
  • Calendar list: used so you can choose which calendars Transcript may use for meeting matching and reminders.
  • Calendar events: read-only event title, time, attendees, and meeting link are used to detect upcoming or active meetings, show reminders, and attach meeting context to the local recording and recap you create.
  • Google Drive folders: used only when you choose a Drive destination in Cloud Sync. Transcript uploads only the Transcript-created files you select to that chosen folder.

Recordings and Transcripts

  • On Mac, recordings are saved locally in your configured Transcript data folder. The default location is ~/Documents/Transcript-App.
  • On iPhone, recordings are saved in the Transcript Private app container. By default, local audio is deleted after transcription succeeds unless you enable audio retention.
  • Local Whisper transcription processes audio on your device.
  • On iPhone, Transcript Private prepares prompts, copies them to the clipboard, and opens AI apps such as ChatGPT, Claude, or Gemini. You decide whether to paste and send the prompt in that third-party app.
  • On Mac, if you choose a cloud transcription or recap provider, the app or CLI sends the relevant audio, transcript, recap input, or prompt directly to that provider from your Mac.
  • You can delete recordings, transcripts, recaps, and metadata from inside the app. On Mac, you can also delete them from Finder.

Local/Remote Diarization

When Local/Remote diarization is enabled, Transcript writes a hidden .channels/activity.json file next to the recording. This file contains derived RMS and peak activity by second for microphone and system audio. It is not an audio file and cannot reconstruct speech.

Google Calendar Integration

Google Calendar connection is optional and uses OAuth 2.0. When enabled:

  • Transcript requests read-only calendar access and your email address.
  • Calendar data is used to match a recording with the meeting happening at the same time, display meeting context, and infer a local-speaker hint from the calendar account.
  • OAuth tokens are stored in the macOS Keychain and are not sent to any Transcript server. On iPhone, tokens are stored in the iOS keychain.
  • Transcript does not create, edit, or delete calendar events.

Google Drive Integration

Google Drive connection is optional and uses OAuth 2.0. When enabled:

  • Transcript requests Google Drive file access only so you can choose a Drive folder and upload Transcript-created files to it.
  • Depending on your Cloud Sync settings, uploaded files may include recap documents, metadata, transcripts, or audio recordings.
  • Transcript does not browse, index, or read arbitrary files in your Google Drive.
  • Drive folder IDs, display names, selected upload settings, and the connected Google account email are stored locally on your device.
  • Uploaded files remain in your Google Drive until you delete them there. Removing a Drive destination in Transcript removes the local routing configuration; it does not delete existing Drive files.

Google API Services User Data Policy and Limited Use

Transcript'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.

  • Transcript uses Google user data only to provide user-facing features you enable: calendar matching, meeting reminders, local speaker hints, and Google Drive export.
  • Transcript does not sell Google user data, use it for advertising, share it with data brokers, determine credit-worthiness, or use it to train AI models.
  • Google Calendar data is not sent to AI providers unless you explicitly run a Transcript feature that uses calendar context, such as generating a recap or title for that meeting. In that case, only the relevant meeting context needed for that user-requested output may be included in the prompt sent from your device. Transcript does not proxy these requests through a Transcript-operated server.

Retention and Deletion of Google User Data

  • Transcript does not retain Google user data on Transcript-operated servers. Google Calendar and Google Drive data is processed from your device for the optional features you enable.
  • Calendar metadata may be stored locally in meeting metadata or recap files until you delete those local files from inside Transcript or from Finder.
  • Google Drive destination details, such as folder IDs, display names, selected upload settings, and connected account email address, are stored locally until you remove the Drive destination or delete Transcript's local settings.
  • Files uploaded to Google Drive remain in your Google Drive until you delete them there. Removing a Drive destination in Transcript stops future uploads and removes the local routing configuration; it does not delete files already uploaded to your Drive.
  • Google OAuth tokens remain in the macOS or iOS Keychain until you disconnect the account in Transcript, remove the app's local data, or revoke Transcript's access from your Google Account permissions.
  • Transcript protects Google user data using operating-system storage protections, macOS and iOS Keychain storage for OAuth tokens, and HTTPS/TLS connections to Google APIs.

Third-Party Services

Depending on your settings, Transcript may communicate with:

  • Google Gemini API, OpenAI API, Codex CLI, or Claude Code for transcription, recap, title generation, or related AI tasks.
  • Google Calendar API for optional read-only calendar matching.
  • Google Drive API for optional user-selected Drive exports.
  • ChatGPT, Claude, Gemini, or another AI app you open from Transcript Private when you choose to paste and send copied prompt content there.
  • Sparkle and Cloudflare R2 for app update checks and download assets.

Third-party providers process data according to their own terms and policies. Transcript does not proxy these requests through a Transcript server.

Credentials

  • Google OAuth tokens for Calendar and Drive are stored in the macOS Keychain. On iPhone, tokens are stored in the iOS keychain.
  • API keys and local AI tool credentials stay on your Mac in the app settings or the relevant CLI configuration.
  • You can revoke Google access from Transcript settings or from your Google Account permissions.

Children's Privacy

Transcript is not directed at children under 13. We do not knowingly collect information from children.

Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date.

Contact

If you have questions about this Privacy Policy, contact support@transcriptprivate.com.

← Back to home