Privacy Policy

2.1 Account Information: When you create an account, we collect:

• Email address
• Name (if provided)
• Password (encrypted)
• Profile information

2.2 Content You Upload: We process and store:

• Audio and video files you upload
• Transcripts generated from your content
• Metadata associated with your files
• Cloud storage files accessed through integrations

This includes any screenshots you choose to capture via the in-app Screenshot-to-Notes feature, which are stored securely in your account and never sent to AI providers or shared with third parties.

2.3 Calendar Data (with your consent): If you connect your Google Calendar or Microsoft Outlook, we read, in read-only mode, from the calendars you choose to show:

• Event titles and start and end times
• The organizer, and attendee names and email addresses
• Meeting URLs (Google Meet, Zoom, Teams, etc.)
• The id of each event and of the recurring series it belongs to
• Your email address (to identify the connected account)

The LiteScribe apps (web, desktop, browser extension and mobile) show these events, upcoming and past, for up to 62 days at a time. Our servers fetch the events from Google or Microsoft when an app asks for them and pass them to that app; we do not keep a copy of your calendar. We do keep on our servers:

• Which of your calendars you chose to show
• When you record a meeting you started from a calendar event: the event title (as the recording's name), the attendee names and email addresses, and the ids of the event and its series, saved with that recording. We use them to name the speakers, to file the recording into a collection, and to find your earlier meetings with the same people.
• When you choose to file every meeting in a calendar series into a collection: the series id and the collection it goes into

2.4 Usage Information: We automatically collect:

• Usage statistics and analytics
• Device and browser information
• IP address and location data
• Cookies and similar tracking technologies
• Service interaction logs

2.5 Payment Information: When you make a purchase, our payment processors collect billing information. We do not store full credit card details on our servers.

4.1 Security Measures: We implement industry-standard security measures to protect your data, including:

• Encryption in transit (SSL/TLS)
• Encryption at rest for sensitive data
• Secure authentication and access controls
• Regular security audits and updates
• Secure cloud infrastructure

4.2 Data Retention: We retain your data for as long as your account is active or as needed to provide the Service. You may request deletion of your data at any time, subject to legal and contractual obligations.

4.3 Where your data is processed and stored

Your recordings and transcripts are processed and stored in the EU.

Payments are handled by Stripe and calendar connections by Google. They only see payment and calendar data, never your recordings or transcripts.

We do not sell your personal information. We may share your information only in the following circumstances:

5.1 Service Providers: We may share information with third-party service providers who perform services on our behalf, such as:

• Cloud storage providers (Supabase, Cloudflare)
• Payment processors (Stripe)
• Transcription service providers (AssemblyAI)
• Analytics providers (Google Analytics)
• Email service providers

5.2 Legal Requirements: We may disclose information if required by law, court order, or government regulation, or to protect our rights, property, or safety.

5.3 Business Transfers: In the event of a merger, acquisition, or sale of assets, your information may be transferred to the acquiring entity.

5.4 With Your Consent: We may share information with your explicit consent or at your direction.

Our Service integrates with third-party services, including:

• Google Calendar: With your explicit consent via OAuth, we access your Google Calendar data in read-only mode to show your meetings, upcoming and past, in the LiteScribe apps, so you can start recording a meeting with one click. We access event titles, times, the organizer, attendee names and email addresses, event and series ids, and meeting URLs (e.g., Google Meet, Zoom links). We do not create, modify, or delete any calendar events. When you record a meeting from your calendar, we keep its title, attendees and event ids with that recording, as described in Section 2.3. Calendar data is not shared with third parties, except that the AI features you use on a meeting send its title and attendee names to our AI provider, as described in Sections 7.3 and 8. You can disconnect Google Calendar at any time from Settings > Integrations, which immediately stops all calendar data access.
• Microsoft Outlook Calendar: With your explicit consent via OAuth, we access your Outlook Calendar data in read-only mode for the same purpose and under the same conditions as Google Calendar above.
• Google Drive, Dropbox, OneDrive: For cloud storage access. These services have their own privacy policies.
• AssemblyAI: For transcription services. See AssemblyAI's privacy policy for their data practices.
• Stripe: For payment processing. Payment data is handled according to Stripe's privacy policy.
• Google Analytics: For usage analytics. Data is anonymized and aggregated.
• AI assistants you connect (such as Claude, ChatGPT, Cursor and VS Code): Only after you sign in and approve, a connected app can read your recordings as described in Section 8.9. That app's own privacy policy governs what it does with the data.

We encourage you to review the privacy policies of these third-party services.

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

7.1 Scopes Requested: LiteScribe requests the following Google OAuth scopes:

• calendar.calendarlist.readonly - See the list of calendars you are subscribed to, so you can choose which ones LiteScribe shows
• calendar.events.readonly - View the events on those calendars (title, times, attendees and meeting link)
• userinfo.email and openid - Identify the connected Google account
• drive.file - Open only the Google Drive files you pick in the Google Picker

7.2 How We Use Google Calendar Data: We use your calendar data solely to:

• Show your meetings, upcoming and past (up to 62 days at a time), in the LiteScribe web, desktop, extension and mobile apps, so you can start recording and transcribing a meeting with one click
• Keep a meeting's title, attendees and event and series ids with the recording you make of it, so we can name the speakers and file the recording into a collection, including every meeting in a series when you ask for that
• Write a "Prep me" brief for an upcoming meeting, only when you ask for one

We access event titles, start/end times, the organizer, attendee names and email addresses, event and series ids, and conference/meeting URLs.

How We Use Google Drive Data: LiteScribe can open only the audio and video files you choose in the Google Picker. We download each file you pick so we can transcribe it, and store it in your LiteScribe account like any file you upload, until you delete it. We cannot see or list any other file in your Drive.

7.3 Storage and Sharing: Our servers fetch your calendar events when one of your LiteScribe apps asks for them and pass them to that app; we do not keep a copy of your calendar. The desktop app also keeps your upcoming events on your device for its reminders. We keep on our servers only what Section 2.3 lists: the calendars you chose to show, the title, attendee names and email addresses, and event and series ids of each meeting you record from your calendar (saved with that recording), and the calendar series you chose to file into a collection. Disconnecting your calendar stops all new access but does not remove these details from recordings you already made. This data and your OAuth tokens (access and refresh tokens) are stored on our servers in a database that is encrypted at rest. We do not sell Google user data, use it for advertising, or use it to develop, improve or train generalized AI or machine learning models.

When you start a meeting from a calendar event and use an AI feature on that meeting (for example enhanced notes or naming the speakers), the event title and attendee names are sent with that meeting's transcript to the AI provider that produces the result, as described in section 8. When you click "Prep me" on an upcoming meeting, its title, start time and attendee names (or an attendee's email address when the invitation has no name) are sent to the AI provider, together with the summaries and open action items of up to five of your earlier recordings with the same people, to write a short brief. Nothing is sent unless you click it. Each of these happens only to provide the feature you asked for, and under terms that do not allow the provider to train on it. We do not otherwise transfer Google user data to any third party, except where needed to comply with the law or as part of a merger, acquisition or sale of assets with notice to you.

No person at LiteScribe reads your Google user data unless you ask us to (for example in a support request), it is needed for security purposes such as investigating abuse, or it is required by law.

7.4 Revoking Access: You can revoke LiteScribe's access to your Google Calendar at any time by:

• Disconnecting from Settings > Integrations in the LiteScribe app
• Revoking access from your Google Account permissions page

Upon disconnection, we deactivate stored tokens and stop all calendar data access. You may request full deletion of stored tokens by contacting [email protected].

LiteScribe offers optional AI-assisted features that process your transcript text and notes through third-party AI providers. This section explains exactly what data is sent, to whom, for what purpose, and how you can control it.

8.1 What data we send to AI providers

Depending on which AI feature you use, we may transmit:

• The transcript text of the recording or meeting the feature is acting on
• The meeting notes you have typed (including any images you have attached, in the case of future vision-enabled features)
• Your questions and prompts typed into the AI chat or "Ask Anything" bar
• A small amount of context metadata (for example, a calendar meeting's title and attendee names when matching speakers to names or writing a "Prep me" brief, or an attendee's email address when the invitation has no name)

We do not send your audio files, your account email, your payment information, or any other personal data to AI providers. Audio itself is only sent to our transcription provider (AssemblyAI) for the purpose of producing the transcript.

8.2 Which features send data to which providers

8.3 Who the providers are and how they handle your data

• AssemblyAI (transcription and the LiteScribe LLM gateway). LiteScribe uses AssemblyAI on a paid API tier. AssemblyAI's API terms state that submitted content is not used to train their models. See https://www.assemblyai.com/legal/privacy-policy.
• Google (Gemini via the Google AI / Vertex AI API). LiteScribe uses Google's paid API tier. Under Google's Generative AI APIs terms, prompts and responses from paid API usage are not used to train Google's models. See https://ai.google.dev/terms and https://cloud.google.com/terms/generative-ai/.
• OpenAI and Anthropic (GPT and Claude models). These receive data only when you pick one of their models, and only through the LiteScribe LLM gateway on AssemblyAI's paid tier.
  • OpenAI API data-usage policy: https://openai.com/policies/api-data-usage-policies
  • Anthropic commercial terms: https://www.anthropic.com/legal/commercial-terms

In all cases, we use the providers' paid API tiers, on which the providers contractually commit not to train their models on data submitted by API customers.

8.4 What each provider does with your data

AI providers receive your data only in order to generate the response we ask them for. The response is returned to LiteScribe, the response is stored in your LiteScribe account as part of the relevant transcript or meeting note, and the original request is not retained by LiteScribe after the response is received. A "Prep me" brief is not saved to your account; we keep it for up to six hours so that asking again does not send the same request twice. We do not permit AI providers to use your data for training, advertising, or any other purpose. We link to each provider's terms above so you can independently verify their practices.

8.5 Your controls

• Opt out of AI features entirely. You can decline the AI consent dialog on first run of the desktop app, or disable AI features from Settings at any time. With AI features disabled, no data is ever sent to AI providers; transcription (AssemblyAI) still operates if you choose to use it.
• Delete your data at any time. Deleting a transcript, note, or chat conversation from LiteScribe removes it from both your local device and our servers. Transcript content is then no longer available to any AI feature.
• Review what has been processed. Each transcript and meeting note shows the AI-generated content visually distinguished from your own input, so you can always see exactly what the AI has added.

8.6 Retention

• LiteScribe's retention: We retain transcripts, notes, and chat histories for as long as your account is active, or until you delete them. Deletions are effective immediately on our primary storage and propagate through our backup systems within 30 days. AI request/response pairs are stored as part of the associated transcript or note; there is no separate long-term log of AI prompts.
• Provider retention: We configure AI providers for zero or minimal retention wherever the provider offers that option on their paid API tier. Google, AssemblyAI, OpenAI, and Anthropic all publish their own retention policies for paid API usage, linked above.

8.7 Children

LiteScribe is not intended for children under 13, and AI features in particular should not be used by minors without parental consent. See Section 11 (Children's Privacy).

8.8 Free transcriber without an account

On litescribe.ai/audio-to-text you can transcribe one file a day, up to 10 minutes long, without creating an account.

• What we receive: the audio or video file you choose, its file name, the language you pick, and the transcript we produce from it.
• Who processes it: the file is sent to our transcription provider, AssemblyAI, under the paid API terms described in 8.3. We delete AssemblyAI's copy of the transcript as soon as we have stored the result.
• How long we keep it: we delete the file, its name and the transcript 24 hours after you upload it, and a storage rule removes any file left behind after 2 days. After that we keep only a record that a job ran, its length and its cost, with no content.
• Daily limit and abuse prevention: to enforce the one-file-a-day limit we store a keyed hash of your IP address and of a random device identifier kept in your browser. We do not store your IP address itself. Cloudflare Turnstile checks that the request comes from a person; see Cloudflare's privacy policy.
• Saving the transcript: if you create a free account within 24 hours in the same browser, you can move the transcript into your account. It is then kept like your other transcripts (8.6).

8.9 AI assistant connections

You can connect AI apps such as Claude, ChatGPT, Cursor and VS Code to your LiteScribe account through our MCP server at mcp.litescribe.ai. This section explains what a connected app can access and how you stay in control.

• What a connected app can read: Details of your recordings (such as title, date, length, source, language and speakers), transcripts, summaries, action items and folders. An app gets this access only after you sign in to LiteScribe and approve the connection.
• Changes are optional: If you allow changes when you connect, the app can also rename a recording, move it to another folder or create a share link, and it asks you before each change. No connected app can delete anything.
• Local Mode: Local Mode recordings that were never synced to your account stay on your device and are not visible to connected apps.
• Sign-in and access tokens: You connect with your LiteScribe sign-in, not an API key. Access tokens are short-lived and are stored hashed by our authorization server, which runs on Cloudflare.
• Disconnecting: The Integrations page in LiteScribe lists every connected app. You can disconnect any of them at any time, which ends its access.
• What the connected app does with your data: The AI app does the reasoning. For these requests LiteScribe returns the data the app asks for and does not send it to its own AI model. What the app then does with that data is governed by the app's own terms and privacy policy.
• What we log: To keep the service secure and prevent abuse, we log which tool was called, by which connected app and when. We do not log the content.
• No model training: We do not use your data to train AI models.

Setup steps and the full list of tools are on the Claude, ChatGPT and MCP pages.

You have the following rights regarding your personal information:

• Access: Request access to your personal data
• Correction: Update or correct inaccurate information
• Deletion: Request deletion of your data
• Portability: Request a copy of your data in a portable format
• Opt-Out: Unsubscribe from marketing communications
• Account Closure: Delete your account and associated data

To exercise these rights, please contact us at [email protected] or use the account settings in the Service.

We use cookies and similar technologies to:

• Authenticate your session
• Remember your preferences
• Analyze Service usage
• Improve user experience

You can control cookies through your browser settings. However, disabling cookies may limit some Service functionality.