Cookie Notice

This Cookie Notice explains how the current BitQaan customer application uses cookies and browser storage.

BitQaan may update this notice if analytics, marketing, customer-support widgets, monitoring tools, or third-party embeds are added.

The current app uses `bitqaan_session`, an essential HTTP-only, Secure, SameSite=Lax cookie with an explicit expiry, to keep signed-in users authenticated.

Google sign-in uses temporary OAuth state cookies to protect the sign-in flow. These cookies are part of the authentication process and are treated as essential where Google sign-in is available.

The disabled native BTQ send UI includes sessionStorage for the latest submitted transaction summary when that controlled feature is enabled. It does not store private keys, raw signatures, unsigned transaction payloads, passwords, seed phrases, or recovery phrases.

Clipboard APIs are used for copy actions in wallet and purchase screens; clipboard contents are controlled by the user/browser and are not cookies.

No analytics or marketing cookie implementation is used in the current customer application.

If analytics or marketing tools are added, BitQaan will update this notice, classify the cookies/storage, and implement legally required consent controls before use.

You can control cookies through browser settings. Blocking essential authentication cookies may prevent sign-in or protected customer pages from working.

A dedicated cookie-preference centre has not been implemented in the current customer application because no non-essential analytics or marketing cookies are used.

This notice should be reviewed when the live application, infrastructure, support tooling, analytics, marketing, or third-party scripts change.