Trust Center
Data Handling & Privacy
This page is maintained by EQIQs to explain how we collect, store, encrypt, retain, and delete customer data across the platform.
What data we collect
- Assessment responses: raw inputs from the 21 psychometric frameworks (MBTI, Enneagram, Big Five, DISC, EQ, RIASEC, and others) used to generate your EQIQs™ profile.
- Profile fields: name, email, job title, optional demographic fields, and social links you choose to add.
- Organizational metadata: workspace name, roles, team assignments, and relationship graphs used for compatibility scoring.
- Product telemetry: event logs and error traces used to keep the platform reliable. Consent-gated analytics vendors receive no data until you opt in.
- Billing data: handled by Stripe. We store only the subscription reference, tier, and status — never full card numbers.
Where data is stored
- Primary database: managed PostgreSQL on Supabase (AWS us-east-1) with daily encrypted backups and 7-day point-in-time recovery.
- Authentication: Supabase Auth with PKCE flow; passwords hashed with bcrypt. Google OAuth and passwordless magic links supported.
- File storage: Supabase Storage for uploaded assets (logos, avatars). Each bucket enforces row-level access rules.
- Regional processing: primary region is us-east-1. Enterprise customers with data-residency requirements can request an addendum via privacy@eqiqs.com.
How data is protected
Encryption
TLS 1.3 in transit and AES-256 at rest via managed platform defaults.
Row-Level Security
Every table enforces RLS at the database layer, so users and workspaces can only reach their own rows even if application logic is bypassed.
API key handling
Constant-time comparisons prevent timing attacks. Keys are hashed at rest and revocable from Settings.
Admin audit log
Sensitive admin actions (tier grants, impersonation, deletions) write immutable rows to an audit table available on Enterprise plans.
AI processing
- Providers: Google Gemini and OpenAI models via the Lovable AI Gateway. Prompts are sent server-side from edge functions.
- No training: customer data is contractually excluded from provider model training.
- Cached outputs: some AI responses are cached to reduce cost and latency. Cache entries scope to the user or workspace that generated them and are purged when the underlying inputs change.
- HR-safety mode: when enabled, raw psychometric codes (e.g. "INTJ", "3w4") are stripped from generated reports in favor of behavioral language suitable for hiring contexts.
Your rights
- Export: one-click JSON/CSV export from Settings → Data & Privacy.
- Correction: edit any profile field directly, or request assistance via privacy@eqiqs.com.
- Deletion: account closure triggers a 30-day grace window, then automated purge of personally identifiable data and psychometric responses.
- Consent controls: analytics and ad vendors are disabled by default and only activate after explicit cookie consent.
- GDPR / CCPA / CPRA: data-subject requests are acknowledged within 5 business days and completed within statutory timelines.
Retention & deletion
| Data type | Default retention | On deletion |
|---|---|---|
| Profile & assessment data | Life of account | Purged within 30 days |
| Shared report tokens | 60 days | Auto-expire |
| Comparison invites | 90 days | Auto-purge |
| Backups | 7 days rolling | Overwritten on cycle |
| Billing records | 7 years (tax law) | Retained per Stripe |
This page is app-owned editable content, not a formal certification. See the Trust Center, Subprocessors, and Privacy Policy for full detail.