Cookie Policy — ScripTrade

This page explains which cookies and similar technologies (such as browser local storage) ScripTrade uses, why, and for how long. Strictly necessary technologies are always active; analytics and marketing tools are switched on only with your consent.

1. Technologies we use

Clerk authentication cookies (__session, __client_uat and related security cookies): strictly necessary; used to authenticate users, protect sessions, and prevent abuse; retained for the session or the period configured for Clerk authentication.
aw_cookie_consent (local storage): strictly necessary to remember your cookie choices; retained for up to six months, or until choices are changed or browser storage is cleared.
aw_privacy_subject_id (local storage): random identifier strictly necessary to link cookie-choice evidence on the device; it contains no name or email and remains until browser data is cleared.
aw_pending_cookie_consent_events (local storage): temporary technical queue containing only choices not yet delivered to the compliance record; it is removed after delivery and contains at most ten events.
aw_analytics_sid (session storage): optional analytics identifier, created only after analytics consent and removed when the browser session storage ends or consent is withdrawn.
aw_waitlist_affiliate_code (local storage): functional identifier used to show the personal referral code issued after joining the waitlist; retained for up to 30 days. Referral attribution arriving from a shared link is passed directly to the waitlist request and is not stored on the device.
Google Ads, Meta and OpenAI Ads marketing tools: They activate only with your consent to measure advertising conversions. You can change or withdraw your choice at any time from the footer.

2. Managing your choices

You can accept, reject or change your choices at any time, and rejecting optional cookies does not limit the Service. You can also delete cookies and local storage from your browser settings: the banner will then ask for your choices again. We ask again every six months in any case.

3. More information

The data controller, the providers involved, transfers outside the EU and your rights are described in the Privacy Policy.

1. Technologies we use

Clerk authentication cookies (__session, __client_uat and related security cookies): strictly necessary; used to authenticate users, protect sessions, and prevent abuse; retained for the session or the period configured for Clerk authentication.

aw_cookie_consent (local storage): strictly necessary to remember your cookie choices; retained for up to six months, or until choices are changed or browser storage is cleared.

aw_privacy_subject_id (local storage): random identifier strictly necessary to link cookie-choice evidence on the device; it contains no name or email and remains until browser data is cleared.

aw_pending_cookie_consent_events (local storage): temporary technical queue containing only choices not yet delivered to the compliance record; it is removed after delivery and contains at most ten events.

aw_analytics_sid (session storage): optional analytics identifier, created only after analytics consent and removed when the browser session storage ends or consent is withdrawn.

aw_waitlist_affiliate_code (local storage): functional identifier used to show the personal referral code issued after joining the waitlist; retained for up to 30 days. Referral attribution arriving from a shared link is passed directly to the waitlist request and is not stored on the device.

Google Ads, Meta and OpenAI Ads marketing tools: They activate only with your consent to measure advertising conversions. You can change or withdraw your choice at any time from the footer.

2. Managing your choices