Privacy Policy
Last updated: October 2026
1. Introduction
At Kokoro, we respect your privacy and are committed to protecting the personal data and study materials you entrust with us. This Privacy Policy explains what information we collect, how it is used, and your rights regarding your data.
2. Information We Collect
Account Information: When you sign up, we collect your email address, name (if provided), and password hash. If you sign in via Google OAuth, we receive your email and basic profile information from Google.
Study Materials: We collect and store documents (PDFs, Markdown, text files) you upload so you can access your decks and notes across devices.
Study Activity: We record flashcard review logs (ratings and review dates) solely to calculate spaced repetition schedules (SM-2 intervals) and study streaks.
3. How Your Information is Used
- To extract text from your notes and generate tailored flashcards.
- To calculate repetition intervals and due dates for daily study queues.
- To perform semantic searches across your notes when you ask questions in chat.
- To authenticate your session and manage subscription status.
4. Third-Party Service Providers
We work with reputable third-party infrastructure providers to operate Kokoro:
- Supabase: For authentication, encrypted database storage, and file storage with strict Row Level Security (RLS).
- Anthropic: To process note texts and generate flashcards and chat responses via Claude Haiku 5.5. Your data is not used to train public foundational models.
- Polar: For payment processing and subscription billing. Polar handles credit card information securely without Kokoro seeing or storing your raw payment credentials.
5. Data Retention & Deletion
You have complete control over your data. You can delete individual documents anytime from your Library, which immediately purges the associated chunks and cards. You can also permanently delete your entire account and all associated data directly from the Settings page.
6. Security
We apply industry-standard security measures, including HTTPS encryption in transit, strict Row Level Security (RLS) policies in Postgres ensuring only you can read or modify your files, and secure tokenized authentication.
7. Contact
For any questions or privacy requests, reach out to us at privacy@kokoro.study.