1. Your choices
You can reject, accept or configure optional technologies from the initial notice and from “Privacy preferences” in the footer. Rejecting must be as accessible as accepting. The bag, payment and human support remain available without optional advertising or analytics.
Global Privacy Control, when communicated by the browser, prevents advertising from being enabled in this implementation. Withdrawing permission stops new optional events and removes known first-party advertising cookies; technologies already operated by third parties on their domains are also managed under their tools and policies.
2. Implementation inventory
| Technology | Purpose | Duration/initial configuration |
|---|---|---|
__Host-cuvex in production (cuvex_session in development) |
Bag session, associated CSRF, verified access and operational preferences | Session; one-hour expiry on the server; HttpOnly, Secure in production, SameSite=Lax |
csrftoken |
Prevent unauthorised requests in forms and API | Django's technical duration; not used for advertising |
cuvex_preferences |
Remember the signed privacy choice | Up to 180 days; not used for advertising identification |
cuvex_visitor |
Random identifier for new/returning visitors with analytics accepted | Up to 90 days; deleted when analytics permission is withdrawn |
| First-party event records | Visits, purchase actions and approximate country | Initial retention of 90 days; no IP address stored in that table |
_gcl_au and Google Ads technologies |
Campaign/conversion measurement when Google Ads is configured and advertising is accepted | Duration set by Google; review the actual inventory before enabling each configuration |
_fbp, _fbc and Meta technologies |
Consented measurement and attribution, with event deduplication | Duration set by Meta; review the actual inventory before enabling |
| BTCPay Server and Cuvex SCP | Session and security for the requested payment; only the enabled method | Necessary payment-screen technologies; these do not themselves authorize optional analytics or advertising |
| YouTube | Videos opened by the user | The service's technologies apply after the link is opened |
The inventory must be validated against the configuration actually published. Pasting arbitrary scripts into the manager is not permitted: enabled providers have typed fields and specific controls. Adding another provider requires reviewing its processing and expanding this inventory before enabling it.
3. Analytics and advertising
First-party analytics uses random identifiers with consent. Observed visitors and conversions do not represent all visitors and are not supplemented through fingerprinting. Where available, the country comes from a CloudFront estimate; we do not request GPS or promise an exact location.
Advertising may transmit click/browser identifiers and a purchase event with the amount, currency and technical reference. Names, emails and addresses are not sent by the included advertising modules. This does not make advertising identifiers anonymous data. Rejecting advertising prevents these optional transmissions.
4. Management and contact
You can change your choice in the footer or delete cookies through your browser. Deleting necessary cookies may clear the session or require you to verify access again. For information about controllers, transfers and rights, consult the privacy policy or write to sato@cuvex.io.
Payments and scope of this version
New orders have a USD reference price. BTC is accepted through BTCPay Server and, only when enabled, native USDC on Solana through Cuvex SCP. Card payments are not offered. The sales terms govern exchange quotes and refunds. This version does not retrospectively change contracts or rights arising from earlier purchases.