Digital Asset ExchangeScope and purpose
Cookies are small values stored in a browser and sent with requests to the relevant website. Aldenex uses Supabase server-side authentication cookies to recognise account sessions, complete authentication flows and refresh access. These support account functions you request.
The current application does not implement advertising pixels, behavioural advertising cookies or optional analytics integration. This policy describes its authentication storage, not technologies merely common on other websites. Independent sites have their own policies.
Session cookies
The session cookie uses a project-specific name in the form sb-<project-ref>-auth-token. Large values can be split into numbered chunks such as .0 and .1. It carries authentication state, including session tokens, and must be treated as confidential access material.
These are used by Aldenex’s first-party pages and server, with Supabase supplying authentication. They are not advertising identifiers. Naming them by project does not mean unrelated websites can read the account.
Authentication-flow verifier
Sign-in, confirmation or recovery flows can use sb-<project-ref>-auth-token-code-verifier. It supports Proof Key for Code Exchange, or PKCE, linking the returning flow to the browser that initiated it.
The library clears the verifier when the flow consumes or clears it. An abandoned flow can leave it until cleanup or expiry. Deleting it before completion may require restarting the flow in the appropriate browser.
Lifetime and other storage
The installed Supabase server-side library sets a default cookie maximum age of up to 400 days and can rewrite values as session state changes. That is not a promise of 400 days of authorised access: token expiry, refresh availability, logout and server-side rules separately determine session validity.
Signing out clears the application’s authentication cookies for the relevant session. Browsers may remove them earlier. Closing a tab alone can leave persistent cookies; sign out on shared devices.
The integration uses cookies rather than a separate application-managed local-storage login token. No additional application preference or marketing storage is included. Never copy cookie values into support messages or screenshots.
Essential use and your controls
Authentication storage provides requested account functions. Where the applicable strictly necessary exemption applies, optional-cookie consent is not required for that purpose. This is not an exemption for unrelated uses of the identifier.
You can inspect, block or delete cookies in browser settings. Blocking essential storage can prevent sign-in or interrupt confirmation and recovery. It does not erase server financial records or close the account.
Future optional storage needs an explanation and the consent or other framework applicable to its actual purpose. Continuing to browse is not treated here as consent to advertising.
External services and privacy
Email and Telegram links open independent services. The support link does not embed a Telegram tracking widget. Following it can involve the external service’s own data processing and storage.
The Privacy Policy explains associated account and technical data, providers and rights. Cookies differ from server logs: blocking them does not necessarily prevent a server receiving an IP address or recording a request.
Changes and questions
This edition describes the current application integration. Authentication, hosting or optional-integration changes require review of the deployed storage inventory and notice. No hosting cookie, consent tool or analytics provider is claimed to be installed without confirmation.
Company contact: ADEMEX TECHNOLOGIES LTD, registered in England and Wales under company number 15576900, with its registered office at 71–75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom. For questions, requests or complaints, email support@aldenex.com or write to the registered office. Operational support is also available through @adelmex_support on Telegram. Never send passwords, authentication tokens, private keys or recovery phrases.