Sys_Compliance
Cookie Policy
Last Updated: 18 jun 2026
[01] Local State Architecture
Our infrastructure utilizes standard HTTP cookies and browser LocalStorage to maintain functional state and routing preferences. A "cookie" is a small text file downloaded onto your device when you access our network, allowing us to recognize your device and store some information about your preferences or past actions.
[02] Strictly Necessary Cookies
These cookies are essential for the core functionality of our digital infrastructure. You cannot opt-out of these cookies without severely degrading the performance of the application.
- Consent Management: We store a localized boolean in your browser's LocalStorage (`bb_cookie_consent`) to record whether you have accepted or dismissed our cookie banner, preventing it from constantly reappearing on subsequent visits.
- Routing/i18n: `NEXT_LOCALE` is utilized to remember your preferred language rendering (e.g., English, French, Georgian).
[03] Analytics & Telemetry Cookies
With your consent, we deploy performance monitoring and analytical cookies to measure network latency and user interaction.
- Vercel Speed Insights: Used strictly to measure Core Web Vitals (Largest Contentful Paint, rendering stability). No personally identifiable information (PII) is captured.
- Google Analytics 4 (GA4): We utilize GA4 to aggregate data regarding traffic volumes and geographic routing. Google may set its own cookies (`_ga`, `_ga_*`) to distinguish unique users across sessions.
[04] Opt-Out Procedures
You have full control over the telemetry data you provide to our network. To manage your cookie preferences:
- Browser Controls: You can configure your browser to block or alert you about these cookies. Check the "Help" menu of your browser for instructions.
- Google Analytics Opt-Out: To prevent your data from being used by Google Analytics globally, you can install the official Google Analytics Opt-out Browser Add-on.
- Local Reset: You may clear your browser's LocalStorage and cache at any time to reset our `bb_cookie_consent` state.