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 access in read-only mode:

• Event titles, start/end times, and durations
• Attendee names and email addresses
• Meeting URLs (Google Meet, Zoom, Teams, etc.)
• Your email address (to identify the connected account)

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 Data Location: Your data may be stored and processed in servers located in different countries. By using the Service, you consent to the transfer of your data to these locations.

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 display upcoming meetings in the LiteScribe desktop app. We access event titles, times, attendee lists, and meeting URLs (e.g., Google Meet, Zoom links). We do not create, modify, or delete any calendar events. Calendar data is cached locally on your device and is not shared with any third parties. 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.

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.readonly - View your calendars
• calendar.events.readonly - View calendar event details
• userinfo.email and openid - Identify the connected Google account

7.2 How We Use Google Calendar Data: We use your calendar data solely to display upcoming meetings within the LiteScribe desktop application, allowing you to start recording and transcribing meetings with one click. We access event titles, start/end times, attendee lists, and conference/meeting URLs.

7.3 Storage and Sharing: Calendar event data is cached locally on your device (in an encrypted SQLite database) and temporarily on our servers for the purpose of delivering it to your app. OAuth tokens (access and refresh tokens) are stored encrypted on our servers. We do not share, sell, or transfer your Google Calendar data to any third party. We do not use Google Calendar data for advertising, AI/ML model training, or any purpose other than displaying your meetings.

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, the names of calendar attendees when matching speakers to names)

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, Anthropic, Groq, DeepSeek, Cohere, and other "Bring Your Own LLM" (BYOLLM) providers. These only receive data when you have explicitly configured your own API key for that provider in LiteScribe settings. When BYOLLM is active, LiteScribe sends requests directly from your device or our server to the provider you chose, using your credentials. That provider's terms and retention policies then apply. LiteScribe does not retain copies of those requests beyond normal request logging needed to operate the service.
  • OpenAI API data-usage policy: https://openai.com/policies/api-data-usage-policies
  • Anthropic commercial terms: https://www.anthropic.com/legal/commercial-terms
  • Groq privacy policy: https://groq.com/privacy-policy/
  • DeepSeek privacy policy: https://chat.deepseek.com/downloads/DeepSeek%20Privacy%20Policy.html
  • Cohere privacy policy: https://cohere.com/privacy

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. 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.
• Bring your own API keys (BYOLLM). You can route AI requests directly to a provider of your choice using your own API key, bypassing our default provider. This is configured in Settings > Integrations.
• 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. For BYOLLM configurations, the retention policy is whatever the provider you chose applies to your API key.

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).

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.