Privacy Policy
Draft pending legal review · Last updated: [OWNER: date]
1. Who is responsible
CA-Wiki is operated by [OWNER: legal name / entity], [OWNER: registered address]. This policy explains what we collect, why, who processes it, and the controls you have. It is written to comply with the Information Technology (SPDI) Rules, 2011 today and is designed for the Digital Personal Data Protection Act, 2023, whose obligations apply to us in full from 14 May 2027.
2. What we collect, and why
- Email address (via Google sign-in or email code) — your account identifier and, if you opt in, the digest channel.
- Exam preferences — exams you prepare for, target year, language — to render notes and quizzes for your exams.
- Date of birth — declared once at sign-up, used solely for the legal age check (under-18 accounts need verified parental consent for engagement features). It is not shown publicly and not editable afterwards.
- Reading activity — which topics and content segments you read and when. This powers "what changed since you last read", streaks, and our anti-redistribution access log (which also records IP address and browser user-agent per content fetch).
- Quiz activity — attempts, answers, and scores, to show your progress and power revision tools.
- Consent records — an append-only log of every consent you grant or withdraw, with timestamp and policy version.
We do not collect your phone number, payment details (payments are not live), precise location, or contacts.
3. Consent — purpose-specific, never bundled
Each optional purpose (email digest, browser push, Telegram updates, product analytics) is a separate, unticked choice. Nothing is pre-ticked and nothing optional is bundled into account creation. You can withdraw any consent at any time from Settings — withdrawing is as easy as granting, and every change is recorded.
4. Who processes data on our behalf
We itemize every processor with its country and purpose. Our AI-assisted editorial workflow processes public news content only — user personal data never enters it.
| Processor | Country | Purpose | Status |
|---|---|---|---|
| Clerk | United States | Authentication and session management (Google sign-in, email one-time codes) | Active |
| Google Gemini API (paid tier) | United States | Server-side embeddings of our own published study content for search and deduplication — no user personal data is ever sent | Active |
| Cloudflare | United States / global network | CDN, caching, and security in front of the Service | Planned |
| Resend or Amazon SES | United States | Transactional email and the opt-in daily digest | Planned |
5. Retention, export, and deletion
- Export: download everything we hold about you as a JSON file, self-service, from Settings.
- Deletion: request account deletion from Settings (this page is the public web deletion path). A scheduled purge job permanently erases your data after a grace window; until the purge runs you can sign in and cancel the request. Records we must keep for legal or security reasons (e.g., tamper-evident access logs relevant to an active enforcement matter) may be retained for the legally required period.
- Correction: exam preferences and language are editable in Settings; for anything else contact the Grievance Officer.
6. Children and minors
Accounts of users under 18 (per the declared date of birth) have streaks, behavioral analytics, and leaderboards disabled until a parent or guardian verifies consent. We do not use minors' data for tracking or behavioral advertising. We serve no advertising at all.
7. Security
Data is encrypted in transit; content delivery is authenticated, rate limited, and recorded in hash-chained (tamper-evident) access logs; admin access is token-scoped and audited. In the event of a personal-data breach we will notify affected users and the relevant authority in line with applicable law and our breach runbook.
8. Grievances
Concerns or complaints go to our Grievance Officer — see the Grievance page for contact details and response timelines.
9. Changes to this policy
Material changes will be announced in-app or by email, and the policy version stamped on your consent records will change. Continued use after notice constitutes acceptance under current law; where DPDP requires fresh consent, we will ask for it.