Spryng.io Cookie Policy

Last updated: October 28, 2026

This Cookie Policy explains how Spryng.io LLC ("Spryng," "we," "us," "our") uses cookies and similar technologies on our public website and related services.

1. What Cookies Are

Cookies are small text files stored on your browser or device. Similar technologies (local storage, pixels, SDK storage) can perform comparable functions.

2. No advertising tracking

No advertising tracking. We do not use advertising cookies, marketing pixels, or data-broker integrations, and we do not sell personal information or share it for cross-context behavioral advertising. We use two analytics tools, described in section 3.2, to understand how our website is used.

3. Cookie Categories We Use

3.1 Strictly Necessary Cookies

These are required for core site and service operation, including:

  • security and fraud prevention,
  • session continuity,
  • load balancing and reliability controls,
  • saving your analytics opt-out (spryng_analytics_opt_out), kept for one year.

These cannot be turned off because the site may not function properly without them, or because the opt-out has to keep being honored. A previous "rejected" choice from the old cookie banner is still honored.

3.2 Analytics

Analytics load by default. The marketing site does not show a consent banner, and it does not load Facebook, TikTok, Google Ads, IndustryBrains, or other advertising pixels.

On spryng.io, www.spryng.io, and stagex.spryng.io:

Visitors in the EEA, the United Kingdom, or Switzerland: Google Analytics does not load and no request is sent to Google.

  • Google Analytics 4 measures page visits only where it is allowed to load. The tag sends the public page path, the site name, whether the host is production or staging, and campaign labels (utm_source, utm_medium, utm_campaign, utm_content, utm_term) when those values are simple tokens. Referrers are reduced to the referring origin. It does not send form contents, private deck addresses, or other URL parameters. Google also receives technical browser and device data. Google Signals and advertising personalization are off. ad_storage, ad_user_data, and ad_personalization stay denied. analytics_storage is granted only in that case, because the tag is not loaded for the EEA, the United Kingdom, or Switzerland. The site does not set a custom cookie lifetime, so Google's default for _ga and _ga_YEHWDQ123N is two years.

  • PostHog records product analytics: page views and named product events (for example pricing or orientation choices), sent through g.spryng.io. PostHog, Inc. processes that data for Spryng. Where session replay is on, PostHog also receives a recording of the page, click heatmaps, and dead clicks. The browser configuration masks all inputs, masks all text, and blocks form, input, textarea, and select elements, replacing them with an empty block before the recording is sent. That is the setting this site uses. It is not a statement that a later page change will stay masked. Exception capture and surveys stay off. Where session replay is on, clicks and form submits are recorded on the elements of the page, so heatmaps, dead clicks, and rage clicks can be studied. Session replay is on for a browser whose time zone does not begin with Europe/ (see below). The data-attr marks on retailer links, Studio signup links, the book activation form, pilot and contact forms, webinar registration links, and pricing buttons remain. Typed input values are not captured. Copied text is not captured. The text of input, textarea, and select elements is removed before the event is sent. Labels on buttons and links can be included. Recordings that do run mask all inputs, mask all text, and block form fields. PostHog keeps its identifiers in memory only on this site: it sets no cookie and no local-storage identifier, and no identifier is shared with app.spryng.io or copied into signup links. Page views follow in-app navigation. Events can include the page address and technical data such as browser and IP address. Person profiles are limited to people who identify themselves; the marketing site does not identify visitors. The site does not set a custom PostHog cookie lifetime, so the default is up to one year. Session replays are kept for 14 months with the other website analytics.

    Where you are is read from one thing only: your browser's time zone. The site uses no server, CDN, or cookie location hint.

    • Time zone beginning Europe/…, or a time zone that cannot be read: no analytics load. Google Analytics and PostHog do not start, and no request is sent to either.
    • Any other time zone: Google Analytics may load. PostHog keeps memory only, with no cookie and no local-storage identifier. Session replay, heatmaps, and dead clicks may run with the masking described above. A visitor in the EEA, the United Kingdom, or Switzerland whose browser time zone does not begin with Europe/ (for example Atlantic/Reykjavik, Atlantic/Canary, Asia/Nicosia, or UTC) is treated this way. A site setting can keep Google Analytics and session replay off for every visitor. That setting is off unless we turn it on.

Global Privacy Control and Do Not Track. If the browser sends either signal, Google Analytics and PostHog do not load. No analytics request is sent, and session replay does not start. That applies in every location.

Footer controls. "Opt out of analytics" is in the footer for every visitor. It stores the opt-out for one year and turns off Google Analytics, PostHog, heatmaps, dead clicks, and session replay in that browser, including a replay that has already started. "Do not sell or share my personal information" is shown to every visitor, because the site does not determine location beyond the time zone. It runs the same opt-out.

3.3 Storage this site uses

Name Provider Purpose Duration Where it is set
_ga Google Distinguish browsers for Google Analytics 2 years Cookie set by gtag.js only when Google Analytics is allowed to load
_ga_YEHWDQ123N Google Keep session and campaign state for measurement ID G-YEHWDQ123N 2 years Cookie set by gtag.js only when Google Analytics is allowed to load
ph_phc_HlsqUGABBmeHms0IlRusgBgI2N342MDgKyestrDtSE9_posthog PostHog Persist the PostHog client, including the distinct id and the session id a replay is stored under when replay is on. Shared with app.spryng.io when that app uses this PostHog project Up to 1 year Not set on this site: PostHog runs memory-only
Session replay, heatmaps, and dead clicks PostHog Page recording, click positions, and clicks that do not navigate. Text is masked, inputs are masked, and form fields are blocked in the browser before sending. Kept 14 months with website analytics Not a separate cookie Sent to g.spryng.io when replay is on. Not sent when the browser time zone begins with Europe/ or cannot be read. Stopped by GPC, DNT, or "Opt out of analytics"
__ph_opt_in_out_phc_HlsqUGABBmeHms0IlRusgBgI2N342MDgKyestrDtSE9 PostHog Remember a PostHog opt-in or opt-out Up to 1 year Cookie. Deleted, with other ph_ and __ph_ keys, when you opt out on this site
spryng_analytics_opt_out Spryng Remember that this browser opted out of analytics 1 year Cookie (Max-Age 31536000) and localStorage, set by the footer controls and the control on this page
spryng-site-theme Spryng Remember light or dark appearance Until you clear site data localStorage only

4. How to Manage Your Choices

You can stop analytics, including session replay, on this browser by:

  • sending Global Privacy Control or Do Not Track;
  • using Opt out of analytics in the footer; or
  • using Do not sell or share my personal information in the footer when that control is shown; or
  • selecting Opt out of analytics on this Cookie Policy page.

You can also block or delete cookies in browser settings. Blocking cookies stops analytics cookies where we would otherwise set them. Blocking all cookies may affect features that need a strictly necessary cookie.

5. Third-Party Services

Marketing-site analytics providers are Google (Google Analytics 4) and PostHog, Inc. PostHog processes events for Spryng, and processes session replays where replay is on, as described in our Privacy Policy. They may process limited technical data (such as event metadata and device/browser details). Google Analytics does not load for visitors in the EEA, the United Kingdom, or Switzerland. Session replay, heatmaps, and dead clicks are not started for those visitors.

6. Changes to This Policy

We may update this policy from time to time. Material changes will be published with an updated date.

7. Contact