Transparency
What we collect and how sign-in works (data per feature, Clerk, roles).
Effective date: April 3, 2026. This document explains what data we collect, how authentication works, and what each feature accesses.
1. Authentication
We use Clerk for authentication. When you sign in, Clerk sets strictly necessary session cookies (__clerk_*, __session). These are required for the platform to function and are not subject to cookie consent. No passwords are stored on our servers.
2. Data Collected Per Feature
Research (Surveys): Survey definitions, questions, response data (may include PII if respondents provide it), distribution links, completion timestamps, device type, geo-coordinates (with explicit consent).
Analytics: Aggregated metrics derived from survey responses. Account health scores, CLV predictions, and campaign models use organization-provided data. No additional PII is collected.
AI Tools: Smart Desk indexes documents you upload. Front Desk processes conversation text. Synthetic Data generates fictional personas — no real PII is used. All AI processing uses Groq (see Subprocessors).
3. Roles & Permissions
Platform roles (owner, admin, member, viewer) control what data each user can access. Row-Level Security (RLS) in PostgreSQL ensures that users can only query data belonging to their organization. Role assignments are stored in our database and synchronized with Clerk metadata for session validation.
4. Analytics Tracking
We use self-hosted Matomo analytics (on our own servers, not shared with third parties). Matomo tracking is only activated after you explicitly accept analytics cookies via the cookie consent banner. If you decline, no analytics data is collected.