Privacy policy

PULSO is an employee-engagement platform sold to employers ("Workspaces"). This policy explains how we collect and process data when (a) Workspace administrators sign up and use the dashboard, and (b) employees of those Workspaces complete check-in interviews. If you are an employee, the controller of your data is your employer; PULSO acts as a data processor on their behalf.

• From admins: name, email, password hash, workspace name, industry, employee-count band, billing address (via Stripe).
• From employees: the name they type into the check-in form, the department they pick, the language they conduct the check-in in, the full conversation transcript, and the AI-derived sentiment scores. We do not collect IP addresses or device identifiers beyond what's needed for rate limiting.
• Operational telemetry: aggregated usage counters (check-ins per month, distinct employees per month) and error logs without personally-identifiable content.

Each check-in is forwarded to the Anthropic Claude API for two purposes: (a) generating empathetic follow-up questions during the conversation, and (b) producing a structured engagement score, themes, notable quotes, and recommended actions afterwards. Anthropic processes the data on PULSO's behalf under their Privacy Policy. Anthropic does not train models on customer prompts or responses sent through the API.

Workspaces choose how long check-in transcripts are kept. Each campaign supports an "Anonymize after 90 days" toggle — when enabled, the employee_name field is replaced with "Employee #N" while keeping the aggregate scoring intact. Workspaces can also delete a single employee, a single campaign, or the entire workspace at any time from /dashboard/settings (see Sections 6 & 7).

• Anthropic, PBC — Claude API for interview conversation and post-interview scoring.
• Supabase, Inc. — managed PostgreSQL, authentication, Edge Functions, file storage.
• Stripe, Inc. — subscription billing and payment-method storage. PULSO never sees full card data.
• Vercel, Inc. — hosting and serverless runtime for the web app.

Workspace owners and admins can request a full JSON export of every byte we hold for their workspace from the Settings page. Exports include: company profile, members, departments, campaigns, interviews (with transcripts), interview scores, and usage history. Limited to one export per hour per workspace to prevent abuse.

Workspace owners can delete (a) all data for one named employee, (b) a single campaign and all its check-ins, or (c) the entire workspace. Deletions are immediate and irreversible — exports first if you need a record. Foreign keys cascade so a workspace deletion removes every related row in our database.

We use a single first-party cookie issued by Supabase Auth to keep dashboard sessions signed in. We do not use any tracking, analytics, or advertising cookies. The first time you visit, a small banner asks you to acknowledge this — your choice is stored in localStorage, never on a server.

All traffic is HTTPS. Database access is enforced via row-level security so one workspace cannot read another's data even with valid credentials. The Anthropic API key never reaches the browser — it lives only on the server side. Employee transcripts are never shown to other employees in the same workspace; only authenticated admins can see them.

Data is stored in Supabase's US region by default. If your jurisdiction requires data residency in the EU, write to us and we will provision an EU-region project at the Professional or Enterprise tier.

Questions, complaints, or data requests: privacy@pulso.ai. We aim to respond within 30 days.