Cookie Policy

This Cookie Policy explains how SnapCash uses cookies, local storage, and similar technologies on the marketing site and dashboard.

Some of these technologies are required for sign-in, security, and product functionality. Others help remember your preferences. SnapCash also uses consent-aware Google Analytics 4 through Google Tag Manager for product measurement when analytics is enabled and your browser choice allows it.

SnapCash uses essential cookies and similar technologies to support secure sign-in, session continuity, request integrity, and other core product functions. These technologies are necessary for features such as account login, token refresh, and provider sign-in flows.

• Refresh and session cookies used to keep authenticated sessions working securely.
• Temporary sign-in state cookies used during OAuth or similar identity flows.
• Security-related browser storage or request state needed to protect the service from misuse.

SnapCash stores preference data so the site can remember settings you choose, such as language, theme, and whether you allowed or declined analytics on this browser.

• Dashboard language preference (`pk_locale`).
• Dashboard theme preference (`pk_theme`).
• Marketing-site cookie banner acknowledgment stored in local storage (`snapcash_cookie_consent_v1`).
• Dashboard analytics preference stored in local storage (`snapcash_analytics_consent_v1`).
• Short-lived country bootstrap cookie (`snapcash_country_hint_v1`) containing only a version, an approximate-IP source class, and a canonical country code. It helps avoid repeated catalog-resolution steps and is not trusted as proof of location or for task-start enforcement.

SnapCash loads Google Tag Manager and Google Analytics 4 only after you select Allow analytics on this browser. If the choice is unset or declined, SnapCash does not load those Google tags or send cookieless analytics pings.

SnapCash analytics events are designed to avoid emails, names, wallet balances, payout destinations, ledger identifiers, provider event identifiers, click IDs, handoff tokens, raw provider URLs, and support message text.

Analytics page locations and referrers use sanitized route templates. Verification, password-reset, OAuth, handoff, advertising click, search, and other sensitive query values are removed before an analytics event is created.

SnapCash does not use Google Analytics 4 for cross-context behavioral advertising or advertising personalization in this implementation.

If you click through to a third-party survey, offer, authentication, or payout provider, that provider may set its own cookies or similar technologies under its own policies. SnapCash does not control those third-party cookies once you leave or embed a third-party surface.

You can control cookies through your browser settings and clear local storage through your browser or device controls. Blocking essential cookies may prevent you from signing in or using protected features of SnapCash.

You can update the SnapCash analytics choice for this browser on this Cookie Policy page. Revoking a prior grant clears known first-party Google Analytics cookies and reloads into a no-Google-tag state. Clearing browser storage removes the saved choice and may show the analytics prompt again.

For more information about how SnapCash handles personal information, see the Privacy Policy. If you have questions about this Cookie Policy, contact SnapCash through the Support page.