Cookie Policy
Last updated: September 23, 2026
BTR and its contributors (collectively “BTR”, “we”, “us”, “our”) respect your privacy and will provide the information and tools you need to manage your cookie preferences. This policy covers the BTR Interface and applies to residents of the EEA. Outside the EEA, see our privacy policy.
1. Definition
A cookie is a small file which asks permission to be placed on your computer’s hard drive. Once you agree, it is added and lets a web application analyze traffic, know when you visit a site, respond to you as an individual, monitor which pages you find useful, and remember your preferences so the site can be tailored to them.
BTR-operated websites set no first-party tracking cookies. Infrastructure providers (e.g., Cloudflare) may set strictly-necessary cookies (__cf_bm, cf_clearance) for security and rate-limiting; those are listed in 3.2. Any cookie used beyond strictly-necessary would be limited to essential site functionality or aggregate analytics. The Interface uses no marketing, advertising, or cross-site tracking cookies. If that ever changes, BTR will provide the relevant information and tools so that you can manage your cookie preferences.
2. Cookies typology
BTR v1’s websites use no tracking or marketing related cookies.
2.1. Definition
Types of cookies we could use in the future:
- Essential: cookies essential to the functioning of the Interface (for example, session continuity, security challenges, and disclaimer-acceptance state). Disabling them may prevent parts of the Interface from working.
- Analytical: aggregate cookies that would help us improve the Interface. Any such data would be anonymized.
The Interface does not use marketing, advertising, or cross-site tracking cookies, and does not collect information through cookies that could identify you as an individual.
2.2. Cookies cannot
- store any personally identifiable information such as passwords
- access any other information stored on your computer
- compromise the security of your device(s)
2.3. Cookies can
- monitor the number of people using the website
- see how people arrive at the website (for example, via search engine or via a link)
- gather technical information such as approximate geographical location and web-browser type
- recall certain settings and preferences to make the website easier to use.
3. How to manage your cookie preferences
If BTR uses cookies in the future, you will be provided with a dedicated settings panel allowing to disable non-critical cookies, and this document will be updated accordingly.
To find out more about how you can block, delete or manage cookies, please visit https://www.aboutcookies.org. We comply with all applicable EU laws that govern the handling of cookies. How we handle your data: Privacy Policy.
Questions: contact@btr.markets.
3.1. Data rights
Access, correction, erasure and your other data rights: Privacy Policy §5.
3.2. Strictly-necessary cookies in use
| Cookie | Provider | Category | Duration | Purpose |
|---|---|---|---|---|
__cf_bm | Cloudflare | Strictly necessary | 30 min | Bot-management; distinguishes humans from automated traffic |
cf_clearance | Cloudflare | Strictly necessary | 30 days | Records that the visitor passed a Cloudflare security challenge |
These cookies are set by infrastructure providers and are required to deliver the Service securely. They do not track users across sites and carry no marketing payload.
4. Local storage and application state
The Interface uses browser localStorage and sessionStorage (which are not cookies but serve a related role) for client-side state: UI preferences (theme, slippage tolerance defaults, last-selected pool, last-connected wallet provider hint), disclaimer-acceptance state, and ephemeral application state. Three items are sent to BTR servers: the queue of usage events (Privacy Policy §2.3), sent periodically and on your next visit if you leave first; the referral session id, if you entered with an invite code, sent to the referral service when you accept the terms and with your wallet address when you connect; and, for operator accounts only, sign-in tokens. You can clear all of it at any time via your browser’s site-data controls.
5. Third-party endpoints (non-cookie tracking)
Independent of cookies, your interactions with third parties surface metadata that BTR does not control:
- RPC endpoints may log your IP address and call patterns.
- Wallet providers (browser extension wallets, mobile-wallet relays) may log connection events and signed payloads.
Refer to each provider’s privacy policy. You may use a self-hosted RPC, a self-hosted relay, or other operational measures to limit third-party exposure.