Brimlo · autonomo.space
Cookie Policy
Cookies and similar technologies on autonomo.space under Article 22.2 LSSI-CE and AEPD guidance.
Last updated: 6 September 2026
1. What this policy covers
Brimlo uses cookies and browser storage such as localStorage/sessionStorage for authentication, security, preferences, analytics and, if consented, advertising measurement. Non-essential technologies remain disabled until the user makes a choice.
2. Strictly necessary
Essential storage is used for authentication/session handling, security, routing and saving the user's cookie choice. It is required to provide the service and cannot be switched off through the consent panel. Essential technologies are not used for advertising.
3. Analytics
If Analytics is enabled, Brimlo may load Google Analytics/Google tag infrastructure to measure aggregated site usage and Smartlook (EU configuration) for session/interaction analytics. Smartlook is configured so form inputs and sensitive on-page values are not intentionally recorded. Analytics consent can be withdrawn at any time.
4. Personalization
Personalization storage remembers non-essential UI choices such as language, theme and workspace preferences. Disabling it may cause preferences to be reset but does not prevent core use of Brimlo.
5. Marketing — Meta
If Marketing is enabled, Brimlo loads Meta Pixel for advertising measurement, attribution and audience/remarketing functions using Dataset/Pixel ID 2214990032736476. Meta may create/read identifiers such as _fbp and, where an ad click provides it, _fbc. For a consented registration or trial event Brimlo may also send the matching conversion through Meta Conversions API, including hashed matching identifiers and technical request data. Browser and server copies use a shared event ID for deduplication.
6. Providers and typical storage
First-party Brimlo storage includes the consent record and product preferences. Google may set analytics identifiers such as _ga when Analytics is enabled. Meta may set _fbp/_fbc when Marketing is enabled. Smartlook may use cookies/local storage needed to associate visits and sessions when Analytics is enabled. Exact names and lifetimes can change when provider SDKs change; the purpose category and consent choice continue to control whether the optional provider is loaded.
7. Accept, reject and configure
The first layer offers Accept all and Reject optional at the same level, plus granular settings. Consent is a positive choice: inactivity or simply continuing to browse is not treated as consent. Optional consent is separate from accepting the Terms or registering for Brimlo.
8. Withdraw or change consent
Cookie settings can be reopened at any time from the permanent link on autonomo.space and inside the Brimlo workspace. Withdrawing consent stops new optional events. Where technically possible, Brimlo also clears the relevant first-party analytics/advertising identifiers. Provider-side data already lawfully received may remain subject to that provider's retention rules.
9. Consent renewal
We may ask for consent again when purposes or providers materially change, where law/guidance requires renewal, or where an older consent was collected under a materially different banner. We do not silently convert a previous non-marketing choice into marketing consent.