Cookie Policy
Our cookie policy and how we use them
This Cookie Policy explains how ShotTrack Pty Ltd ("Company," "we," "us," or "our") uses cookies and similar technologies when you visit or use our websites and web applications, including shockai.co, shottrack.com.au, and related ShockAI services that link to this policy (collectively, the "Services").
For how we process personal information more broadly, see our Privacy Policy. Our Terms of Service govern your use of the Services.
Effective 6 May 2026.
Overview
We use cookies and similar storage (for example local storage in your browser) where needed to operate, secure, and improve the Services. Many cookies are strictly necessary for sign-in, security, or basic site function. Others remember preferences such as theme or interface layout so the experience stays consistent when you return.
At the time this policy was written, we do not use cookies on our web Services for third-party advertising or behavioural profiling. If that changes, we will update this policy and, where required by law, seek appropriate consent.
What are cookies?
Cookies are small text files placed on your device when you visit a site. They are widely used to make sites work more efficiently, remember choices, and understand how a service is used.
Cookies may be "session" cookies (removed when you close your browser) or "persistent" cookies (which remain for a set period or until you delete them). Similar technologies can include pixels or local storage keys; we describe browser storage used for preferences below where relevant.
Categories of cookies we use
- Strictly necessary. Required for authentication, security (for example session cookies), routing you to the correct workspace after sign-in, request tracing for reliability, and other core functionality. The Services cannot work properly without these.
- Functional / preferences. Remember choices such as colour theme, collapsed or expanded navigation, selected language, and UI layout for certain tools. Disabling these may reset preferences on each visit.
Cookies and similar storage we use
Exact cookie names for authentication are managed by Supabase and may include a project-specific prefix (for example cookies beginning with "sb-"). Team-selection cookies include your user identifier in the name. Tool-related layout cookies use names beginning with event-compare- for certain analysis UIs.
| Name / pattern | Purpose | Typical duration |
|---|---|---|
Supabase auth cookies (e.g. names starting with sb-) | Maintain your signed-in session and refresh tokens securely. | Session or persistent (as set by Supabase) |
x-correlation-id | Associates requests for logging and troubleshooting (HTTP-only, not readable by page scripts). | 24 hours |
last-selected-team | Remembers your last opened team workspace for routing within the app. | 30 days |
theme | Stores light or dark theme preference. | Up to 1 year |
lang | Stores your selected interface language. | Up to 1 year |
sidebar:state | Remembers whether the sidebar is expanded or collapsed. | 7 days |
layout-style | Remembers app shell layout preference where applicable. | Persistent |
event-compare-* | Persists panel and layout state for certain in-app tools. | Persistent (long-lived) |
Our mobile apps may use platform storage (not browser cookies) for similar purposes; see the Privacy Policy for app data practices.
Third-party services
Some features rely on services that may set their own cookies when you interact with them. For example, our authentication stack is hosted on Supabase; payment flows may route through Stripe or other processors they specify. Those providers control their own cookies and you should read their policies if you use those features.
We do not control cookies set by third-party sites that you reach through links from our Services.
Your choices
Most browsers let you refuse or delete cookies through settings. If you block strictly necessary cookies (including authentication cookies), you may not be able to sign in or use parts of the Services.
You can change theme, language, and some layout options in the app; that updates the related preference cookies where we use them.
A cookie consent banner component may appear in some deployments; where present, controls in the banner apply to consent managed in the browser (for example local storage keys used alongside the banner), in addition to cookie settings described here.
Updates to this policy
We may update this Cookie Policy from time to time. The effective date above reflects the latest revision. Material changes may be communicated through the Services or as required by law.
Contact us
If you have questions about this Cookie Policy or our use of cookies, contact us at privacy@shottrack.com.au.