RevIT legal
Privacy Policy
This policy describes the account, study, preference, AI, and voluntary-support information processed by the current RevIT codebase.
01
Scope
This Privacy Policy describes the information RevIT stores or processes. RevIT is an educational study platform, not a clinical records system.
02
Account and Profile Information
When cloud accounts are enabled, RevIT uses Supabase Authentication to process your email address, password authentication, email-verification status, session information, and any configured multi-factor authentication. RevIT’s profile table stores your username, first name, optional avatar URL, onboarding status, and the versions and database timestamps for accepted Terms and Privacy Policy.
RevIT application code does not store your plain-text password.
03
Study and Progress Information
RevIT may store question-attempt history, selected answer index, correctness, question and topic identifiers, difficulty, review mode, adaptive-repeat status, timestamps, weakness and reinforcement state, daily activity totals, subjects studied, XP, level-related progress, achievements, grades, exam schedules, and related activity-event identifiers used to prevent duplicate rewards.
04
Plans, Calendar, and Preferences
The current Study Planner stores plan titles, dates, blocks, times, categories, subjects, topics, notes, completion state, and calendar-link state in local browser storage scoped to the signed-in user or local mode. Exam schedules and study activity used by the calendar may be stored in Supabase when cloud accounts are enabled.
RevIT also stores preferences such as timezone, theme, optional leaderboard participation, whether you enabled NU MTAP-specific features, and whether you completed that preference prompt. The MTAP choice is private and is not added to your public profile or leaderboard results. Selected topics, sidebar state, sound preference, and session-policy markers may be kept in browser storage.
05
RevIT AI and Saved Conversations
When you use RevIT AI, recent chat messages are sent through RevIT’s server route to Groq when a Groq API key is configured. Groq processes that text to generate an educational response. When no key is configured, the app returns a limited built-in demo response without sending the prompt to Groq.
For signed-in cloud users, RevIT stores AI conversation titles, user messages, assistant messages, and timestamps in Supabase so chat history can be reopened. RevIT also stores short-lived request reservation and successful-usage timestamps, your applicable access tier, and quota configuration to enforce per-minute and daily limits. Failed validation and failed provider requests are not recorded as completed usage. Do not submit patient-identifying information, confidential clinical records, or information you are not authorized to share.
06
How Information Is Used
RevIT uses this information to authenticate accounts, verify email, maintain sessions, synchronize profiles and study records, personalize access to optional NU MTAP-specific tools, deliver reviewer and planning features, calculate deterministic grades and learning analytics, operate adaptive repetition, track activity and achievements, save AI conversations, display optional leaderboards, protect the service, and troubleshoot failures.
07
Supabase Storage and Processing
RevIT uses Supabase for authentication, database storage, and optional avatar storage. Private application tables use row-level security so authenticated users can read or change their own records under the current policies. The public avatar bucket permits public reads of uploaded avatar files, and leaderboard functions may expose the limited public profile fields described below.
08
Local Browser and Device Storage
RevIT uses localStorage and sessionStorage for theme, selected topics, local or cached question attempts, adaptive-repetition state, local-mode profile and study data, the local-mode MTAP preference, Study Planner records, sound and sidebar preferences, queued sync operations, level-notice state, and remember-me or session-only markers. Browser storage remains on the device and browser profile until cleared by you, the browser, or device-management settings.
09
Leaderboard Visibility
Leaderboard participation is optional and off by default. If enabled, leaderboard results may show your display name, avatar, rank, selected metric, and related eligibility or percentile information. RevIT’s leaderboard functions are designed not to expose email addresses, account UUIDs, or raw private attempt history.
10
Data Sharing and Service Providers
RevIT processes data through Supabase and, when live AI is configured and used, Groq. Information may also pass through the hosting and network providers that deliver the application. RevIT does not currently contain advertising or data-broker integrations in the inspected codebase.
11
Voluntary Support and External Payments
The Support RevIT interface may display a static QR code associated with an external payment provider. When you choose to use that QR, the contribution is completed outside RevIT through the third-party provider and is subject to that provider’s own terms, privacy practices, fees, and processing rules.
RevIT itself does not ask for or collect payment-card details, bank credentials, payment-app PINs, one-time passcodes, transaction identifiers, contribution amounts, or payment-account information through the Support RevIT interface. The current implementation has no payment webhook, contribution history, supporter account, or contributor tracking.
Scanning or using the QR may cause the external payment provider and your payment app or device to process information under their own policies. RevIT does not receive that provider-side payment information merely because it displays the QR.
12
Retention and Deletion
RevIT retains cloud records until they are changed or deleted through implemented features, removed by the operator, or deleted through account-cascade behavior. Deleting an authentication user is configured to cascade to related profile and user-owned database records. The interface includes deletion for selected items such as AI chats and exam entries, but it does not include a self-service delete-account workflow.
Clearing browser site data removes local-only information from that browser but does not delete cloud records. If you need to delete your account or data, please contact us.
13
Security and Its Limits
RevIT uses Supabase authentication, email verification, optional multi-factor authentication, row-level security, scoped database functions, and browser-session controls. No system can guarantee absolute security. Protect your credentials, use a trusted device, and report suspected unauthorized access through the production contact channel once configured.
14
Your Choices
You can switch theme, choose remember-me or session-only access, keep leaderboard participation off, enable or disable MTAP Features in Settings at any time, remove or change supported profile and study records, clear local browser storage, and sign out rather than accept a new policy version. Disabling MTAP Features hides only MTAP-specific tools and does not delete your grades or other study data.
15
Policy Updates
RevIT may update this policy as its features or processing practices change. RevIT stores the privacy-policy version you accepted. If the current version changes, signed-in users will be asked to review and accept it before continuing, or may sign out.
16
Contact
If you have questions about your privacy, access, correction, or deletion requests, please contact us.
17
Effective Date
Effective as of September 6, 2026. Material service or data-practice changes will be reflected in a new privacy version and presented to users for review.