MODI Privacy Policy · MODI-PRIVACY-v1

Your information and MODI

This page explains, in plain language, what the MODI student service processes, why, where it goes, and how you can manage it. MODI does process account and learning information; it does not promise to collect no personal information.

Last reviewed: 5 October 2026. This notice describes the current source configuration and needs operator/legal review before launch.

Information MODI processes

• Account: Firebase UID, email, sign-in provider, email verification and account security information. If you choose to enter it, your name, class/year, country, subjects, curriculum and learning preferences are also saved.
• Learning: saved normal conversations, exams and answers, progress records, uploaded document metadata/content, support messages and replies.
• Service and security records: limited activity events (such as an AI request result), rate-limit/security signals, technical error codes and hosting/authentication logs. When a chat is flagged by safety checks, MODI may save a short excerpt of the message and answer with a risk reason for Admin security review.
• Technical data: Firebase, Vercel and other providers may process connection, device/browser and security data such as IP address and request metadata as part of operating their services. Exact provider retention and region depend on the account configuration.

Why it is used

MODI uses this information to sign you in, provide learning tools, keep normal chats/exams/documents when requested, respond to support, secure the service, prevent abuse, and maintain the system. Learning preferences can be used to tailor answers. Saved chat excerpts are no longer included as extra context in new Groq prompts; the current prompt, selected learning level/subjects/preferences, and any document you ask about may be sent for that answer.

Normal Chat and Temporary Chat

Normal Chat is saved under your signed-in Firebase account and appears in your normal history. You can delete saved conversations in Settings.

Temporary Chat is stored separately under your account and does not go into normal saved conversation history, normal history/search, or Admin conversation history. It is designed to expire after 24 hours without activity or 48 hours total. Expiration prevents use; a scheduled daily cleanup removes expired session records and uploaded temporary files. A cleanup run may therefore happen later than the exact expiry time. Temporary Chat messages are used to generate replies and may be sent to Groq or the configured search provider when needed.

Documents

MODI checks supported file types and size on the server, extracts text or image content, and stores account documents in a private Vercel Blob store with ownership metadata in Firestore. The browser does not receive Blob credentials or public Blob URLs. The contents are sent to Groq only when used for AI analysis/chat. Temporary uploads use a separate per-user/per-session path and are removed with the expired/deleted Temporary Chat. Some document-study mode uses browser device storage; those files stay on that device until you remove them or clear its browser data. Account deletion removes the account's private Blob prefix.

Services that may receive information

• Google Firebase Authentication and Firestore: account authentication, profile, saved learning data, temporary sessions and support. The project operator controls the end-user data and must review Firebase data-processing terms and location configuration.
• Vercel and Vercel Blob: hosting, application requests and private document storage. Blob read/write access is performed by the server.
• Groq: the current chat prompt, limited learning context, and document text/image that you ask the AI to use are sent server-to-server for generation. The Groq key stays on the server. MODI does not send saved conversation history as supplemental context. Account-level retention/zero-retention settings cannot be confirmed from this source tree.
• Web search provider: only when a current-information search is triggered, the latest question/search query is sent to the configured provider (Brave, SerpAPI or Tavily). Search credentials stay server-side. The whole conversation is not sent as search history.
• Stripe: billing code is present but the source only accepts Stripe test-mode credentials; confirm whether billing is disabled or used in the deployed environment. Payment processing can involve payment/contact and transaction metadata.
• Email: Firebase Authentication sends account verification and password-reset messages. No separate email-delivery integration is configured in the student application source.

No separate analytics/advertising tracker was found in the reviewed project dependencies and frontend allowlist. Hosting/Firebase operational logs still exist.

How long data stays

Normal chats, exams, account profile data and saved documents stay until you delete them, delete your account, or the operator otherwise removes them. Temporary data expires as described above and is cleaned up by the daily scheduled task. Support tickets and some account activity/security records are removed during account deletion. A minimal administrative deletion audit record is retained to show that deletion was requested/completed; a retention period for these audit records has not yet been configured or confirmed. Provider-side logs/retention are subject to each provider's settings and terms and have not all been verified.

Your controls

• Delete saved chats in Settings; delete documents from Documents; remove device-only documents in the app/device.
• End or delete a Temporary Chat at any time. Temporary data is also expired and cleaned automatically.
• Use the account deletion control or contact the MODI support team from the signed-in app. Account deletion revokes Firebase refresh tokens, removes the user profile/subcollections and account-owned Blob objects, and deletes the Firebase Auth account when the workflow completes. If an operation fails, the account is locked until deletion is retried or support is contacted.
• You may contact support through the signed-in application for questions or help with your information.

Security and AI

Server APIs verify Firebase ID tokens and derive the student UID from the verified token. Firestore rules and server services restrict account data to its owner; Admin routes require verified Admin authorization. Private document operations check ownership. These controls reduce risk but cannot guarantee that any internet service is perfectly secure.

MODI is AI and can be wrong. Check important information with a teacher or trusted source. Generated lessons/exams are not automatically official school, exam-board or SQA materials. Do not enter very sensitive personal information unless it is needed for your study question.

Your privacy rights

Depending on the law that applies to you, you may have rights to ask for access to your personal information, correction, deletion, restriction of processing, objection, or a copy in a portable format. You may also have a right to complain to your local data-protection authority. The exact rights and exceptions depend on your location and situation. Agreement acceptance does not remove statutory rights.

To ask about your information or raise a privacy concern, use the signed-in Support Center. The operator has not supplied a separate verified privacy email or postal address, so none is invented here. The controller should publish a direct privacy contact and response process before public launch.

Account deletion

You can request deletion in Account settings. The service locks the account while it removes eligible Firebase account data, saved chats, exams, support records, temporary sessions and private document files, then invalidates the Firebase sign-in account. If deletion is interrupted, the account remains locked until the deletion can be retried or Support helps. A limited security/deletion audit record may be retained where needed; the retention period must be confirmed by the operator. Copies in provider backups or operational logs may not disappear immediately.

Parents and guardians

MODI is an educational AI assistant for students, including children. It may process account identifiers, questions, saved learning records, support messages and documents as described on this page. A parent or guardian can read the full Privacy Policy, ask the student to use the signed-in Support Center, or contact the MODI team there to raise a privacy concern. Applicable child privacy rights depend on the child’s age, capacity, location and the relevant law. MODI does not claim that parental consent is always required or that a parent can exercise every right on a child’s behalf.

Children and launch readiness

MODI is for students and may be used by children. The service has no age-verification gate. The applicable age, parent/guardian information, lawful basis, privacy contact, international transfer terms, provider account eligibility, and any required child-specific controls depend on where the service is offered and must be decided with a qualified privacy professional before launch. The internal Children’s Code DPIA is maintained separately and is not shown in the student app.

Who operates MODI and how to contact us

MODI is presented as a Modupath service. The legal data-controller/operator name, business address, privacy contact, and response process for formal privacy requests have not been supplied in the project configuration. Until those are confirmed, use in-app Support for operational help; the operator must publish verified contact details before public launch.

Changes

A material change to this notice or the Student Agreement will be published as a new version. The app records agreement acceptance by version. Privacy notice acknowledgement is not represented as GDPR consent, and the source currently has no separate optional tracking consent.

Provider details reviewed: Firebase Privacy and Security; Vercel private Blob documentation; Groq Services Agreement; Groq DPA.