Legal
Last updated July 21, 2026
LatentQ stores account identifiers, verified email status, practice progress, drafts, submissions, study history, and membership entitlements needed to provide and secure the service. Submitted code and interview answers are not sent to product analytics.
Payments are processed by the configured payment provider. LatentQ stores provider customer, checkout, transaction, and subscription references plus entitlement status; it does not store full card details.
Necessary transactional messages cover verification, password recovery, payment, receipts, waitlist confirmation, and account access. Optional founder updates and beta invitations use a separate preference that can be changed in account settings. Disabling optional product communication does not disable necessary transactional email.
When the private interview simulation uses adaptive interviewer turns or rubric evaluation, the CV, job description, typed or browser-transcribed answers, recent transcript, and submitted evidence needed for that request are relayed through the LatentQ backend to the configured AI provider. LatentQ requests provider-side storage to be disabled and does not persist these request bodies, model responses, or transcripts in its database or application logs. The provider may still process request data under its own service terms and data-handling policy.
Browser speech recognition and speech synthesis remain device or browser features; LatentQ does not send microphone audio to its backend. Session recovery data stays in browser session storage and deliberately excludes the CV and job description.
Optional browser analytics starts only after you choose Allow analytics. It may include sanitized page paths, a pseudonymous first-party visitor identifier, browser-session timing, broad device category, referrer domain, campaign tags, and product actions. When a consenting session later signs in, its first-touch website and campaign metadata may be associated with that account. The consent prompt disappears completely after your choice. You may change the saved choice here on the Privacy page. Declining clears the browser analytics identifier and stops future optional browser collection.
Necessary server records continue to record account creation, verification, successful login, practice progress, submissions, promotional entitlement results, and membership state so the service can operate, remain secure, and provide account history. Promotional-code plaintext is never stored in analytics. Automatic token refreshes do not count as product activity.
Analytics events never include email addresses, passwords, tokens, promotional-code plaintext or hashes, raw IP addresses, full user-agent strings, source code, draft or notebook contents, custom cases, typed or spoken interview answers, raw runner output, card data, or payment instruments. Account identifiers already needed by the service may link authenticated activity to your account.
Detailed product events, pseudonymous sessions, first-touch attribution, promotional redemption attempts, and user-day activity are retained for 13 months. Minimal D1, D3, D7, and D30 return indicators remain with the account so its history stays accurate after detailed rows expire. Successful promotional grants remain necessary membership records. Non-identifying daily and retention totals may be retained longer. Read access and safe metadata exports are restricted to the single configured, verified analytics administrator and are audit logged; administrator audit records are retained for 24 months. Billing records follow separate account and payment retention requirements.
Configured infrastructure, email, payment, and analytics providers process only the information needed for their role. Access controls, verified webhooks, database constraints, and abuse protections are used to protect accounts and entitlements.
Privacy questions may be sent to contact@latentq.com.