Cookie Policy
Last updated: August 25, 2026
This page explains what we store in your browser to run Podify and, with your consent, to understand how it is used — and how to change that choice at any time. Our Privacy Policy covers what we collect about your account; this page is only about cookies and the equivalent browser storage.
Two categories, one choice
A banner appears the first time you visit and asks you to accept, reject, or customize. It offers two switches — Analytics and Marketing — on top of what is strictly necessary and always on. Behind those switches are the seven signals Google Consent Mode v2 defines. Here is exactly how your choice maps onto them:
| Category | Signals it controls | Without a saved choice |
|---|---|---|
| Strictly necessary (always on) | security_storage, functionality_storage | Always granted — these two hold the consent choice itself, so the site cannot remember any choice without them. |
| Analytics switch | analytics_storage | Denied |
| Marketing switch | ad_storage, ad_user_data, ad_personalization, personalization_storage | Denied |
Rejecting, or simply closing the banner without choosing, leaves every signal in the two switchable rows at its denied default. The strictly-necessary row is not part of that choice — it is granted either way, which is what makes it strictly necessary. Nothing we set for analytics or marketing is stored until you say so.
One thing is not covered by that choice, so we name it here rather than let you discover it: episode pages embed the YouTube player, and YouTube stores its own cookies in your browser as soon as an episode page loads the player — you do not have to press play, and it happens whatever you answered above. Those belong to Google, not to us — we can neither read them nor switch them off, and they are governed by Google's own privacy policy. The only way to avoid them is on your side: block third-party cookies in your browser, or do not open episode pages.
What loads, and when
We use Google Tag Manager to run Google Analytics. The container does not load at all — no request to Google's servers — unless you accept at least one of Analytics or Marketing. There is no fallback that loads it for visitors without JavaScript, so if your browser cannot run our consent script, you are simply not tracked.
Revoking your consent takes effect immediately for any new activity. What it cannot do is unload a container that already started running in this page load — once it has loaded, it stays loaded until you close the page or load another one. Reject, or come back and switch it off, and the container is simply absent from then on.
On some hubs, a second measurement script runs alongside ours: the creator's own Google Analytics property, not ours. They connect it themselves, from their own settings; what it collects goes to their property, and we never read it. It answers the Analytics switch on the same banner above — nothing extra to accept, and nothing else turns it on: accept Marketing while leaving Analytics off and it never loads at all. One banner, one decision on this page, not two. Revoking updates its signals immediately, the same as ours; what it cannot do, also the same, is unload a copy already running in this page load — that stays until you close the page or load another one. What it sends is a single pageview each time you open a page on this hub — no search text, no email address, nothing from your Podify account, and no events beyond that pageview. Like any Google Analytics property, and like ours, it does use the standard Google Analytics cookie in your browser: a random per-browser number, set only after you accept Analytics, that lets repeat visits count as one visitor instead of several. It is not your name, and the creator's property only ever receives what happens on their hub — but it is an identifier, so we would rather name it than let you find it in your cookie list. The cookie itself belongs to the website you are on: on a creator's own domain it is theirs alone, and on podifyapp.co it is the same one our own analytics uses. Reject Analytics, or never answer, and it is never set at all. Switching it off after you had accepted is different, and we would rather be exact: nothing new is written from then on, but the cookie already in your browser stays there until it expires or you clear it yourself. We do not delete it for you; your browser's settings do, for this site and any other.
The identifier behind Analytics
The events that carry an internal account identifier all come from our billing system: a completed subscription payment, a plan change, and a cancellation. Our server sends each one to Google Analytics directly. The identifier is an internal reference — not your email address, your name, or your hub's public address — and it is what lets a purchase be matched to the visit that led to it. The events your browser sends do not carry it. Because these events do not come from your browser, they use an identifier recorded when you checked out: switching Analytics off in the banner stops what your browser sends, and it does not stop these. Deleting your account (see Privacy Policy) sends Google a deletion request for that identifier and the Analytics profile behind it. Google confirms that it accepted the request, not that the data is gone — the erasure happens on their side, on their schedule, and it is the only answer their API gives us. Everything we hold ourselves is deleted outright.
How long the analytics data is kept
Google Analytics keeps the event data for 14 months, then deletes it automatically. Aggregate reports — visit counts and the like, with nothing tied back to an individual — outlive that window. If you delete your account before it is up, the identifier and the profile behind it go with it, without waiting for the 14 months to run out.
If you reach us through a creator's own domain
Some hubs are published on a custom domain instead of podifyapp.co. Browsers keep cookie and storage choices separate per website, and a custom domain is a different website from ours — even though it shows you the exact same banner. So if you visit a hub on podifyapp.co and then the same hub on its own custom domain, you will be asked to choose again. There is no way around this without a third-party consent service shared across every domain, which we do not run.
Changing your choice
You can reopen the banner at any time, with your current choice preselected, and save a different one.
The sign-in cookies
Separately from all of the above, we set the cookies sign-in needs: one that keeps you signed in, plus short-lived ones our authentication library uses to protect the sign-in form and to complete the Google round-trip. They are strictly necessary to use an account at all, so they are not part of the choice this page describes, and our Privacy Policy covers them.
Changes to this policy
If we materially change what we store or why, we'll update the date at the top of this page.
Contact
Podify is operated by Cristian Filimon, trading as Amaze Labs (NZBN 9429053396341), New Zealand. Questions about this policy go to privacy@podifyapp.co. See also our Privacy Policy.