ThunderPhone
TechnologyPlatformPricingEnterpriseDocs
Sign inGet started
Privacy policyTerms of serviceCookie policyData processing (DPA)

Cookie policy

Every cookie and storage entry this site uses, named specifically — with consent rules that follow your region's law.

Last updated July 31, 2026
On this page
01Our approach02Essential storage03Analytics04Product dashboard and client portals05What we don't use06Managing your choice07Questions

01Our approach

In short

Consent rules follow your region's law: opt-in in the EEA, UK, and Switzerland; on-by-default with a working opt-out everywhere else. No ad pixels, no data sale, no cross-site behavioral ads.

Cookies and similar technologies (like localStorage) are small pieces of data a site stores in your browser. What runs, and when, depends on where you are:

  • Only essential storage runs everywhere by default.
  • In the EEA, UK, and Switzerland, analytics and session replay run only after you click "Accept analytics" in the consent banner.
  • Everywhere else, privacy-filtered analytics and session replay run by default. You'll see a notice on your first visit, and you can opt out at any time — your opt-out takes effect immediately and sticks until you change it.
  • Session replay data goes to an OpenReplay instance that we host on our own infrastructure; Google Analytics requests, where analytics runs, go to Google and are processed under Google's data-protection terms.

02Essential storage

In short

Two things: your cookie choice, and sign-in session cookies in the dashboard.

NamePurposeTypeDuration
tp-cookie-consentRecords whether you accepted or declined analytics, so we don't ask again.localStorageUntil you change or clear it
thunderphone_auth_tokenKeeps you signed in to the ThunderPhone dashboard.localStorageUntil logout, token expiry, or browser storage clearing
thunderphone_selected_org_id and related workspace keysRemembers your current workspace and product setup state.localStorageUntil changed, logout, or browser storage clearing

Essential storage can't be switched off — without it the site and dashboard don't work — but none of it tracks you across other sites.

03Analytics

In short

OpenReplay and Google Analytics where configured. Opt-in in the EEA/UK/Switzerland; on-by-default with a working opt-out elsewhere.

Where analytics is allowed to run — by your consent in the EEA, UK, and Switzerland, or by default with a working opt-out elsewhere — we run OpenReplay and Google Analytics where configured. We use these tools to understand page performance, product interest, and site issues; we do not sell the data or use it for cross-site behavioral advertising. Session replay is privacy-filtered (inputs and identifiers are masked) and may include our support staff viewing an in-progress session live to help you.

On the marketing site only, and under the same regional rules, we also use company-identification services (currently Snitcher and Leadfeeder) that estimate which company a visit comes from — for example from the network the visit originates on — so our team can follow up with businesses that show interest. These services identify companies, not individual people, and never run in the signed-in dashboard or client portals.

Inside the signed-in product dashboard, OpenReplay privacy-filtered session replay and product analytics may run where enabled to help us operate, secure, debug, support, and improve the service.

NamePurposeTypeDuration
__openreplay_*Maintains privacy-filtered replay session identifiers and buffered telemetry where OpenReplay is enabled.localStorage or sessionStorageProvider defaults, typically session-scoped or up to 12 months unless shortened in configuration
_ga, _ga_*Google Analytics measurement where configured.CookieProvider defaults, typically up to 24 months unless shortened in configuration
_lfaLeadfeeder company-identification (marketing site only).CookieProvider default, typically up to 24 months
Snitcher identifiersSnitcher company-identification (marketing site only); storage names vary by tracker release.Cookie or localStorageProvider defaults, typically up to 12 months

Analytics data is typically retained for up to 24 months, then aggregated or deleted unless a shorter period is configured.

04Product dashboard and client portals

In short

The signed-in dashboard uses the same consent-gated analytics; the client portals we host for your end users load none.

Inside the signed-in product dashboard we use the same regional consent rules as the marketing site — Google Analytics and OpenReplay privacy-filtered session replay, opt-in in the EEA/UK/Switzerland and on-by-default with a working opt-out elsewhere — to operate, secure, debug, support, and improve the service. We honor the Global Privacy Control (GPC) signal here as well. The dashboard shows its own regional banner.

The dashboard's support chat loads as part of the service itself: talking to support is a product feature, so its widget is identified by your account (name, email, organization) to route and answer your conversation. It is not used for advertising or cross-site tracking.

The client portals we host for our customers' own end users (the /portal pages) load no analytics and no session replay at all — only the essential storage needed to load the page runs there.

05What we don't use

  • No advertising pixels (Meta, Google Ads, LinkedIn, or otherwise)
  • No advertising analytics used to share or sell data
  • No session replay in the EEA, UK, or Switzerland without your consent, and none anywhere after you opt out
  • No cross-site tracking or fingerprinting
  • No selling or sharing of data, ever

06Managing your choice

In short

Change your mind anytime — right here, or in the footer of any page.

You can also clear or block storage in your browser settings; blocking essential cookies may break dashboard sign-in.

We honor the Global Privacy Control (GPC) signal as a standing opt-out: if your browser sends it, analytics stays off — including overriding an earlier acceptance, unless you accepted while the signal was already on. Opting out takes effect immediately: analytics stops and its cookies are removed. We do not treat the legacy "Do Not Track" field as a signal, because major browsers shipped it enabled by default for years and it no longer reflects a deliberate user choice.

07Questions

Email privacy@thunderphone.com. For the bigger picture, see our privacy policy.

ThunderPhone
ProductTechnologyPlatformPricingEnterpriseBlog
Legal & trustPrivacyTermsCookiesDPATrust center
© 2026 Autophonix, LLC d/b/a ThunderPhone