Last updated: 2026-07-16

What data do we collect?

• Authentication: email and password, to sign in via Supabase Auth. The session token is stored locally in the extension. We never store the password — it is sent to Supabase Auth, which hashes it.
• Alert responses: whether the user accepted, refused, or did not respond to an alert.
• Deal reference & metadata: the HubSpot deal ID plus non-personal deal metadata (formation, acquisition channel, campaign, HubSpot link). We never store the prospect's personal data (name, phone, notes).
• Technical & presence telemetry: extension health signals — service-worker heartbeats, connection (WebSocket) state, alert delivery timing — and, to tell a technical freeze apart from an absent user: presence state (active / idle / locked, via the browser's idle API), whether a browser tab is playing audio, and basic device signals (CPU load, free memory, battery, network quality, OS/Chrome/install profile). Each signal is tagged with the user's email. We do not record keystrokes, browsing history, page content, or clicks outside the extension.

How do we use this data?

• Email + password: solely to authenticate the user and route alerts to the correct representative. Passwords are hashed by Supabase Auth (never plaintext).
• Alert responses: to track alert status and run the cascade (passing an alert to the next teammate when one declines or doesn't respond).
• Deal reference/metadata: solely to link each alert to its source deal in HubSpot for follow-up.
• Technical & presence telemetry: solely to detect and resolve reliability issues, and to distinguish a genuine technical failure from a user who was simply away from their desk. Used for internal diagnostics only — never for performance reviews, ranking, or individual surveillance.

Data storage Stored securely on Supabase (hosted on AWS, [à confirmer : eu-west-1 / Ireland]). Row-Level Security is enforced at the database level: each user can access only their own data.

Data flow & processors Data flows within LiveMentor's own systems: HubSpot (source deal) → N8N (cascade orchestration) → Supabase (storage & realtime) → the extension. Internal reliability diagnostics are performed with AI-assisted tooling (Anthropic Claude, read-only access to telemetry). We do not sell user data, nor share it with any third party for their own purposes.

Data retention

• Raw telemetry: automatically deleted after 30 days.
• Alert records and aggregated diagnostic facts (used for reliability KPIs): retained for operational and analytics purposes.
• Users can request deletion of their data at any time by contacting the administrator.

Contact: [email protected]