Cookie Policy
Last updated: 15 September 2026
This Cookie Policy explains how Podible, Inc., doing business as Podscribe (“Podscribe,” “we,” “us,” or “our”) uses cookies and similar technologies on our websites and in our measurement tag.
It should be read with our Privacy Policy and Terms and Conditions. If there is a conflict about personal data, the Privacy Policy controls.
1. Who we are
Podible, Inc.10 Waterside Plaza #35F
New York, NY
United States
Privacy requests: privacy@podscribe.com
2. What this policy covers
This policy covers:
| Property | Role |
|---|---|
| podscribe.com | Marketing website |
| app.podscribe.com | Logged-in product (dashboard) |
| auth-v2.podscribe.ai | Sign-in (Amazon Cognito Hosted UI) |
| help.podscribe.com | Help Center |
It also describes cookies set by the Podscribe JavaScript tag
(tag.js) when an advertiser installs that tag on their website.
Those cookies are first-party to the advertiser’s domain. The advertiser is typically
the controller for that placement; we process the data to provide measurement. See
Section 7.
This policy does not list cookies set solely by third-party sites you visit from our
pages (for example Google’s own cookies on accounts.google.com during
“Sign in with Google”).
3. What cookies are
Cookies are small text files stored on your device when you visit a website. They are widely used to make sites work, remember preferences, understand usage, and (where allowed) support advertising and attribution.
We also use similar technologies, including pixels, tags, local storage, and session storage. Where those technologies identify a browser or store a preference, we treat them like cookies for this policy.
4. How we group cookies
| Category | What it does | Consent |
|---|---|---|
| Strictly necessary | Required for the site or a service you asked for to work (security, login, payment). | Set without a prior opt-in. You can block them in your browser; the site or payment flow may break. |
| Functional | Remember choices such as UI layout so the product behaves as you left it. | Not required for the core service. We still set a small number today (see the lists below). You can delete them in your browser. |
| Analytics | Help us understand how the site and product are used so we can improve them. | In the EEA/UK and other consent regions, these should be set only with your permission. Today they load on our app without a banner; see Section 8. |
| Advertising / attribution | Measure campaigns, attribute conversions, and (on Google properties) support ads features. | Require consent in the EEA/UK and similar regimes, except where an advertiser has another lawful basis for their site. |
We do not change our practices when a browser sends a Do Not Track (DNT) signal. That matches our Privacy Policy.
5. Cookies on Podscribe websites
Durations are typical vendor defaults. A vendor may change them. Values are set by us or by the named provider.
5.1 Strictly necessary
| Name | Provider | Property | Purpose | Duration |
|---|---|---|---|---|
XSRF-TOKEN |
Amazon Cognito | auth-v2.podscribe.ai |
Cross-site request forgery protection on the hosted login pages | Session / short-lived |
csrf-state |
Amazon Cognito | auth-v2.podscribe.ai |
OAuth sign-in state | Session / short-lived |
csrf-state-legacy |
Amazon Cognito | auth-v2.podscribe.ai |
OAuth sign-in state (older browsers) | Session / short-lived |
__stripe_mid |
Stripe | app.podscribe.com (checkout / billing only) |
Fraud prevention and device recognition for card payments | 1 year |
__stripe_sid |
Stripe | app.podscribe.com (checkout / billing only) |
Stripe checkout session | 30 minutes |
Sign-in tokens for the dashboard are stored in local storage by
Amazon Cognito / AWS Amplify (CognitoIdentityServiceProvider.*), not as
cookies on app.podscribe.com. See
Section 6.
5.2 Functional
| Name | Provider | Property | Purpose | Duration |
|---|---|---|---|---|
sidebar_state |
Podscribe | app.podscribe.com |
Remember whether the navigation sidebar is open or closed | 7 days |
intercom-id-s0wdxf80 |
Intercom | app.podscribe.com |
Identify the visitor for the in-app support messenger | About 9 months |
intercom-session-s0wdxf80 |
Intercom | app.podscribe.com |
Keep the messenger session | About 1 week |
intercom-device-id-s0wdxf80 |
Intercom | app.podscribe.com |
Recognize the browser for support | About 9 months |
The Intercom widget script loads on the app. The messenger is booted for eligible production users so they can contact support. Intercom also records product events we send (for example tab views) to help support.
5.3 Analytics
| Name | Provider | Property | Purpose | Duration |
|---|---|---|---|---|
_ga |
Google Analytics |
app.podscribe.com (Universal Analytics property
UA-144207800-1); podscribe.com if GA is present
|
Distinguish unique browsers | 2 years |
_gid |
Google Analytics | Same | Distinguish unique browsers | 24 hours |
_gat |
Google Analytics | Same | Throttle request rate | 1 minute |
_ga_* |
Google Analytics 4 |
podscribe.com (measurement ID G-0D4FMZKSLL, via GTM,
mainly demo-form events)
|
GA4 client and session | Up to 2 years |
Google Tag Manager container GTM-TL6PS4QR is loaded on
app.podscribe.com and is also used on the marketing site. GTM itself is a
loader; the cookies above come from Google Analytics tags that GTM or our app code run.
Mixpanel analytics on the app uses local storage, not cookies. See Section 6.
5.4 Advertising / attribution
| Name | Provider | Property | Purpose | Duration |
|---|---|---|---|---|
_gac_UA-144207800-1 |
app.podscribe.com |
Store ad-click information when Google Ads is linked to Universal Analytics | 90 days | |
IDE |
Google (DoubleClick) | Third-party, doubleclick.net |
Google advertising / conversion measurement | About 13 months |
__ps_did |
Podscribe tag | Our sites if the tag runs (including via GTM); advertiser sites | Anonymous device ID (pscrb_…) for attribution |
365 days (some advertisers shorter) |
__ps_r |
Podscribe tag | Same | First referrer URL (first-touch) | 365 days |
__ps_lu |
Podscribe tag | Same | First landing page URL | 365 days |
__ps_fva |
Podscribe tag | Same | First-visit timestamp | 365 days |
__ps_sr |
Podscribe tag | Same | Session referrer | 30 minutes (rolling) |
__ps_slu |
Podscribe tag | Same | Session landing URL | 30 minutes (rolling) |
hubspotutk |
HubSpot | podscribe.com (request-demo / HubSpot forms) |
Recognize visitors on HubSpot forms | About 13 months |
__hstc |
HubSpot | Same | HubSpot analytics | About 13 months |
__hssc |
HubSpot | Same | HubSpot session tracking | 30 minutes |
__hssrc |
HubSpot | Same | Detect a new browser session | Session |
Google may also set other gcl_* / _gcl_* cookies if ads click
identifiers are present.
5.5 Help Center
help.podscribe.com is hosted by our help-center provider. It may set its own strictly necessary and functional cookies (session, load balancing, authenticated help). We will update this list if the provider’s cookie list changes.
6. Similar technologies (not HTTP cookies)
These are not cookies. They can still store identifiers or preferences on your device.
| Name / key | Technology | Purpose | Category |
|---|---|---|---|
CognitoIdentityServiceProvider.* |
local storage | Access, ID, and refresh tokens for app.podscribe.com |
Strictly necessary |
oauth_state, ouath_pkce_key |
session storage | OAuth/PKCE sign-in | Strictly necessary |
Mixpanel keys (project 2c670e5a541bafd5919ce56e04a3cff9) |
local storage | Product analytics (page views and events in production) | Analytics |
podscribe-ui-theme2 |
local storage | Light / dark / system theme | Functional |
| Table layout, filters, and similar UI keys | local storage | Remember product UI | Functional |
| Sentry session / replay data | browser storage | Error monitoring and session replay on errors | Strictly necessary / security (diagnostics) |
You can clear site data for app.podscribe.com in your browser. Clearing
local storage signs you out.
7. Cookies set by the Podscribe tag on advertiser websites
Advertisers who use Podscribe measurement may install our JavaScript tag from
https://d34r8q7sht0t9k.cloudfront.net/tag.js
(or a staging equivalent). The tag sets first-party cookies on the
advertiser’s registrable domain (SameSite=None; Secure).
| Name | Purpose | Retention |
|---|---|---|
__ps_did |
Anonymous device ID (pscrb_ + UUID). Used to recognize returning
browsers for analytics and attribution.
|
365 days (may be shorter for specific advertisers) |
__ps_r |
First referrer URL (original source). First-touch attribution. | 365 days |
__ps_lu |
First landing page URL. | 365 days |
__ps_fva |
Timestamp (ms) of the first visit. Journey duration and return frequency. | 365 days |
__ps_sr |
Session referrer. | 30 minutes (rolling) |
__ps_slu |
Session landing URL. | 30 minutes (rolling) |
Older names may still be read if present
(__podscribe_did, __podscribe_{advertiser}_referrer,
__podscribe_{advertiser}_landing_url, and related
__pscrb_* keys). New writes use the __ps_* names.
The tag also sends events (for example view, purchase, signup, lead) to Podscribe, including IP address, user agent, page URL, and optional advertiser-supplied identifiers (hashed email, mobile ad IDs, order metadata). See the Privacy Policy and the advertiser’s Data Processing Agreement.
Who is responsible for consent on advertiser sites. The advertiser must only load our tag in line with applicable law, including ePrivacy/GDPR consent where required. We do not show a banner on the advertiser’s site. If you are a visitor to a brand’s site, use that site’s cookie settings, or email privacy@podscribe.com to opt out of cookie collection from our pixel (include IP address and user agent, as described in our Privacy Policy).
DAI / impression pixels (https://verifi.podscribe.com/pxl) are URL
callbacks from ad servers. They do not set these __ps_* cookies unless
the JavaScript tag is also installed.
8. How you can manage cookies
On Podscribe websites (current controls)
We do not currently display a cookie banner or in-product preference center. You can still control cookies as follows.
Browser settings. Most browsers let you block or delete cookies, or block third-party cookies only. Instructions:
Blocking strictly necessary cookies will prevent sign-in or payment.
Google Analytics. Opt out of Google Analytics with Google’s browser add-on.
Google advertising cookies. Use Google Ads Settings and industry tools such as YourAdChoices (US) or Your Online Choices (EU).
Intercom.
Closing the messenger does not delete Intercom cookies. Delete them via browser site
settings for app.podscribe.com, or contact us.
Podscribe pixel cookies on our sites or advertiser sites. Email privacy@podscribe.com. Include your IP address and user agent if you want us to opt you out of pixel cookie collection or related IP/user-agent collection, or to make a “Do Not Sell” / DSAR request, as described in the Privacy Policy.
Local storage.
Use the browser’s “clear site data” control for app.podscribe.com. This
signs you out.
Withdrawing consent
Where consent is the legal basis, you can withdraw it at any time by deleting the relevant cookies (and site data) and by emailing privacy@podscribe.com. Withdrawal does not affect processing already carried out.
EEA and UK residents also have rights described in the Privacy Policy (access, correction, deletion, and others).
9. Updates
We may update this Cookie Policy when our cookies, vendors, or the law change. The “Last updated” date will change. Material changes may also be noted in the Privacy Policy or by a notice on the site.
10. Contact
Questions about cookies or this policy: privacy@podscribe.com.
Security vulnerability reports: security@podscribe.com.