Privacy and data use
Clear context for behavioral and AI data
Lumivox processes study activity to provide its core workspace, analytics, and AI-assisted features. This page describes the current project implementation; it is not a claim that no third party ever processes data.
Implementation reviewed: 30 September 2026
Account data
Authentication and profile records identify your account, preferred language, onboarding state, and product settings. Supabase provides authentication and database infrastructure. These records are used to secure access and personalize the workspace.
Tasks, goals, and focus behavior
Task titles, descriptions, priorities, dates, completion state, goals, focus-session duration, and recorded distractions support planning and behavioral analytics. They may also form input features for task-risk assessment and weekly reflection.
Study-room interactions
Room membership, presence, text messages, voice-room connection metadata, reactions, and challenge progress are processed to provide collaborative study features. Other room participants can see information that the interface presents as shared.
Uploaded documents
Files that you upload are stored for document features. Extracted text can be divided into chunks and represented as embeddings so selected documents can be searched during grounded AI conversations. Only upload material you are permitted to use.
AI request context
When you request an AI insight, roadmap, translation, reflection, or document-grounded answer, relevant prompt text and selected context may be sent through the Lumivox AI service to configured external model providers. The current service supports Google Gemini and Groq-backed generation paths; document embeddings use Google Gemini.
Storage and access controls
Application records are stored in Supabase. Public-schema tables use row-level security so application requests are scoped by the relevant ownership and access policies. Secret backend credentials are not shipped to the browser; the web client uses a publishable key.
Website analytics
Lumivox uses Google Analytics to understand how the public website is discovered and used. Analytics may process information such as page views, session activity, browser and device characteristics, and approximate geographic information. Lumivox uses this information to evaluate website and SEO performance. Application passwords, task content, uploaded documents, and email addresses are not intentionally included in analytics event parameters.
Managing your information
You can edit or remove many workspace records through their product controls. Account-level export and deletion are not currently presented as a self-service control in this codebase. For requests that cannot be completed in the interface, contact the project through the public repository and avoid posting private data in a public issue.
Research reporting
Public research pages use aggregate metrics. Participant names and verbatim usability comments are not published without explicit consent. Model evaluation statistics describe classifier performance and do not represent improvements in student outcomes.
Chrome Extension and focus awareness
Lumivox Focus Companion uses a separate authenticated session to display and control focus timers. Optional tab observation is disabled by default and requires explicit Chrome permission. When enabled, the extension processes the active tab's domain locally to identify possible distractions during an active focus round. Full browsing URLs, page titles, and browsing history are not transmitted to Lumivox. Temporary observations and suggestions are held in extension session storage. Only when the user explicitly confirms a suggestion are its category, duration, and associated focus-session identifiers sent to Lumivox for storage and analytics. Authentication session credentials are stored in extension-local storage with access restricted to trusted extension contexts. Users may disable observation, revoke the optional tabs permission, dismiss suggestions, and sign out of the extension. Data is processed using the infrastructure identified elsewhere in this policy.