Privacy, with clear boundaries.
This draft describes the current implementation. It is not a claim of legal compliance or a finalized public-launch policy.
What we process
Supabase processes account email, authentication credentials and sessions. Veriqo stores your assignment title, subject, education level, instructions, rubric, draft, explanation language, reviews and source snapshots. Usage records hold request status, consent timestamp, model and reported token usage/cost estimates.
Document uploads and AI processing
Uploaded files are extracted on the server; original file bytes are not stored by the current upload flow. Saved content is sent to NVIDIA NIM only after explicit per-review consent. NVIDIA receives the instructions, draft, optional rubric and assignment metadata necessary for the review. The interface does not send AI requests on each keystroke.
Access and Campus privacy
Assignment and review access is limited to the owning student through server authorization and database RLS. Backend operators with privileged access must use it only for authorized operation. Campus membership does not grant administrators access to private student documents. Campus administrators manage membership, seats and institutional billing; analytics suppress small cohorts and exclude document content. Live Campus rollout requires the tested migrations and acceptance checks.
Retention and deletion
Assignments remain until you delete them. Individual deletion removes reviews and scrubs associated document snapshots; content-free usage metadata is retained separately for quota accounting. Data export and bulk document deletion are available after the privacy migration; bulk deletion requires your current password. A privileged retention function is prepared but not scheduled. Account deletion and backup erasure require an operator process. Contact the operator for account/data requests through a private channel.
Support requests
The contact form uses your confirmed account email as the reply address and accepts a subject and plain-text message. Delivery is currently disabled. If enabled after approval, those details are forwarded to the configured email provider and Veriqo's support inbox; do not include assignment content or passwords. Support retention and provider terms require owner/legal review.
Cookies and analytics
HttpOnly session cookies support authentication. Preference cookies store the interface language and theme. Recovery cookies are short-lived and signed. No advertising pixels or third-party analytics trackers are added. Operational usage records support quotas, errors and cost control; they are not a student surveillance dashboard.
Before public launch
The owner must finalize the controller identity and private contact route, purposes/legal bases, provider processing terms and regions, retention schedule, rights handling and any required notices. Supabase and NVIDIA processing arrangements must be reviewed. This policy is a draft for that work.