TickerCase Policy
Cookie Policy
TickerCase uses essential sign-in technologies and consent-based campaign measurement, without personalised advertising or cross-site behavioral profiles.
Essential Technologies
Supabase authentication uses secure browser cookies or equivalent local session storage to keep you signed in, complete OAuth login, and protect account access. These technologies are required for signed-in functionality and cannot be disabled through a TickerCase preference panel.
Optional Campaign Measurement
If you choose Allow measurement, TickerCase uses first-party localStorage to keep a random attribution identifier and limited first- and last-touch campaign information. This can include UTM fields, an advertising click identifier supplied in the landing URL, referring host, landing path, and timestamps. TickerCase treats this attribution as expired after 90 days and removes or replaces it when the site next runs in that browser. A random visit identifier is held in sessionStorage for the browser session.
After you allow measurement, TickerCase also loads the Google Ads tag. The tag may use first-party advertising cookies or similar browser storage and send Google page URLs and titles, referring information, browser and device information, advertising click identifiers, consent signals, and pseudonymous measurement identifiers. TickerCase uses Google Ads tag ID AW-18483659850 for campaign and conversion measurement. Google determines its own retention under its policies.
Google Ads personalisation, remarketing signals and enhanced conversions are disabled for this launch. TickerCase does not send Google account email addresses, raw claims, transcripts, report prose or payment-card details through the tag.
Privacy-Scoped Product Events
When optional measurement is allowed, product and campaign events may be recorded server-side without raw claim text, transcripts, report prose, email addresses, authentication values, or payment-card details in event metadata. Purchase and refund confirmations remain recorded as necessary transaction and accounting records even when optional measurement is off.
Your Consent Choice
Optional measurement is off until you choose Allow measurement. Before consent, the Google Ads script is not requested. Rejecting measurement does not affect essential sign-in, analysis, saved-report, or payment functions. Your preference is stored for up to 12 months so the service can honor it.
You can reopen Privacy choices at any time to withdraw or grant consent. Withdrawing consent clears TickerCase campaign attribution from that browser, sends denied Consent Mode signals to a Google tag already loaded on that page, and stops future optional measurement events. It does not erase transaction records or processing completed before withdrawal. You can delete existing browser storage through your browser settings.
A recognized Global Privacy Control or Do Not Track browser signal keeps optional measurement off and overrides an attempt to enable it.
Browser Controls
You can also delete or block cookies, localStorage, and sessionStorage through your browser. Blocking essential authentication storage may prevent sign-in, transcript import, analysis, and access to saved theses.
Future Changes
If additional analytics providers, advertising pixels, personalised advertising, remarketing, customer-list matching, or other cross-site marketing technologies are introduced, this policy will be updated and required consent controls will be provided before those technologies are activated.