Does VoiceSnap Pro set any cookies at all?

No. There are no cookies on voicesnap.pro — not first-party, not third-party, not analytics, not advertising. The only things the site writes to your browser are the localStorage values listed on this page, which remember a setting or script in a tool you used, and the speech model the audio-to-text tools cache. YouTube players on some blog posts may store data of Google's own.

Is localStorage the same thing as a cookie?

No, and the difference matters. A cookie is attached to every request your browser makes to the domain that set it, so the server sees it constantly. A localStorage value is never sent anywhere: it sits in your browser, readable only by pages on voicesnap.pro, until you or the site removes it. We never read these values on the server, because the server never receives them.

Why do I not get a cookie consent banner?

Because consent is required for storage that is not necessary, and what we write is not that. Each value records a choice you already made — setting up a tool you are using — which is exactly the kind of strictly necessary storage that does not need a banner. The one exception is the YouTube player on some blog posts: it is Google's, it loads with the page, and we do not currently ask before it does. If you would rather it did not load, block youtube-nocookie.com in your browser or content blocker.

How do I delete what VoiceSnap Pro has stored in my browser?

Clear site data for voicesnap.pro in your browser settings, or open the site in a private window so nothing persists. Every value is removed instantly. The tools forget their settings and cached data.

Do the free browser tools store anything?

A few do, in your browser only: the alt-code finder remembers your platform and recent symbols, the decibel meter its calibration, the pitch detector its tuning reference, and the teleprompter your script, so it survives a refresh. The audio-to-text converters cache the speech model they download. None of it is sent to us. Most tools process what you paste or record entirely in the page; the voice-typing tools are the exception, because they use your browser's own speech recognition, which in Chrome sends the audio to Google.

Does buying Pro add cookies to this website?

No. You subscribe to Pro inside the app, which opens Polar's checkout in your browser on Polar's own website; the customer portal works the same way. Any cookies there are set by Polar, under its own policy, not by voicesnap.pro. If we ever add something to this website that sets a cookie, this page is updated before it goes live, with the provider named and the cookie described.

Legal

Cookie Policy

Short version: this site sets no cookies. Here is exactly what is stored in your browser instead, and why we do not show you a consent banner.

Last updated 2 October 2026

The short version

voicesnap.pro sets no cookies — not first-party, not third-party, not advertising, not analytics.
Analytics run through Fathom, which is cookieless and builds no profile of you.
A few free tools use your browser's localStorage to remember settings or a script you entered. None of those values is sent anywhere.
The one third-party embed is YouTube videos on some blog posts, which load Google's player and may store data of Google's own.

What is stored in your browser

localStorage is not a cookie. It is never attached to a network request, it is readable only by pages on voicesnap.pro, and it never leaves your device. The values we write remember a setting or script in a free tool you used.

Name	What it is for	How long it stays
`voicesnap.altcodes.os and voicesnap.altcodes.recent`	Whether the alt-code finder shows Windows or Mac codes, and the last few symbols you copied from it.	Until you clear site data for voicesnap.pro.
`voicesnap.decibel-meter.calibration.v1`	The calibration offset you set in the decibel meter, so its readings match your reference.	Until you reset the calibration or clear site data.
`voicesnap:pitch-detector:a4`	The tuning reference (for example 440 Hz) you picked in the pitch detector.	Until you clear site data for voicesnap.pro.
`voicesnap:teleprompter:v1`	The script you typed into the teleprompter and its display settings, so a refresh does not lose them. This one holds your own text.	Until you clear site data for voicesnap.pro.
`Cache Storage (speech model)`	The audio-to-text converters download a Whisper speech model from Hugging Face and a code library from jsDelivr, and your browser caches them so the next transcription starts faster.	Until you clear site data, or your browser evicts it.

If you never use these tools, none of these values are written. Nothing here is sent to us or to anyone else. Most entries are settings; the teleprompter entry holds whatever text you typed into it.

We do not set cookies

There is no cookie on voicesnap.pro. No advertising cookie, no remarketing pixel, no ad network tag. We do not run a session recorder, a heatmap tool, a chat widget or a customer-data platform. The one place a third party loads anything into a page is the blog, where some posts embed YouTube videos; that is described below.

No advertising, remarketing or conversion cookies, and no ad network tags.
No cross-site tracking pixels from social networks or ad platforms.
No session recording, heatmaps or mouse-movement capture.
No chat widgets or comment systems. The only third-party embeds are YouTube videos on some blog posts.

Analytics, and what they actually see

We use Fathom Analytics to count page views. Fathom is cookieless by design: it does not store anything in your browser, does not assign you an identifier that follows you between websites, and does not build a profile of you. To tell unique visitors apart, it briefly turns your IP address and browser details into a hash that changes every day, and it does that on EU servers for EU visitors. What we get back is aggregate — how many people opened a page, which page sent them there, roughly which country they were in. There is no way for us to go from a number on that dashboard back to a person, and none of it is sold or shared with advertisers.

No cookie and no localStorage entry. Unique visitors are counted with a daily-changing hash of your IP address and browser details, not an identifier that follows you.
No cross-site or cross-device identifier.
Aggregate counts only — page views, referrers and country-level location.
Analytics load in production only. A local development build has none.

Why there is no consent banner

Consent banners exist because most sites store things that are not necessary for the site to work — almost always for advertising. Under the ePrivacy Directive and the GDPR, that kind of storage needs your permission first. Storage that is strictly necessary to deliver something you asked for does not. The values listed above are the only things we write, and each one exists to honour a choice you already made — setting up a tool you are using. There is nothing to ask you about for those, so we do not put a click between you and the page. The exception is the blog: some posts load a YouTube player with the page, and that player may store data of Google's own. That storage is not ours and not strictly necessary, and today we do not ask before the player loads. If you would rather it did not load, block youtube-nocookie.com in your browser or content blocker; the rest of the post works without it.

The VoiceSnap Pro app does not use cookies

This policy covers the website. The desktop app is not a browser and has no cookies at all. Audio is captured only during a dictation or note you start, dictation audio is discarded once the transcript comes back, notes and their recordings are kept in your account, and nothing you dictate is used to train AI models. Signing in and subscribing happen in the app: Google's sign-in page and Polar's checkout and customer portal open in your browser on their own websites, under their own cookie rules, not on voicesnap.pro. The privacy policy covers all of that in detail.

Videos on the blog

Many posts on the blog embed YouTube videos in YouTube's privacy-enhanced mode (youtube-nocookie.com). The player loads with the page rather than when you press play, so opening one of those posts sends your IP address and browser details to Google, and the player may store data in your browser under Google's own rules. Those values belong to Google, not to us, and we cannot read them. Clearing site data for youtube-nocookie.com removes them.

Clearing what is stored

Clearing site data for voicesnap.pro in your browser settings removes every value listed above immediately. Browsing in a private window has the same effect — everything is discarded when you close it. Nothing breaks if you clear them. The tools forget their settings — the teleprompter its script too.

Chrome and Edge: Settings, then Privacy and security, then Third-party cookies, then See all site data and permissions.
Safari: Settings, then Privacy, then Manage Website Data.
Firefox: Settings, then Privacy & Security, then Cookies and Site Data, then Manage Data.

Changes to this policy

If we ever add something to this website that does set a cookie, this page is updated before it goes live, and the change is spelled out here rather than folded into a paragraph nobody reads. The date at the top of the page always reflects the last change.

Questions about any of this

If something on this page is unclear, or you want to know whether a specific tool is in use, write to us and you will get a straight answer. VoiceSnap Pro is run by Iaroslav Morgunov, a sole trader in Porto, Portugal, who is responsible for this website; the Legal Notice has his full details.

Email support@voicesnap.pro

Cookie questions we actually get

: No. There are no cookies on voicesnap.pro — not first-party, not third-party, not analytics, not advertising. The only things the site writes to your browser are the localStorage values listed on this page, which remember a setting or script in a tool you used, and the speech model the audio-to-text tools cache. YouTube players on some blog posts may store data of Google's own.
: No, and the difference matters. A cookie is attached to every request your browser makes to the domain that set it, so the server sees it constantly. A localStorage value is never sent anywhere: it sits in your browser, readable only by pages on voicesnap.pro, until you or the site removes it. We never read these values on the server, because the server never receives them.
: Because consent is required for storage that is not necessary, and what we write is not that. Each value records a choice you already made — setting up a tool you are using — which is exactly the kind of strictly necessary storage that does not need a banner. The one exception is the YouTube player on some blog posts: it is Google's, it loads with the page, and we do not currently ask before it does. If you would rather it did not load, block youtube-nocookie.com in your browser or content blocker.
: Clear site data for voicesnap.pro in your browser settings, or open the site in a private window so nothing persists. Every value is removed instantly. The tools forget their settings and cached data.
: A few do, in your browser only: the alt-code finder remembers your platform and recent symbols, the decibel meter its calibration, the pitch detector its tuning reference, and the teleprompter your script, so it survives a refresh. The audio-to-text converters cache the speech model they download. None of it is sent to us. Most tools process what you paste or record entirely in the page; the voice-typing tools are the exception, because they use your browser's own speech recognition, which in Chrome sends the audio to Google.
: No. You subscribe to Pro inside the app, which opens Polar's checkout in your browser on Polar's own website; the customer portal works the same way. Any cookies there are set by Polar, under its own policy, not by voicesnap.pro. If we ever add something to this website that sets a cookie, this page is updated before it goes live, with the provider named and the cookie described.