Cookie Policy

Last updated: 21 October 2026

1. What Cookies Are

A cookie is a small text file that a website places on your device when you visit it. Cookies let the site remember information about your visit — your preferences, whether you are signed in, and how you interact with the page — so it can work properly and improve over time.

This policy explains which cookies and similar technologies (local storage, session storage, pixels, SDKs) Sparkling uses, why we use them, and how you can control them. It applies to the marketing site at sparkling.nz and to the Sparkling product surfaces (the Telegram mini-app and the web app).

2. Categories of Cookies We Use

2.1 Strictly Necessary

Required for the Service to function. Without them, parts of the site or app will not work. We rely on legitimate interest for these — they cannot be switched off.

• Session and authentication tokens: Keep you signed in to the Sparkling app while you trade, sign quotes, or review balances.
• Security cookies: Protect against cross-site request forgery (CSRF), bot abuse, and account takeover.
• Load-balancing cookies: Route your requests to the nearest healthy server.

2.2 Functional

Remember the choices you make so the experience feels consistent across visits. Setting them requires your consent under the ePrivacy framework in the EU/EEA.

• Preferences: Language, currency display, dark/light theme.
• Recent activity hints: Surface your last-used pairs and chains for faster re-entry.

2.3 Analytics

Help us understand how the site and product are used in aggregate, so we can fix slow pages, broken flows, and confusing copy. On the website, we use Google Analytics with its advertising features turned off, so it does not build cross-site advertising profiles.

• _ga – distinguishes visitors with a random identifier. Expires after 2 years.
• _ga_SP8BTJ33C0 – keeps the state of your current visit. Expires after 2 years.

What they measure: pages viewed, referrer, device and browser type, viewport size, approximate location (country and city) and anonymised event data – feature usage, error rates, performance metrics.

In the EEA, the UK and Switzerland we ask for your consent before setting analytics cookies. Until you accept, and if you decline, the Google tag sets no cookies and sends only cookieless signals in Google's consent mode. Elsewhere, analytics cookies are on by default, and you can decline them at any time.

2.4 Marketing

We do not currently run third-party ad-targeting cookies. If we add them in the future, we will list them here, ask for your consent, and give you the same one-click opt-out as for analytics.

3. Similar Technologies

• Local storage and session storage: Used for non-sensitive preferences and temporary UI state (open panels, draft inputs). They are scoped to your browser and never sent to third parties. Your cookie choice is kept the same way, as sp-consent in local storage.
• Pixels and SDK initialisation: Where embedded (for example to load a Telegram WebApp), they are subject to the host platform's own privacy notice.

4. Third-Party Cookies

Some pages embed content from partners — for example, a Telegram authentication flow, a wallet-provider widget, or an embedded support chat. Those embeds may set their own cookies that we do not control. We list the integrations we currently rely on in our Privacy Policy.

5. How to Control Cookies

5.1 In the Consent Banner

When you first visit from the EEA, the UK or Switzerland, we show a banner where you can accept or decline analytics cookies – declining is as easy as accepting. Visitors from elsewhere can make the same choice. You can re-open the banner at any time from the footer link Cookie settings.

5.2 In Your Browser

Every major browser lets you block or delete cookies. Some functions of the Service will not work if you block strictly necessary cookies. Useful links:

• Chrome
• Firefox
• Safari
• Edge

6. Changes to This Policy

We may update this Cookie Policy from time to time to reflect changes in how we use cookies, in our partners, or in the law. The "Last updated" date at the top will move when we do. Material changes will be highlighted on the site for at least 14 days.

7. Contact

Questions or requests about cookies or related tracking technologies should go to: