What browser storage does
Engagivo uses cookies and browser storage for authentication, request protection and selected interface preferences. The API issues host-only session and CSRF cookies through the frontend origin. Necessary storage is used to operate the service you request; optional measurement should remain disabled until you choose it.
Essential session and request protection
Production session and CSRF cookies use the __Host-engagivo_session and __Host-engagivo_csrf defaults. Session cookies authenticate requests; the CSRF cookie protects state-changing requests. The default configured session lifetime is eight hours, but deployment configuration may differ. The server Google OAuth flow can use __Host-engagivo_google_oauth for a ten-minute return-state check. Signing out clears the session cookies; blocking necessary cookies can prevent sign-in.
Preferences and authentication providers
The browser can save your selected color mode under engagivo.color-mode and dashboard navigation preferences. Authentication with Firebase/Google can use its own browser storage to complete a sign-in you request. The relevant provider controls its separate services. Do not clear all site storage while relying on unsaved work; doing so can remove preferences and authentication state.
Optional analytics
When configured and enabled by your choice, Google Firebase Analytics measures permitted public page visits and a Google login event. The implementation excludes query strings, emails, tokens, account IDs and private workspace routes from those events, and disables Google signals and advertising personalization in its configuration. Provider-generated measurement identifiers can still be used; this is not a claim of anonymous processing or zero provider retention. Analytics is optional and declining it does not block account access.
Change your choice
Use Cookie choices to enable or decline optional analytics. The preference is saved on this browser; another browser may need its own choice. Withdrawing consent stops future application analytics events and disables an initialized analytics instance. Previously collected events and provider storage may require the provider’s deletion process or browser clearing. Your browser settings also allow cookie removal and blocking.
Inventory and approval
Before this draft becomes an approved notice, confirm production cookie names, configured lifetimes, Firebase measurement settings and any additional providers. Applicable consent rules and an effective date remain approval requirements; contact Engagivo through /contact. The Privacy draft describes the wider processing and request route.
Facts needed before approval
- Engagivo policy contact route and responsibility for handling requests
- Applicable jurisdictions, legal grounds and any age restrictions
- Current provider inventory, processing locations and transfer arrangements
- Production retention settings, backup expiry and deletion procedures
- Trial, renewal, cancellation, refund and support commitments
- Qualified policy review and an approved effective date