Account data: your email address and authentication credentials.
Application data: if you applied for beta access — your name, work email, company, job title, industry, team size, use case, and optional LinkedIn URL.
Research content you create: persona definitions and their psychological profiles, conversations and focus-group transcripts (including each persona’s simulated “inner world”), simulated memories and emotional states, uploaded files, experience ingestions, and variant comparisons. Persona psychology is simulation data about fictional characters you design — do not model real, identifiable individuals in your personas.
Usage data: per-request model usage (tokens, latency, model) for cost and abuse monitoring, plus standard server logs.
To generate persona responses, your conversation content and the relevant persona profile are sent to our AI subprocessors: Anthropic (Claude models, for persona reasoning and responses) and OpenAI (text embeddings, for persona memory retrieval). Both process the data to provide the service; we do not permit our API traffic to be used to train their models. Infrastructure providers: Supabase (database, file storage, authentication), Vercel (hosting), Upstash (rate limiting), and Cloudflare (bot protection on the application form).
Your research content is retained while your account exists so your personas keep their memory and history.
Rejected access applications are automatically and permanently deleted 30 days after review. Approved applicants’ application records are deleted when the account they created is deleted.
On account deletion we erase your storage files, your application record, and your entire database footprint (personas, conversations, memories, focus groups, uploads, comparisons). Aggregate model-usage records (token counts and costs) are retained for billing integrity but are anonymized — the link to your deleted account is severed.
From the Settings page you can, at any time and without asking us:
If you are in a jurisdiction with statutory data rights (e.g. GDPR), these tools implement your access, portability, and erasure rights; for anything they don’t cover, contact us and we will respond within the statutory window.
Data is encrypted in transit and at rest by our infrastructure providers. Access to production data is limited to the operating team. Files are stored in a private bucket scoped to your account. No system is perfectly secure; we will notify affected users of any breach as required by law.
Perplica uses only the cookies required to keep you signed in (authentication session). There are no advertising or cross-site tracking cookies.
We will announce material changes to this policy in the product before they take effect. Questions or requests: contact the Perplica team through your beta onboarding channel or the contact address on the application form.
Terms of Service · Privacy Policy · Sign in
A Pixelik Labs product