COOKIE POLICY
What we store on your device, and what we do with it.
Last updated: 28 July 2026
This policy explains the cookies and similar identifiers used on apraemio.com: which ones exist, who sets them, what each is for, and how to turn them off. It applies to this website. The Apraemio Dashboard, where accounts and token purchases live, and the documentation site at learn.apraemio.com are covered by their own notices.
A cookie is a small piece of data a site asks your browser to keep and send back on your next request. Pixels, tags and browser storage do much the same job by other means, and this policy treats them all the same way, because the question that matters is not the mechanism but whether something is following you.
On this page
1. How consent works here
Only the strictly necessary cookie is set when you arrive. Nothing in the analytics, marketing or functional categories loads until you choose to allow it — the scripts themselves are not fetched, so no request reaches Google, Meta, X or Crisp before you have said yes.
You are asked once. Your answer is recorded, and you can change it at any time — see withdrawing consent below. Refusing everything except the strictly necessary category leaves the site fully usable; nothing is gated behind a cookie.
2. Strictly necessary
One cookie, apra_consent, records which categories you accepted or refused. Without it the site would have to ask you again on every page, which is worse for you than storing the answer.
This category is set under Article 5(3) of the ePrivacy Directive, which exempts storage strictly necessary to provide a service the user asked for. It cannot be switched off from the banner, but you can delete it in your browser like any other cookie — you will then be asked again on your next visit.
3. Analytics — Google Analytics 4
Google Analytics 4 tells us how many people reach the site, which pages they read, and where they stop. We use it to find out which explanations are failing — a page nobody finishes is usually a page written badly, and this is how we find those.
The measurement is aggregate. We do not upload your name, email or wallet address to Google, and we do not use Analytics to build profiles of individuals or to target advertising. Google is a separate controller for the data it receives; its own terms govern what it does with it.
Legal basis: your consent, Article 6(1)(a) GDPR, together with Article 5(3) of the ePrivacy Directive.
4. Marketing — Meta Pixel and X Pixel
The Meta (Facebook) Pixel and the X (Twitter) Pixel report back to those platforms when someone who saw one of our ads reaches this site. That is how we learn whether an advert did anything, and how we avoid showing the same one to the same person indefinitely.
Both platforms may also use what they receive for their own advertising purposes, including building audiences and matching your activity here to your account with them. That is a real cost of allowing this category, and it is the reason it is off by default. If you would rather we could not do this, refuse the marketing category — nothing on the site changes.
Legal basis: your consent, Article 6(1)(a) GDPR, together with Article 5(3) of the ePrivacy Directive.
5. Functional — Crisp chat
Crisp runs the chat widget, including its automated first responder. It stores a session identifier so a conversation survives you moving between pages, and it keeps that identifier in your browser's local storage as well as in a cookie. Local storage is not a cookie, but it does the same thing to you, so it is listed here rather than left out on a technicality.
What you type into the chat is stored by Crisp on our behalf and is covered by the Privacy Policy. Do not send private keys, seed phrases or passwords through the chat. Nobody at Apraemio will ever ask you for them.
Legal basis: your consent, Article 6(1)(a) GDPR, together with Article 5(3) of the ePrivacy Directive.
6. The cookies in full
Providers change their own defaults from time to time. Where a lifetime is given as a maximum, the provider may set a shorter one.
| Name | Set by | What it does | Category | Expires |
|---|---|---|---|---|
apra_consent | Apraemio | Records which cookie categories you accepted or refused, so you are not asked again on every page. | Strictly necessary | 12 months |
_ga | Tells one browser apart from another so visits can be counted. It does not carry your name or email. | Analytics | 2 years | |
_ga_<container> | Holds the session state Google Analytics 4 counts against. The suffix is this site's measurement ID. | Analytics | 2 years | |
_fbp | Meta | Identifies the browser across visits so Meta can report whether an ad led to anything here. | Marketing | 3 months |
_fbc | Meta | Stores the click identifier from a Meta ad. Set only if you arrived by clicking one. | Marketing | 3 months |
muc_ads | X | Measures the performance of ads on X and limits how often the same one is shown to you. | Marketing | up to 2 years |
personalization_id | X | Ties activity on this site to X's advertising profile for your browser. | Marketing | up to 2 years |
crisp-client/session/… | Crisp | Keeps a chat conversation attached to the same visitor from one page to the next, so a reply does not arrive in an empty window. | Functional | 6 months |
7. Where this data goes
Google, Meta and X are established in the United States and process data there. Crisp is established in France and stores its data in the European Union.
For transfers to the United States we rely on the European Commission's adequacy decision for the EU–US Data Privacy Framework where the recipient is certified under it, and on the Commission's Standard Contractual Clauses together with supplementary measures otherwise. You can ask us for a copy of the safeguards that apply by writing to business@apraemio.com.
Apraemio Ltd. is registered in the British Virgin Islands, which the European Commission has not found adequate. Transfers to us are covered by Standard Contractual Clauses. The Privacy Policy sets out how we process personal data more generally.
8. Withdrawing consent
You can change or withdraw your answer at any time, and doing so is no harder than giving it. Withdrawal takes effect immediately and does not affect processing that already happened while consent was in place.
Three routes, any of which works:
- Use the “Cookie settings” control in the site footer, on any page, and change your selection.
- Delete this site's cookies in your browser. You will be asked again on your next visit.
- Email business@apraemio.com and we will action it.
Independently of us, Google offers a browser add-on that opts you out of Google Analytics on every site, and both Meta and X have ad settings in your account with them that limit what they do with what they collect.
9. Browser controls
Every current browser can block or delete cookies, and most can block third-party cookies outright while leaving first-party ones alone. The controls sit under Settings in Chrome, Edge and Firefox, and under Preferences → Privacy in Safari.
Blocking cookies at the browser level is more thorough than any consent banner, because it also covers sites that ask badly. Nothing on this site requires cookies to work, so blocking them here costs you nothing.
10. Changes to this policy
When we add or remove a provider, this page changes and the date at the top changes with it. If a change widens what is collected or what it is used for, we will ask for consent again rather than rely on an answer you gave to a different question.
11. Contact
Apraemio Ltd., registration no. 1573637, Craigmur Chambers, Road Town, Tortola, VG1110, British Virgin Islands.
Email business@apraemio.com or call +36 1 814 2129, weekdays 09:00–17:00 CET. The Privacy Policy sets out your rights over the data described here and how to exercise them.