Privacy Policy
Short version: we store the text of your interviews and the feedback on them. We store no audio anywhere — we never even receive it.
Updated
Who processes your data
VoiceMock is a private project run by Serhiy Klymkovych (an individual, based in Ukraine). There is no company behind it. For anything about your data, write to sergijklimkovic@gmail.com — the same person who writes the code answers it.
What happens to your voice
This is the section that matters most, so it goes first. Your microphone is handled by your browser through its built-in Web Speech API. Audio is never sent to our server, never written to a file, and never stored.
Your browser does not do the recognition on its own, though: in Chrome and Edge the audio goes to Google servers and comes back as text. That leg is covered by Google’s privacy policy, not ours. What reaches us is already text.
Spoken questions work the other way round: the question text goes to Google Gemini and audio comes back. Your voice is not involved in that direction at all.
What we store
Exactly four categories, with nothing hidden behind them:
- Account. If you sign in with Google — your email, name and avatar URL. We never see or receive your Google password.
- Interview content. The settings you chose (industry, challenge type, company context, language), the generated prompt, and the text transcript of the conversation.
- Feedback. Per-criterion scores, the overall grade, and the recommendations and annotations the AI generated for your answers.
- Matched jobs. Title, company, location, salary and link — what external sources returned for your role.
If you take an interview without signing in, nothing reaches the database at all. That session lives only in your tab’s sessionStorage and disappears when you close it.
Technical data and cookies
- Vercel Analytics — page-to-page movement and product events (for example, whether question generation succeeded). Used to see where people get stuck. Only the last 31 days are available.
- IP address — used solely to rate-limit API requests. It is held in server memory for minutes and never written to the database.
- vm_lang cookie — your interface language.
- Supabase session cookie — keeps you signed in.
- theme in localStorage — light or dark.
There are no third-party advertising or tracking cookies.
Why we need it
- To run the interview and give you feedback — the service you came for.
- To show your interview history and progress in the dashboard.
- To match vacancies to your role.
- To understand which step people drop off at, and fix it.
The legal basis for the first three is performing the service you asked for. For analytics it is the legitimate interest of knowing whether the product works; that data is not tied to your name.
Who we share it with
The services the product cannot run without:
- Google — OAuth sign-in, question and feedback generation via Gemini, spoken questions, and speech recognition inside Chrome.
- Supabase — database and authentication.
- Vercel — hosting and analytics.
- Jooble and jobs.dou.ua — job matching. Only a role keyword is sent: they receive no name, no email and no transcript.
We do not sell your data, do not pass it to advertisers, and do not use your transcripts to train models.
How long we keep it
Account and interview data stays until you delete your account. There is no automatic expiry: interview history is useful precisely because it shows months of progress.
An anonymous interview disappears when you close the tab. Analytics covers 31 days.
Your rights
You can get a copy of your data, correct it, delete it, or object to it being processed.
You can delete everything yourself: in the dashboard open Settings → “Delete account”. Deleting the account cascades to every interview, transcript, grade and matched job. It is irreversible and happens immediately, with no grace period.
For anything else, write to sergijklimkovic@gmail.com — we answer within 30 days.
Age
The service is not intended for anyone under 16, and we do not knowingly collect their data.
Changes
If this policy changes materially, the date at the top of the page changes.