1. Scope and browser storage
Cookies are small values a website asks your browser to store and send with relevant requests. Local storage keeps information in the browser until it is cleared, while session storage is normally limited to a browser tab's session. These technologies serve different purposes and are described separately below. This draft reflects the reviewed website code; the final operator must also confirm cookies and storage introduced by hosting infrastructure and external providers.
2. Session authentication
The sid cookie supports signed-in sessions and access to protected account features. The website passes the session identifier to its authentication service and does not expose this HttpOnly cookie to page scripts. The cookie does not contain a wallet seed phrase or private key. Its lifetime and renewal are controlled by the authentication system and must be confirmed in the final cookie inventory. Clearing it may sign you out.
3. Language preference
The lang cookie records the website language. The merchant website currently uses English and sets this cookie with a one-year maximum age. The checkout may use a supported language based on a saved preference or browser language. A persistent cookie can expire earlier if you clear your browser data or the browser removes it. This is a preference function rather than an advertising identifier.
4. Appearance preference in local storage
The cryptium-theme local-storage entry remembers your light, dark or system appearance choice. It is not a cookie and is not automatically sent with every request. The website reads it in your browser to apply the selected appearance. It has no fixed application expiry and normally remains until changed or cleared, subject to the browser's storage rules.
5. Temporary actions in session storage
The merchant console uses tab-scoped session storage to preserve the context of certain invoice, withdrawal, webhook-test and invitation actions across a reload. This helps the interface resume an unresolved action rather than accidentally submit it again. Depending on the feature, entries may include operation identifiers, request context or an invitation token. They are removed when the relevant flow clears them or the tab session ends, subject to browser restoration behaviour. Avoid using a shared or untrusted browser session for account management.
6. External sign-in and provider storage
If you choose an external sign-in method, the authentication flow may use temporary security cookies or provider-managed storage to validate the return to the service. The provider's own website can set cookies under its own policy. This draft does not set a lifetime for those external cookies or claim that CryptiumPay controls them. The final inventory must identify the enabled providers and the security cookies used by the deployed authentication flow.
7. Analytics, advertising and consent
No optional analytics or advertising tracker was identified in the reviewed application source. Hosting or other deployed integrations must be assessed separately before this statement becomes a final notice. If optional tracking is introduced, explain its purpose, provider and lifetime, obtain consent before storage where required and provide a way to change that choice. Viewing a policy page or accepting merchant terms is not, by itself, consent to optional tracking.
8. Managing cookies and storage
Use your browser's site-data settings to inspect, delete or restrict cookies and local storage. Clearing session storage or using a new tab may reset the context of a pending action; check its status before submitting it again. Blocking essential session storage or cookies can affect sign-in and account features. Private browsing does not make blockchain transfers private or prevent data processing needed to provide a requested service.
9. Contact and details to complete
For personal-information questions, read the Privacy Policy and contact support. Before publication, identify the responsible operator, complete a deployed cookie inventory covering authentication and infrastructure, confirm names, providers, purposes and lifetimes, and verify any consent controls needed for optional storage. Reassess this policy when authentication, hosting, analytics or browser-storage behaviour changes.