Cookie Policy

This Cookie Policy explains how Sharkly ("we," "our," or "us") uses cookies and similar technologies on sharkly.co (our marketing site) and how that relates to the app at app.sharkly.co. It should be read together with our Privacy Policy.

Your choices (marketing site)

When Google Analytics is enabled on sharkly.co, we show a cookie banner until you make a choice. You can:

• Accept — We record your choice in your browser (localStorage key sharkly_cookie_consent with value accepted) and update Google Consent Mode so analytics and related measurement can run as described below.
• Reject — We record rejected and do not enable optional analytics measurement via Consent Mode. The banner closes; your preference is stored locally.

If you have already chosen, you can clear site data for sharkly.co in your browser settings to see the banner again, or remove the sharkly_cookie_consent entry from localStorage for this site. We do not currently offer a separate in-page "cookie settings" dashboard.

Technologies we use

sharkly.co (marketing)

• Google Analytics 4 (GA4) — When our analytics measurement ID is configured and you have accepted analytics, we load Google's tag (gtag.js) to measure page views and usage. Google may set cookies and use similar storage (e.g. _ga, _ga_*) as documented by Google.
• Google Consent Mode — Before you accept, we default analytics_storage and related consent types to denied so optional measurement does not run. After Accept, we update consent to granted for analytics and the Consent Mode categories we pass to Google (including analytics and the ad-related consent flags required by our GA4 integration). We use GA for traffic and product insight; we do not run separate ad network campaigns on the marketing site.
• Theme and UI — We store dark/light preference in localStorage under the key theme. This is not used for cross-site tracking.

For how Google uses data, see Google's Privacy Policy and Google's Cookie Policy.

app.sharkly.co (product)

The logged-in application uses first-party cookies and storage required for authentication (e.g. Supabase session), security, and core features. These are necessary for the service and are not controlled by the same marketing-site banner. See the Privacy Policy for account data.

Updates

We may update this Cookie Policy when we change analytics tools or consent mechanics. The "Last updated" date at the top reflects the latest revision.

Contact

Questions about cookies or this policy:

This Cookie Policy is effective as of March 25, 2026.