Privacy Policy

This policy explains what data Alt processes across the website, desktop app, iOS app, and Android app, when external transfer can occur, and what controls users have. This policy applies equally to all platforms (web, desktop, iOS, and Android).

At A Glance

1. Scope and Definitions

This policy applies equally to all platforms listed below.

• Desktop App: Alt application running on macOS and Windows
• iOS App: Alt application running on iPhone and iPad
• Android App: Alt application running on Android phones and tablets
• Website: altalt.io features including account, billing, download, and sharing
• LocalLLM Mode: AI processing handled on-device
• API Mode: AI processing handled through our servers and integrated API providers

2. App (Desktop, iOS, and Android) Data Processing

The following applies equally to the desktop app, iOS app, and Android app.

2.1 Always Local Processing

• Speech recognition (STT) runs locally using the on-device speech recognition model.
• Recordings, transcripts, and generated outputs are primarily stored on your device.

2.2 Optional AI Processing (LocalLLM/API)

• AI features include summarization, chat, AI scribe, translation, and note title generation.
• LocalLLM: Processing remains local and can be fully offline. When using LocalLLM mode or when API mode is not selected, no data is transmitted externally.
• API: Only when you choose to use API-based AI features and complete the necessary consent process, transcript text and memo content may be transmitted to OpenAI, Anthropic, and Google to perform your requested features such as summarization, translation, AI scribe, note title generation, and chat. The audio recording files themselves are not transmitted to these third-party AI providers.

2.3 Prior Consent Process

• Before using API mode, the app displays an in-app consent prompt that clearly states: (1) what data is transmitted (transcript text and memo content), (2) who receives it (OpenAI, Anthropic, Google), and (3) for what purpose (performing the AI feature you requested, such as summarization, translation, or title generation).
• Data transmission begins only after you explicitly consent through the in-app prompt.
• You may disable API mode at any time to stop data transmission.

2.4 Server Processing and Retention

• Our server acts solely as a relay — it forwards your request to the third-party AI service provider and returns the response.
• User input data (transcript text, memo content) is not stored long-term on our servers and is discarded once the request is processed. However, minimal technical logs may be temporarily generated for service operation, security, and troubleshooting. We ensure these logs do not contain the full content of your AI feature inputs.
• Each AI service provider maintains equivalent levels of data protection consistent with industry standards.

3. Google API User Data (Google Calendar and Gmail)

Connecting Google Calendar and connecting Gmail for sending are each optional and occur only after you explicitly grant permission on Google's OAuth consent screen. Gmail is connected separately, when you add a step that sends email to an automation in the desktop app.

3.1 Google User Data We Access

• Your Google Account email address, OAuth access and refresh tokens, and granted scopes
• Calendar-list data such as calendar IDs, names, primary-calendar status, and display colors
• Calendar-event data such as event IDs, titles, start and end times, all-day status, location, meeting or conference links, and your attendance response status when available
• Gmail sending: for each email an automation you created sends, we pass its To, Cc, and Bcc addresses, subject, and body to the Gmail API and receive the message ID and thread ID Gmail returns. We use only the send-only scope (gmail.send), so we do not read your inbox, existing messages, or contacts.

3.2 How We Use Google User Data

• Link the Google Account you choose to your Alt account and display its connection status
• Display your calendars and upcoming events inside Alt
• Exclude events you declined and let you create or link an Alt note from an event you select
• Send email from your Gmail account to the recipients set in an automation you created and turned on

We use Google user data only to provide or improve these user-facing features. We do not use it for advertising, ad targeting, credit assessment, or unrelated profiling, and we do not use it to develop, improve, or train generalized AI or machine-learning models.

3.3 Google User Data Retention Periods

We retain Google user data only for the periods stated below. When each retention period ends, we delete or destroy the applicable data unless a longer retention period is required by law.

• We store your Google Account email, granted scopes, connection status, and encrypted refresh token on our server only while your calendar remains connected. We delete this data and the connection record when you disconnect Google Calendar, delete your Alt account, or we detect that you revoked Alt's access through Google.
• Google access tokens are not stored in a database or other persistent storage. An access token is held only in server memory while processing each Google API request and is discarded when the request completes.
• Calendar-list and event data is retrieved from Google on demand and is not stored in a database or other persistent storage on Alt's server. The desktop app holds the latest calendar snapshot only in memory, replaces it when refreshed, and discards it when you disconnect, sign out, or close the app.
• If you create an Alt note from an event, the event title, event ID, and start and end times become part of that Alt note. Like other note data, this information may be stored on your device and in your cloud-sync storage until you delete the note or your Alt account.
• For a Gmail connection, we store your Google Account email and an encrypted refresh token on our server only while it remains connected, and delete them when you disconnect it, delete your Alt account, or we detect that you revoked Alt's access through Google.
• The recipients, subject, and body of an email an automation sends are not stored on Alt's server: they are passed to the Gmail API and discarded. Google keeps the sent email in your Gmail Sent folder, and the automation that sent it and its run history are stored on your device.

3.4 Sharing, Transfer, and Disclosure

Google user data is transferred only between Google APIs, Alt's server, and your authenticated Alt desktop app to provide the calendar integration and Gmail sending. An email an automation sends goes only to the recipients you set in that automation. Our infrastructure providers, including Supabase, Cloudflare, and AWS-hosted synchronization infrastructure, may process encrypted connection records and synchronized note data solely to operate and secure the service on our behalf.

We do not sell Google user data or share or transfer it to advertising platforms, data brokers, or information resellers. We also do not send Google user data to analytics services for advertising or advertising measurement.

Alt's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. See the Google API Services User Data Policy.

3.5 Data Protection

• We use HTTPS/TLS to protect data in transit.
• Google refresh tokens are encrypted at rest using AES-256-GCM.
• Tokens are protected by server-side access controls and database row-level security and are never exposed to the desktop app.
• We request only the minimum read-only Google Calendar scopes needed for the integration.
• For Gmail we request only the send-only scope (gmail.send), separately, when you add Gmail sending to an automation.

3.6 How to Delete Google User Data

• You can disconnect Google Calendar from Alt at any time. On disconnect, we revoke the Google token and delete the stored Google email, token, scopes, and connection record from our server.
• You can disconnect Gmail at any time. On disconnect, we delete the stored Google email, token, and connection record from our server and revoke the Google token.
• If one Google Account is connected for both Calendar and Gmail, revoking a token can end the other connection too, so disconnecting only one of them deletes that connection's stored token without revoking it; disconnecting the remaining one revokes it. You can remove Alt's access at any time in your Google Account settings.
• If we detect that you revoked access in your Google Account, we delete the stored connection record.
• Deleting your Alt account also deletes the stored Google connection record.
• Disconnecting does not automatically delete Alt notes you previously chose to create from calendar events. You can delete those notes, including the copied event information, by deleting the note or your Alt account.
• You may also request deletion of Google user data by emailing [email protected]. After verifying your identity, we delete the applicable data without undue delay unless retention is required by law.

4. External Integrations (API Keys and the MCP Connector)

Alt lets an external tool read your note data only when you connect that tool yourself. There are two ways to connect: an API key you issue in your account settings, and the MCP connector, where a client such as Claude is granted access through an OAuth 2.0 consent screen. Both are off by default, and no note data is read until you issue a key or approve the consent screen yourself.

4.1 Data Shared with the Connected Tool

A connected client can read the following data on a read-only basis, limited to the scopes you approved.

• Note list and metadata: note ID, title, created and updated timestamps, transcript and summary readiness
• Note transcript text
• AI-generated note summary

Audio recording files are never shared. The integration has no ability to create, modify, or delete notes, and only notes with a finished recording or a generated summary are exposed.

4.2 What We Store

• API keys and OAuth access and refresh tokens: we never store the raw value. Only an HMAC-SHA256 digest, computed with a server-side secret, is retained.
• Registration details of the connected client (client name, redirect URIs) and the scopes you approved
• Request metadata: timestamp, tool name, response status code, and usage counts, used only to operate and secure the service and to manage usage.

Note content (transcripts and summaries) is not copied or retained for the integration. It is read from existing storage at request time and returned to the connected client.

4.3 Third-Party Disclosure

The third party receiving data through this path is the client you connected yourself, such as Anthropic Claude. Once data reaches that client, its own privacy policy governs further processing. We do not sell data accessed through an integration, do not disclose it for advertising, and do not use it to train models.

4.4 Retention

• OAuth access tokens: 10 minutes from issuance
• OAuth refresh tokens: 30 days from issuance, rotated on every use, with the previous token invalidated immediately
• API keys: until you delete them
• Request metadata: retained only as long as needed for operations, then deleted or de-identified

4.5 Disconnecting

You can revoke any connection or delete an API key at any time from the integrations screen in your account settings. Revoking immediately invalidates the tokens issued to that client and blocks further access.

5. Slack Integration

The Slack integration works only after you install the Alt app in a Slack workspace and link it to your Alt account. Alt can reach only what the permissions you approved on Slack's consent screen allow, and only content you can already see in Slack.

5.1 What We Store

• The workspace ID and name, your Slack user ID, and the permissions you granted
• The tokens Slack issues (a bot token and a user token), encrypted with AES-256-GCM and kept on our servers only. They are never sent to Alt's apps or to you. The HMAC hashing in 4.2 applies to keys Alt issues, not to Slack tokens.

5.2 How We Use It

• Note sharing: Alt posts a note's summary and a link to the note to the channel you choose.
• Automations: when an automation you set up runs, Alt reads or searches the channels, conversations, canvases and files you chose, with your permissions, and sends messages as you or updates canvases and lists where you told it to.

What an automation reads from Slack is used only for that run and is not stored or logged, except what your automation adds to your note, which stays with that note. Slack data is never used to train models, sold, or used for advertising.

5.3 AI Processing

For a step where AI writes, the Slack content that step needs is sent to the AI model provider you selected (by default an OpenAI model through Vercel AI Gateway). It is handled under that provider's API policy and is not used for training.

5.4 Slack's Free Plan

For workspaces on Slack's free plan, automation features are off and the user token is revoked right after connecting. Note sharing still works.

5.5 Retention and Disconnecting

Connection details and tokens are kept until you disconnect Slack in Alt, remove the Alt app from your workspace, or delete your Alt account. Disconnecting in Alt deletes the connection and revokes your user token in Slack. When the app is removed or Slack revokes a token, Alt deletes the affected connection details and tokens as soon as Slack notifies it. To access, transfer, or delete your data, contact us using the details below.

6. Information We Collect on the Website

7. How We Use Information

• Provide and operate the service
• Authenticate users and maintain security
• Process billing/subscription and related accounting
• Handle customer support requests
• Improve product quality and build new features
• Comply with legal obligations

8. Third-Party Processors

We do not sell personal data.

9. International Transfers

Data may be processed in countries where our infrastructure/providers operate (for example Supabase, Stripe, Google Analytics, PostHog, and Resend). When API mode is selected in the desktop or mobile (iOS/Android) app, AI requests may also involve international processing by integrated API providers.

10. Retention

• Account data: until account deletion
• Payment records: retained as required by applicable law (for example up to 5 years)
• Leaderboard data: until deletion request or while required for service operation
• Feedback/support data: deleted or de-identified after purpose fulfillment
• Analytics data: retained within operational needs, then deleted or de-identified

11. Your Rights

• Access your personal data
• Request correction, deletion, or restriction of your data
• Withdraw consent and make privacy inquiries
• Control data transfer in the desktop or mobile (iOS/Android) app by choosing LocalLLM or API mode

To exercise these rights, contact [email protected].

12. Children's Privacy

Our services are not intended for children under 14. We do not knowingly collect personal information from children under 14 and will delete such data if identified.

13. Policy Changes

This policy may be updated due to legal, product, or operational changes.

14. Contact