1. Scope
This notice covers cookies and browser storage used by the Carrierintel website and account flows. Cookies are small values sent with web requests. Local storage is data retained by the browser and is not automatically sent with each request.
2. Storage used in the current build
Authentication and security cookies
Better Auth sets cookies needed to create and maintain a signed-in session and may set short-lived cookies for authentication and two-factor flows. Session cookies are configured as HTTP-only and SameSite=Lax; production configuration requires HTTPS so secure transport flags can be applied.
Consent preference in local storage
The cookie banner stores either accepted or rejected under carrierintel.cookie-consent.v1. In the current build, this value only remembers the banner choice. It does not activate an analytics provider.
Analytics
No optional browser analytics provider is wired into the current application code. Optional analytics must not be enabled in production until the provider, exact storage, retention, consent behavior, and privacy disclosures are documented and tested.
3. Why storage is used
- authenticate users and maintain secure sessions;
- complete sign-in, verification, and two-factor flows;
- remember the user's consent-banner choice;
- protect the Service from abuse and unauthorized access.
4. User controls
Users can remove the saved banner preference through browser site-data settings, which causes the banner to appear again. Blocking authentication cookies can prevent sign-in and account features from working. Signing out invalidates the corresponding server-side session.
[PRE-PROD TODO: implement and test consent enforcement before adding any non-essential storage]
5. Production cookie inventory
Before launch, Carrierintel must publish a table containing each cookie or storage key, its provider, purpose, category, first- or third-party status, data stored, lifetime, and whether consent is required.
[PRE-PROD TODO: generate the inventory against the deployed production domains and verify it in a browser]
6. Contact and changes
Cookie questions will be sent to [PRE-PROD TODO: privacy contact email]. This notice becomes effective only after the production inventory, consent behavior, applicable jurisdictions, and legal review are complete.