TeachPilot TeachPilot
Features Blog Security About
  • Features
  • Blog
  • Security
  • About

Cookie Policy

Effective 1 May 2026 · Veridian AI India Private Limited

Terms Privacy Cookies Security

On this page

  1. What are cookies
  2. How we use them
  3. Cookie & storage list
  4. Analytics & replay
  5. Third parties
  6. Your choices
  7. Updates
  8. Contact

This Cookie Policy explains how Veridian AI India Private Limited uses cookies and similar technologies on TeachPilot websites and applications. It should be read with our Privacy Policy.

1. What are cookies and similar technologies?

Cookies are small text files stored on your device by a website or app. Related technologies include local storage, session storage, pixels, and software development kits that store or read identifiers on your device. We use the word “cookies” in this Policy to cover these technologies for simplicity.

2. How we use cookies

Category Why we use them Can you reject?
Strictly necessary Sign-in sessions, multi-factor challenges, OAuth security state, load balancing/session affinity where used, and core security No — required for the Service to function securely
Functional / preferences Theme (light/dark/system), accessibility and UI preferences, last login method hint, and similar convenience settings Yes — via browser controls or clearing site data (may reset preferences)
Analytics & product improvement Understanding feature usage, performance (web vitals), error diagnostics, and (in the LMS app) privacy-conscious session replay Yes — browser controls, extensions, or contacting us; some enterprise controls may be available under commercial agreements

The marketing site (https://teachpilot.in) primarily uses preference storage for theme and does not initialize the same product analytics stack as the LMS application.

3. Cookies and storage we set

3.1 Authentication cookies (LMS / API)

When you sign in to the application, our API sets first-party HttpOnly cookies used only for security and session continuity:

Name Purpose Typical lifetime Flags
teachpilot_session Authenticated session token Up to 30 days (organization policy may shorten session lifetime) HttpOnly, SameSite=Lax, Secure in production
teachpilot_2fa Temporary two-factor authentication challenge About 5 minutes HttpOnly, SameSite=Lax, Secure in production
teachpilot_oauth OAuth state / CSRF protection during social sign-in About 10 minutes HttpOnly, SameSite=Lax, Secure in production

These cookies are host-scoped (not broadly shared via a parent domain). Session identifiers are stored server-side with cryptographic digests; the browser holds the session secret in the HttpOnly cookie so client scripts cannot read it.

3.2 Browser storage (non-cookie)

Storage Examples Purpose
localStorage theme / appearance settings; last login method hint; accessibility preferences Remember UI choices on this device
sessionStorage Invite return path and similar short-lived UX state Complete multi-step flows in one browser session
localStorage / site data Live activity participant continuity keys; video resume positions Classroom and learning continuity

3.3 Bot protection

When bot protection is enabled on sign-in or similar steps, our security provider may set cookies or use browser signals to help verify that a request is made by a human. Those technologies are also governed by the provider’s own notices.

4. Analytics and session insights (learning app)

In the learning application, we use product analytics to understand usage and reliability. In practice this may include:

  • Events such as page views, interactions, performance metrics, and exceptions
  • After sign-in, association of events with user id, email, name, role, and organization context so we can support institutions and improve the product
  • Optional session insights with input masking by default; additional elements can be masked in product UI
  • Profiles for identified users (not anonymous browsing profiles as a default product setting)

Server-side components may also emit product events (for example login-related analytics) for the same purposes.

5. Third-party cookies and embeds

If you play embedded third-party media, open external identity providers, or load status badges and similar embeds, those third parties may set their own cookies under their policies. Examples include:

  • Google or Microsoft during social / institutional sign-in
  • Infrastructure and security providers that protect the Service
  • Status page badge embeds on the marketing site
  • Optional content providers when teachers search or embed media

6. Your choices

  • Browser controls — block or delete cookies and site data; use private browsing. Blocking strictly necessary cookies will prevent sign-in.
  • Sign out — ends the server session and clears session cookies when you log out (including options to sign out other sessions where available in-product).
  • Theme and preferences — clear site data to reset local preferences.
  • Analytics concerns — contact privacy@teachpilot.in. Institutions evaluating deployment can discuss analytics configuration during onboarding with sales@teachpilot.in.

We currently do not implement a separate cookie-consent banner that disables strictly necessary authentication cookies, because those cookies are required to provide a secure logged-in Service. Preference and analytics technologies are described here so you can make informed browser-level choices.

7. Updates

We may update this Cookie Policy when our technologies change. The effective date at the top of the page will be revised accordingly.

8. Contact

Veridian AI India Private Limited
Vijayawada, Andhra Pradesh, India
Privacy: privacy@teachpilot.in

Effective 1 May 2026.

Last updated 1 May 2026.

TeachPilot TeachPilot

Product

Lesson Planning Student Tracking Analytics Resource Library Request a demo

Resources

Documentation Blog Changelog Support

Legal

Terms Privacy Cookies Security

Company

About Contact

Connect

X LinkedIn GitHub
© 2026 Veridian AI India Private Limited