Privacy Policy

1. Who this policy covers

EDUTICA™ is a product brand operated by EduLogicsAI, Inc., a California corporation ("EduLogicsAI," "we," or "us"). This policy applies to the public site edutica.ai and Edutica MCAT® Prep at mcat.edutica.ai. The current external pilot is for people at least 18 years old, as described in the Terms and Pilot Disclosure.

2. Information we collect

Account and identity information: when you register or sign in, we process your email address, account identifier, and information needed to authenticate your account. If you choose Google Sign-In, Google and our authentication provider may return your Google account identifier and profile information such as your email address and name; a profile image may also be available. We use this information to sign you in, create or associate your Edutica account, and maintain your authenticated session.

Profile and learning information: depending on the features you use, this may include your MCAT test date, score goal and current score; study-plan choices; questions and passages presented; answer selections and results; flags and timing; study and AI-assisted conversations; session summaries; practice, exam, and review history; learning events; concept-level progress; feedback you submit; and records of legal acknowledgements. If you use checkout, billing and subscription information may also be processed.

Technical and support information: we and our service providers may process device/browser and request information, timestamps, error and security diagnostics, and information you include in support messages, to operate, protect, and troubleshoot the service.

3. Google Sign-In and Google user data

Google Sign-In is offered to authenticate you. The web application invokes Google sign-in through Supabase Auth and does not specify additional Google API scopes in its sign-in request or call Google APIs such as Gmail, Drive, Calendar, or contacts. The exact scopes and provider-side storage settings configured in Supabase and Google Cloud are not represented in this codebase and should be checked in those consoles. We do not sell Google user data or use it for advertising.

Supabase processes the authentication identity and session. The application database stores the account identifier and, when provided in authentication metadata, a profile name and avatar URL. The backend loads a display name for application use, but current MCAT agent prompt construction does not add the stored display name, email address, avatar URL, Google provider identifier, or authentication tokens to model requests. Application API bearer tokens are used for backend authentication and are not forwarded by the prompt-building code to model providers. Information you choose to type into a message may of course contain personal information or secrets; do not submit passwords, tokens, or other credentials.

4. How we use learning and other information

We use information to provide and secure account access; deliver study, practice, assessment, planning, progress, and review features; preserve session continuity and results; personalize guidance using your goals and learning activity; respond to requests and feedback; diagnose errors and abuse; and operate and improve the Edutica pilot. When you use AI-assisted features, model requests can include free-text messages you submit, recent conversation turns, retrieved educational passages or content, relevant episodic learning summaries, and task-specific educational data. For answer evaluation this can include the question, answer choices, your submitted answer, the correct answer, and explanations. Plan-generation requests can include your test date, score goal/current score, and derived mastery or review priorities. Current prompt builders do not automatically add your stored name, email, avatar, or authentication tokens. Content you include in a free-text message may be sent as part of that message.

5. When information is shared

Information is shared with service providers as needed to provide the service: Supabase for authentication and database services; Vercel for web hosting and delivery; Railway for backend application hosting; Anthropic models through our LiteLLM gateway for current MCAT agent chat, tutoring, question generation, evaluation, and plan-generation calls; and OpenAI model services through LiteLLM for configured content-manufacturing and embedding workflows. The repository configuration identifies these provider routes, but active production routing and account-level settings must be confirmed against deployed configuration. Google processes sign-in information as the identity provider. When checkout is used, Stripe processes payment and billing information; Edutica also stores related customer and subscription records. We may also disclose information when required by law or when reasonably necessary to protect the service, users, or rights.

6. Storage, retention, and deletion

Account and learning records are stored in the services used to operate Edutica. We have not established a single fixed deletion period that applies to every category of information; records may remain while an account and its learning features are in use and as needed for service operation, security, legal obligations, and dispute handling. Provider logs and backups may have separate retention schedules. This policy does not promise a specific deletion completion time.

There is no self-service account-deletion control in the current application. To request access, correction, or deletion, email legal@edulogicsai.com. We may need to verify your identity and will explain any information we cannot delete and why. Deletion may be subject to operational, security, and legal requirements.

7. Security and privacy choices

Edutica uses authenticated access controls and database protections, including controls intended to restrict student records to the appropriate account and tenant. No online service can guarantee absolute security. You can choose an available sign-in method and may stop using the service. You may contact us with privacy questions or requests. Rights available to you depend on applicable law.

8. Logs, analytics, and AI-provider details

The application source reviewed for this policy does not show a dedicated third-party product-analytics SDK or an integrated Langfuse tracing client. The fresh-session classification and high-risk escalation log events record diagnostic metadata such as a session correlation identifier, agent identifier, and risk/event type; those two paths do not log the raw student message or complete agent response. Other operational logs may include application identifiers or error diagnostics. Raw chat history is held in an in-process cache for session continuity and is not written as a durable transcript table by the reviewed chat path; selected session summaries, question/session state, answers, and learning events are persisted by Edutica. Hosting, authentication, backend, and AI providers may independently create operational or security records. We have not verified the provider-specific retention or model-improvement settings applicable to deployed accounts; do not infer them from this policy.

9. Policy updates and contact

We may revise this policy when the service or its data practices change. We will post the current version here and update the date above. For privacy requests or questions, contact legal@edulogicsai.com.

10. MCAT® trademark

MCAT® is a registered trademark of the Association of American Medical Colleges (AAMC). Edutica is not affiliated with, endorsed by, or sponsored by the AAMC.