Privacy policy

The short version

• We collect what’s needed to run Snapr: your account, the meetings and notes you capture, and the services you connect.

• We never sell your information or use your meetings for advertising.

• Transcription and AI providers process your content to produce transcripts, notes and answers. Snapr doesn’t use your meetings to train its own general-purpose AI models.

• On-device transcription keeps audio on your device; cloud features send content to us and our providers.

• Delete content or your account at any time, and disconnect any connected service in Settings.

• Questions: support@snapr.so.

1. Who is responsible for your information

Snapr is provided by Workyloop OÜ, registry code 16837036, at Tartu mnt 67/1-13b, Kesklinna linnaosa, Tallinn, Harju maakond, 10115, Estonia. Contact us at support@snapr.so and use “Privacy request” in the subject for questions about your information.

This policy covers Snapr’s website, apps and related services. We are the controller of information used to run accounts, handle billing and support, secure the service and understand product use. When a business or other organisation uses Snapr to process meeting content on its behalf, that organisation generally controls the content and we process it on its instructions. Its own privacy notice and any agreed data processing agreement also apply. Meeting participants can contact the organisation that arranged the recording, or ask us for help directing a request. Your use of Snapr is governed by our Terms of service.

2. Information we handle

Account and workspace information. Your name, email address, profile image, sign-in credentials or linked sign-in account, preferences, workspace membership and permissions. Depending on your sign-in method, we store password hashes, passkey records, authentication factors and session information, rather than your third-party account password.

Meeting and note content. Audio you capture, transcripts, speaker labels and names you supply, meeting titles and participants, notes, action items, tags, folders and sharing settings. Screenshots, saved recordings and documents are included when you capture, keep or upload them. Meeting content may contain personal or sensitive information about you and other people.

Telling speakers apart. In online meetings, Snapr names speakers from the meeting app, calendar invitations and your corrections. For in-person meetings, our transcription provider separates speakers within that one recording by how their voices sound and labels them Speaker 1, Speaker 2, and so on. Snapr does not store voice profiles or use anyone’s voice to recognise them in other meetings.

AI questions and context. Questions, chat history, generated answers, attached files and the meeting passages or other context used to answer. Screen context is included when you use a feature that sends it. Search can create numerical representations of text, called embeddings, to find relevant content.

Connected services. If you authorise a connection, we receive the access tokens and information needed for that connection, such as calendar events and attendees, selected documents, or destinations for sending notes. We receive this from the service you connect. We also receive content from workspace members and people who share it with you.

Billing and purchases. Your plan, purchase status, billing contact, invoices, receipts and transaction identifiers. Payment providers and app stores process payment details; Snapr does not receive your full payment card number from those purchases.

Technical and usage information. IP address, device and app details, session and security events, error reports, feature usage, counts, durations and account or workspace identifiers. Product analytics are designed to exclude meeting text, titles and uploaded content. Support messages contain whatever information you choose to send us.

3. Local storage and cloud processing are different

Where available and selected, on-device transcription processes audio on your device. Local storage keeps the resulting meeting or note on that device. These are separate choices: a locally stored voice note can still send audio to a cloud transcription provider if cloud transcription is enabled.

When you use cloud transcription, audio is streamed to the selected transcription provider. Turning off saved audio does not turn off this processing. When you use sync, cloud notes, Ask, search or sharing, the content needed for those features is sent to Snapr and the relevant service providers. Cloud features can process transcripts, notes, participant names, questions and selected files even if transcription itself happened on-device.

The options available to you depend on your device, plan and workspace policy. Selecting local storage is not a promise that account, billing, diagnostic or usage information never leaves the device. Review the transcription and workspace settings before capturing sensitive information.

4. Why we use information

We use information to provide accounts and workspaces; record and transcribe content as instructed; generate notes and answers; organise, search, sync and share content; operate connections you authorise; manage purchases; answer requests; and maintain and protect Snapr.

Where European data protection law applies, our controller activities rely on:

• Providing a contract: account access, the features you request, billing and service-related support. We need the information relevant to those features to provide them.

• Legitimate interests: protecting accounts, detecting abuse, diagnosing faults, handling enquiries and understanding product performance. We consider the impact on your rights and you can object to processing based on this ground.

• Legal obligations: accounting records, lawful requests and other obligations that apply to us.

• Consent: optional website storage or features where required, and other processing for which we specifically ask permission. You can withdraw consent without affecting processing that was lawful before withdrawal.

For an organisation’s meeting content, the organisation is responsible for choosing the lawful basis and obtaining any required permission from participants. An operating-system microphone or screen permission does not replace that responsibility.

Snapr’s ordinary note and answer features do not make automated decisions that have legal or similarly significant effects on you. AI output can be wrong and should be checked.

5. Who receives information

We share information with providers only as needed for the features you use. These include:

• Cloud infrastructure and website providers: hosting, databases, file storage and website delivery; they handle stored content and technical connection information.

• Speech and AI providers: cloud transcription, generated notes, answers and search; they receive relevant audio, text, questions and attachments.

• Communication and support providers: service emails, push notifications and support chat; they receive contact or device details and the messages needed to deliver those services.

• Security, diagnostics and product analytics providers: service protection, fault investigation and usage measurement; they receive technical events and usage information.

• Payment and subscription providers, including app stores: purchases, receipts and subscription status; they handle the billing and transaction information needed for your purchase.

The services we use today:

• Hosting and storage: Fly.io, DigitalOcean, Cloudflare, Vercel

• AI: Anthropic, OpenAI, Google (Gemini)

• Transcription: Soniox, Deepgram

• Email and notifications: Resend, OneSignal

• Errors and analytics: Sentry, PostHog

• Payments: Stripe, RevenueCat, Apple App Store, Google Play

• Support chat: Crisp

These providers operate in the EEA and other countries, including the United States. Section 6 explains international processing and safeguards. Contact support@snapr.so for the recipients and arrangements relevant to your account or a particular feature.

Our AI integrations process content to deliver the requested features. Snapr does not use your meeting content to train its own general-purpose AI models. Provider retention and data-use terms depend on the service and account configuration; this policy does not promise zero retention across every AI feature.

Workspace members, owners and administrators can access content according to their permissions. People with a share link can access the content covered by that link. Links may remain usable until revoked or until an expiry you set. A recipient can keep a copy independently of Snapr.

Services you connect, including calendar and document tools, messaging services, and external AI clients through MCP, receive information when you authorise access or an action. Their own privacy terms govern their use of it. Disconnecting stops future authorised access through that connection but does not recall copies already sent.

We may disclose information when legally required, to protect people and the service, or as part of a business transfer subject to appropriate safeguards and any required notice. We do not sell personal information or share meeting content for targeted advertising.

Google user data

Google Calendar. If you connect Google Calendar, Snapr reads the events on your primary calendar, read-only: their titles, times, attendees and video-call links. We use them to show your upcoming meetings, remind you before they start, title the notes of meetings you record and name who spoke in them. We don’t keep a copy of your calendar: events are fetched when needed. For a meeting you record, we keep that event’s ID, title and recurring-series ID with the note, and attendee names used to label speakers. Snapr never creates, changes or deletes calendar events.

Google Drive. If you connect Google Drive, Snapr can access only the files it creates or that you choose, to save your notes there.

Google user data is not sold, not used for advertising and not used to train AI models. It is shared with the providers listed in this section only as needed to provide these features. You can disconnect Google at any time in Snapr’s settings, which deletes our stored access token and revokes it at Google, or remove Snapr’s access in your Google Account.

Snapr’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.

Slack

If your workspace connects Slack, Snapr stores the workspace’s ID and name, an access token for its bot (encrypted), and the channels you choose as destinations. It reads channel names only to list them for you, and posts only what someone sends — a meeting’s recap or a draft — never the transcript. Snapr does not read messages in your Slack workspace. Disconnecting Slack in Snapr’s settings revokes the token in Slack.

6. Where information is processed

Snapr uses providers in the European Economic Area and elsewhere, including the United States. A provider may use infrastructure or support staff in more than one country. EU hosting for one part of Snapr does not mean that every AI request, email, notification or support operation stays in the EU.

For transfers subject to European data protection law, the applicable arrangement must provide a lawful transfer mechanism, such as an adequacy decision or European Commission Standard Contractual Clauses, with additional safeguards where needed. Contact us for information about the safeguards applicable to your use and how to obtain a copy. We do not represent that every provider or feature has the same data residency or retention terms.

7. How long information stays

Meeting content and workspace records generally remain until an authorised user deletes them or the relevant account or workspace is deleted. Cancelling a subscription does not automatically delete content. Local copies are managed on your device and may remain in device backups. Copies you export or send to another service are controlled separately.

The current service schedules removal of:

• Unsent Ask uploads: after 1 day.

• Files attached to Ask: after 90 days from upload. The chat, extracted context and answers may remain with the conversation; removing the file does not erase information already included in an answer.

• Generated workspace export files: after 7 days.

• Ended or expired sessions: after 30 days.

• Expired sign-in codes, reset links and similar credentials: after 30 days from expiry or revocation, as applicable.

• Security audit events: after 365 days.

These are scheduled cleanup periods, not a guarantee of deletion at an exact minute. Stored file deletion runs separately from deleting its database record. Backups, security investigations, legal obligations and provider-side retention may require information to remain for longer, with access restricted to the relevant purpose.

We retain accounting records for the applicable statutory period. Support correspondence is kept for handling the request, necessary follow-up and any related dispute or legal obligation. Diagnostic and analytics information is governed by the relevant provider’s configured retention and our need to investigate faults and understand usage. Contact us if you need information about a specific record or retention period.

Deleting your account also deletes your personal workspace and associated personal content, subject to the exceptions above. Team meetings and other team records remain with the team. Limited attribution, including your name where needed for those records, may remain until the team deletes them. A team’s only owner must transfer ownership or delete that workspace before account deletion can proceed.

8. Cookies and similar storage

We use cookies and browser storage for functions such as sign-in, security and remembering choices. Necessary storage is not optional where it is required to provide the service you request. Signing out or clearing browser storage may affect access and preferences.

On the marketing website, the Cookie settings control lets you manage optional external media. Embedded video services can receive your IP address and browser details and use their own cookies or storage when enabled. Essential site delivery and self-hosted media do not depend on accepting these optional features. No marketing analytics or advertising tracker is included in the current marketing-site implementation.

The website stores your choice in snapr-cookie-preferences in this browser for up to 180 days. You can reopen Cookie settings on this Privacy page and change it. Clearing browser storage, using another browser, or a material change in the optional services may require a new choice. If storage is blocked, your choice can only last for the current page session.

The signed-in web app is a separate surface. It uses authentication cookies and, where configured, product analytics cookies and local storage. The marketing website’s cookie choice does not currently control native-app, signed-in web-app or server-side analytics. You can contact us to object to analytics processing or ask about the controls applicable to your account.

Support chat is provided by Crisp and loads only after you select Open chat. Opening the support panel or accepting optional video cookies does not load Crisp. Once opened, chat uses cookies and related storage to maintain the conversation you requested; we configure its session cookie to last up to 30 days on the current website host. Crisp may continue to connect while you browse this website after opening chat. Closing the chat window minimises the conversation; it does not erase the conversation or its cookies. The external-media choice does not control chat you have explicitly opened. You can use support@snapr.so instead without loading Crisp. See Crisp’s chat cookie information for its technical storage behavior, and contact us for requests about support records.

9. Your choices and rights

You can change available settings, disconnect integrations, revoke share links, and use the export and deletion controls your account permissions allow. Workspace-wide exports are controlled by the workspace owner. For local-only content, use the app’s local controls; we cannot retrieve content that has never been sent to us.

Depending on the law that applies, you may have rights to access, correct, delete or receive a portable copy of personal information, restrict processing, object to processing based on legitimate interests, and withdraw consent. These rights have exceptions, including legal retention obligations and the rights of other people.

Email support@snapr.so to make a request. We may ask for proportionate information to verify your identity. If an organisation controls the information, we may direct the request to it and help it respond. Under the GDPR, we normally respond within one month; if a lawful extension is needed, we will explain it within that period.

You may complain to your local data protection authority or the Estonian Data Protection Inspectorate. You do not have to contact us first.

10. Security and children

We use safeguards such as encrypted connections, access controls and session management to protect information. No service can guarantee absolute security. Keep your devices and credentials secure and consider what is visible before capturing a screen or sharing a link.

Snapr accounts are intended for adults aged 18 or over. We do not knowingly invite children to create accounts. If you believe a child has provided information inappropriately, contact us. Information about children included in a customer’s meeting remains subject to that customer’s responsibilities and applicable law.

11. Changes to this policy

We update this policy when our practices change. The date at the top identifies the latest version. For material changes, we will provide additional notice through the service or by email where appropriate, and seek consent where required. Questions are welcome at support@snapr.so.