Privacy Policy
Early beta privacy terms for Orvia.
Last updated: September 25, 2026
Overview
This Privacy Policy describes how Orvia handles data during the early beta. Orvia is still evolving, and some features save data on this device while others save supported records to your account.
Data You Provide
You may create tasks, notes, captures, and activity through the product. Signed-in cloud-backed records are associated with your account. Signed-out and fallback records may remain in this browser.
Browser Data And Product Analytics
Browser storage holds your sign-in session, preferences, onboarding state, command history, local Labs data and user-scoped recovery caches. First-party beta analytics sends allowlisted event names, random browser/session IDs and language to Orvia’s server and Supabase. The server records time and verified account ID/signed-in state when available. Successful task activation and feedback submission generate content-free events. A limited local buffer retains event context, never tokens or content. Analytics does not collect task/note/capture content, search text, feedback messages, email addresses, URLs or device fingerprints. No third-party analytics provider is used. Server analytics retention is not yet set; local reset does not delete server analytics. Local reset removes Orvia preferences, local records, caches and this buffer; it does not delete cloud data or sign you out.
Cloud Data
Orvia uses Supabase for sign-in and database storage. Your email and authentication information are processed for account access; confirmation and password-reset emails are requested through Supabase Auth. Supported tasks, notes, captures and activity are associated with your account. Hosting infrastructure also processes requests needed to serve the app.
Error monitoring
When enabled for a deployment, Sentry receives error diagnostics and may receive your internal account ID. Redaction is configured to remove credentials, email addresses and workspace content. Session replay, performance tracing and profiling are disabled. Monitoring is separate from first-party product analytics and submitted feedback.
Feedback and support
Submitted feedback is stored in Supabase with your account ID, message, category, time and review status, plus limited context such as route, language and theme. Authorized beta administrators can review it. Feedback is not a private vault: avoid secrets or unnecessary sensitive information. It is not copied into product analytics or error reports by the feedback flow.
AI And Integrations
AI Chat and Inbox suggestions currently use local mock or rule-based processing. Orvia does not currently send workspace content to an AI provider. Email, calendar and messenger integrations are not active. Supabase and optional Sentry monitoring are described separately above.
Backups And Reset
Create Backup exports legacy device-local tasks, notes and captures, Finance and Cars records, and theme. It excludes cloud records, signed-in recovery caches, feedback and activity. Restore, full account export and self-service account deletion are not available. Local reset does not delete your account or cloud records. Use the support path below to ask about your data; an automated deletion or retention process is not established yet.
Contact
For support, privacy or terms questions, sign in and open Feedback in the sidebar or Settings → Send Feedback. If you cannot sign in, use the channel where you received your beta invite. There is no public support email or guaranteed response time yet.