Cookie Policy
Last updated: August 22, 2026
BTR and its contributors (collectively “BTR”, “we”, “us”, “our”) fully respect your privacy and are committed to ensuring that we provide you with the relevant information and tools so that you can manage your cookie preferences. This policy applies to the BTR Interface.
This Cookie Policy applies to residents of the EEA. If you’re a resident outside of the EEA, please refer to 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, the file is added and the cookie helps analyze web traffic or lets businesses know when you visit a particular site. Cookies allow web applications to respond to you as an individual. Cookies help provide you with services eg. by enabling monitoring the pages that you find useful and tailor our website to your needs, likes and dislikes or by gathering and remembering information about your preferences.
BTR-operated websites do not set first-party tracking cookies. However, infrastructure providers (e.g., Cloudflare) may set strictly-necessary cookies (__cf_bm, cf_clearance) for security and rate-limiting purposes. These are disclosed below. Any cookies used beyond strictly-necessary would be limited to essential site functionality or aggregate analytics. The Interface does not use marketing, advertising, or cross-site tracking cookies. If this 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 do not use 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
In the event of BTR using 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. For more information on how we handle your data please see our Privacy Policy.
If you have any questions or concerns, please reach out to the team at contact@btr.markets or on discord.
3.1. Data subject access requests (DSAR)
EU/EEA users may exercise rights under GDPR Art. 15-22 (access, rectification, erasure, restriction, portability, objection) by emailing privacy@btr.markets. Response SLA: 30 calendar days. UK users invoke equivalent rights under UK GDPR / DPA 2018. California users may exercise CCPA rights via the same endpoint.
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 purely client-side functionality. Stored data may include UI preferences (theme, slippage tolerance defaults, last-selected pool, last-connected wallet provider hint), disclaimer-acceptance state, and ephemeral application state. With one exception, none of this data is transmitted to BTR servers. The exception is a small queue of usage events (see Privacy Policy section 2.3) held in localStorage and sent to us periodically; if you leave before it is sent, it is sent on your next visit. All storage is local to your browser and you can clear 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.