This page explains the limited functional cookies and browser storage Aluma uses for secure sign-in, session continuity, and connected-service handoffs.
Aluma uses cookies in a limited functional way tied to security, sign-in continuity, and integration handoffs.
01
Essential authentication cookies
The current product uses essential cookies to keep practitioners and clients signed in through Supabase-backed authentication and to maintain secure access across protected routes.
02
Temporary integration cookies
When a practitioner connects Google Calendar or Zoom, Aluma uses short-lived state cookies to validate the OAuth handoff and reduce the risk of tampering or cross-site request forgery during that connection flow.
03
No ad-tech cookie stack
The current public site and application are not built around advertising trackers or a marketing-cookie layer. Aluma’s browser storage use is tied to product function, security, and connected-service flows rather than behavioral ad targeting.
04
Managing cookies
Blocking essential cookies may prevent sign-in, workspace continuity, or integration handoffs from working correctly. Browser-level controls still remain available to the user, but some product features depend on these cookies to operate safely.