Privacy Policy
Last updated: October 2026
1. Data We Collect
- Account Information: Email address, country of residence, mobile number when verification is enabled, display name, companion avatar, and password credentials managed by Supabase Auth.
- Roadmap Inputs: Target skill fields, self-reported experience level, weekly availability, budget limit, and quiz scores.
- Progress Tracking: Marked stage completions, ratings, practice checks, and export timestamps.
2. AI & Third-Party Integrations
Verification messages are delivered through Supabase Auth and its configured email and SMS providers. Phone numbers are used for verification, not marketing. Your onboarding parameters are transmitted to Google Gemini API (with search grounding) to synthesize your learning stages and filter public YouTube and web resources.
3. Data Control & Permanent Deletion
You retain full control over your data. You can delete individual learning paths from your Dashboard or delete your entire account permanently via your Account Settings.
4. Cookies & Security
We use strictly necessary cookies for authentication. Session tokens are held in HTTP-only cookies, and private account responses are not cached. Database ownership rules isolate profiles, saved roadmaps, progress and notes from other users, including application administrators. Our trusted backend and infrastructure providers process account data to operate the service. Optional bots receive access only to the course catalog, never your profile or private learning records.
5. Sign-in Security
Optional authenticator MFA is managed by Supabase Auth. Verified accounts must complete their second step before accessing private LearningMap data. Setup keys are shown only during enrollment; keep them private and maintain a backup authenticator. Password resets do not disable MFA.
For passwords submitted through our signup and reset forms, our server checks Have I Been Pwned’s Pwned Passwords service using only the first five characters of a SHA-1 hash, with padded responses. We do not send your password, full hash or email, or log these checks. SHA-1 is used only for this lookup; Supabase Auth remains responsible for password storage. LearningMap performs password operations on the server; its project credentials are not provided to the browser.
6. Google Calendar
Connecting Google Calendar is optional and separate from signing in. With your permission, LearningMap creates timed study sessions in your primary Google calendar when you select Add sessions. We send Google the learning field, stage title and description, session times, time zone, and identifiers used to prevent duplicate imports. When retrying an import, we read the matching event to confirm it belongs to that roadmap. We do not scan your calendar for unrelated events.
The requested permission allows access to events on calendars you own. Our implementation uses it only for the study schedule you request. Your Google access token is kept in an encrypted, HTTP-only connection cookie for at most one hour. We do not store a refresh token or provide ongoing calendar sync.
Google Calendar data is not sent to Gemini, used to train AI models, sold, or used for advertising. LearningMap’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
You can revoke access through your Google Account connections and delete imported study events in Google Calendar. Revoking access, clearing connection cookies, or deleting a LearningMap roadmap does not delete events already imported into Google Calendar. For privacy questions, contact 60shivam50@gmail.com.