1. Who we are
MeetSnap (“MeetSnap”, “we”, “us”, or “our”) is an independent, solo-developer software product operating the desktop application and web dashboard available at meetsnap.app. For any privacy question or request, contact us at hello@meetsnap.app. We act as the data controller for the personal information described in this policy.
2. How MeetSnap processes your meeting audio
Understanding our architecture is the key to understanding your privacy. There are three distinct stages:
2.1 Audio capture & transcription (real-time, zero-retention)
When you run a live session, MeetSnap captures audio from your microphone and/or system output and streams it over an encrypted (TLS) connection to our real-time speech-to-text provider, Deepgram, which transcribes it into text. We operate this in zero data retention mode: the audio is processed live and is not stored by us or by Deepgram, and we do not keep recordings of your calls. Only the resulting text continues through the pipeline.
2.2 AI processing (server-side proxy)
Once audio is transcribed to text, that text — together with any context you provide (such as a selected persona, your notes, or attached documents) — is sent securely to our server-side AI proxy. The proxy forwards the text to a third-party large language model provider (OpenRouter) which generates the live answer or summary that is returned to you. Your AI provider API access is handled server-side; clients never hold those credentials.
2.3 Storage & sync (your account)
The text artifacts of a session — transcripts, AI answers, summaries, session titles, timestamps, and related metadata — are stored in our database (Supabase Postgres) and tied to your user account so you can revisit, export, or delete them later, and access them across the desktop and web apps. In short: audio is transcribed in real time and not stored; only the transcribed text and session data is stored.
3. Information we collect
3.1 Account information
When you sign up, we collect your email address and authentication credentials. Sign-in is handled by Supabase Auth using either email/password or Google OAuth. If you sign in with Google, we receive basic profile information (such as your email address and name) from Google to create and identify your account; we do not receive your Google password.
3.1.1 Google user data — access, use, storage, and sharing
When you choose “Continue with Google,” MeetSnap requests only the openid, email, and profile scopes. We receive your Google account’s email address, name, and profile picture URL, and use this data solely to create and authenticate your MeetSnap account and display your name and picture in the app. We store this data on Supabase (our authentication and database provider) for as long as your account exists. We do not share Google user data with third partiesexcept as needed to provide the service (Supabase as our auth/storage provider),do not use it for advertising, do not sell it, and do not use it to train AI or machine-learning models. You can delete your account at any time from Profile → Account, which removes all stored Google account data.
3.2 Session & usage content
We store the content you create or generate through the product: transcribed meeting text, AI-generated answers and summaries, session names and timestamps, personas you configure, notes, and documents you choose to upload for context.
3.3 Billing information
Payments are processed by our merchant of record, Creem. We do not collect or store your full payment card details. We receive limited subscription and transaction metadata (such as plan, status, and billing country) needed to provision and manage your access.
3.4 Technical & diagnostic data
We may collect limited technical information such as app version, device/OS type, error logs, and basic usage events necessary to keep the service running, secure, and reliable. We do not sell this data or use it for advertising.
3.5 Candidate data (HR Interviews module)
The HR Interviews module is different from the rest of MeetSnap in one important way: it processes information about a third party who is not our user — the job candidate being interviewed. We treat that data with the following commitments.
What is stored. When you use HR Interviews we store, in your account: the candidate’s name, optionally their email address, theextracted text of any CV you supply, any tags or notes you add, the interview transcript, the per-answer scores the AI produced with the verbatim quote each score cites, and the resulting hiring report.
CV files never reach our servers. PDF and DOCX parsing happens entirely in your browser. Only the extracted plain text is transmitted and stored. We keep the original filename for your reference; we do not keep the file itself.
You are the controller; we are the processor. You decide which candidates to interview, what to record, and how long to keep it. Under GDPR and comparable regimes you (or your organisation) are the data controller for candidate data, and MeetSnap acts as a processor on your instructions. That means the obligations to establish a lawful basis for processing, and to give candidates the notice required by Articles 13 and 14 GDPR, rest with you and not with us. Our Terms say the same.
What we deliberately do not do. We do not analyse faces, voice tone, accent, or personality, and we do not infer protected characteristics. Scoring runs on the text transcript only. The AI’s recommendation is advisory: a human reads, edits, and decides. We do not use candidate data to train AI models, we do not sell it, and we do not use it for advertising.
Deletion. Deleting a candidate, a session, or your account removes the associated candidate records, transcripts, and hiring reports on the schedule described in section 7. If a candidate contacts us directly asking about their data, we will refer them to the employer who holds it, since we cannot identify which of our customers interviewed them without that employer’s involvement.
4. How we use your information
- To provide the core service — live transcription support, AI answers, summaries, and session history.
- To authenticate you and keep your account secure.
- To sync your sessions and settings between the desktop and web apps.
- To process subscriptions, billing, and entitlements through Creem.
- To enforce usage limits, rate limits, and abuse protections.
- To diagnose problems, improve reliability, and provide support.
- To send essential transactional emails (verification, password reset, billing).
- To comply with legal obligations and protect our rights and users.
We do not sell your personal data, and we do not use your meeting content to train our own models.
5. Third-party processors (sub-processors)
We rely on a small number of trusted infrastructure providers to operate MeetSnap. Each processes data only as needed to deliver their part of the service:
These providers maintain their own privacy and security practices. We encourage you to review their respective privacy policies for details on how they handle data.
Candidate data follows the same path. When you run an HR interview, the candidate’s speech passes through our transcription provider and their answers plus your kit’s competencies pass through our AI provider in order to produce coaching and the hiring report. No additional sub-processor is introduced for the HR module, and CV files are parsed in your browser so they are never transmitted to any of them.
6. Cookies & local storage
We use cookies and browser local storage strictly for essential functionality — primarily to keep you signed in and maintain your authentication session. The desktop app stores configuration and session state locally on your device. We do not use third-party advertising or tracking cookies.
7. Data retention
We retain your account and session data for as long as your account is active so the service remains useful to you. You may delete individual sessions at any time, and deleted content is removed from our active systems. If you delete your account, we delete or anonymize your associated personal data within a reasonable period, except where we are required to retain certain records (for example, billing records) to comply with legal or accounting obligations. Raw audio is never retained — it is transcribed in real time in zero-retention mode and discarded; we keep no recordings of your calls.
Candidate data (HR Interviews). Candidate records, interview transcripts, per-answer scores, and hiring reports are retained for as long as you keep them. Deleting a candidate removes their record and CV text; deleting a session removes that interview’s transcript, scores, and report; deleting your account removes all of it. Because you are the controller for candidate data (section 3.5), deciding how long to keep a rejected candidate’s interview is your call and may be governed by your own retention policy or local employment law. We do not impose a shorter limit, and we do not keep a copy after you delete.
8. Your rights & choices
Depending on your jurisdiction (including under the GDPR and CCPA/CPRA), you may have the right to:
- Access the personal data we hold about you.
- Export your sessions and data in a portable format.
- Correct inaccurate account information.
- Delete individual sessions or your entire account.
- Object to or restrict certain processing.
- Withdraw consent where processing is based on consent.
Much of this is self-serve from within the app. For anything you can’t do yourself, email hello@meetsnap.app and we will respond promptly.
9. Data security
We protect your data using industry-standard measures including encryption in transit, row-level security so each user can only ever access their own records, server-only handling of AI provider credentials, rate limiting, and usage quotas. No method of transmission or storage is perfectly secure, but we take reasonable steps to safeguard your information.
10. International data transfers
Our processors may store and process data in the United States and other countries. Where required, we rely on appropriate safeguards (such as standard contractual clauses) for cross-border transfers of personal data.
11. Children’s privacy
MeetSnap is intended for users who are 18 years of age or older. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us with personal data, contact us and we will delete it.
12. Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date above and, for material changes, take reasonable steps to notify you. Your continued use of MeetSnap after an update constitutes acceptance of the revised policy.
13. Contact us
Questions, requests, or concerns about your privacy? Reach us anytime at hello@meetsnap.app.