Cookie Policy

1. “Zero-Tracking” Philosophy and Pure Performance

At PlanoBinario, we operate under a purist engineering philosophy: unnecessary tracking degrades application performance and compromises user privacy.

By design, our architecture avoids the mass injection of commercial tracking scripts and invasive third-party analytics tools. We do not sell user profiles and we do not use advertising targeting cookies.

2. What is a Cookie from a technical perspective?

A cookie is a small text file (payload) injected by our server or executed by the browser (client-side) on your device. We use them exclusively to resolve HTTP state issues, manage cryptographic sessions, or purge caches on the CDN.

3. Typology of Cookies in our Infrastructure

Our platform is restricted to the use of Strictly Necessary (Technical) Cookies. These do not require explicit consent under the ePrivacy Directive, as the application would fail if they are blocked.

A. Session and State Cookies (Core)

• JWT Session Token: If you access protected dashboards, we store encrypted JSON Web Tokens in HttpOnly cookies to verify your identity and mitigate CSRF and XSS attacks.
• UI Preferences: Boolean information (such as theme=dark or language preferences) saved in localStorage to prevent Cumulative Layout Shifts (CLS) during initial rendering.

B. Performance and Security Cookies (Edge)

• Cloudflare (e.g., __cf_bm): Cookies injected at the network layer (CDN) to detect malicious bot traffic, prevent DDoS attacks, and manage load balancing. They are mandatory for secure packet routing.

4. Minimalist Analytics

To understand the behavior of our infrastructure and detect navigational bottlenecks, we may employ self-hosted or privacy-first analytics tools (such as Vercel Analytics or Plausible). These tools do not generate device fingerprinting nor do they inject persistent cookies into your browser, operating in full compliance with GDPR and CCPA regulations.

5. User-Level Control and Debugging

You have total control over your execution environment. To purge our cookies or the localStorage state, you can use your browser’s developer console (DevTools) or access standard security settings:

1. In Chromium/Chrome: Settings > Privacy and security > Cookies.
2. In Firefox: Settings > Privacy & Security > Cookies and Site Data.
3. In Safari: Preferences > Privacy > Block all cookies.

Please note that blocking technical network cookies (Cloudflare) may trigger our firewalls to identify your connection as a network threat, thereby blocking your access to the platform.