Privacy Policy
Katasaga
Effective date: 12 September 2026
Last updated: 11 November 2026
Katasaga is committed to handling personal data transparently and responsibly. This Privacy Policy describes how personal data is collected, used, disclosed, retained, and protected when you visit katasaga.com, join the Katasaga waitlist, create a Katasaga account, or use the Katasaga web or iOS application.
This Policy is intended to provide the transparency information required under Articles 12–14 of Regulation (EU) 2016/679 (the GDPR). It should be read together with the Katasaga Terms of Service.
1. Controller identity and contact
Katasaga
KVK number: 42159778
Website: https://katasaga.com
Privacy and legal contact: dev@katasaga.com
Katasaga is operated as a Dutch sole proprietorship registered with the Netherlands Chamber of Commerce. Registered business details are available through the Dutch Business Register.
For the purposes of the GDPR, Katasaga is the controller responsible for the processing described in this Policy. Katasaga does not currently appoint a Data Protection Officer. Privacy requests may be sent to the contact address above.
2. Scope and terminology
In this Policy:
- Katasaga, we, us, and our mean the Katasaga business identified in Section 1.
- Service means the Katasaga website, waitlist, web application, iOS application, APIs, live voice features, interactive stories, flashcards, and related services.
- User, you, and your mean an individual who visits the website, joins the waitlist, creates an account, or uses the Service.
- Personal data means information relating to an identified or identifiable individual.
- Processing includes collecting, storing, using, transmitting, analyzing, and deleting personal data.
- Processor means a service provider that processes personal data on Katasaga's documented instructions.
3. Age requirement
The Service is intended for individuals aged 13 or older. Katasaga does not knowingly offer accounts to individuals under 13 and does not currently provide a parental-consent registration process.
During account registration, the User must confirm that they are at least 13 years old. Katasaga does not ordinarily require the User to provide a date of birth. If Katasaga becomes aware that an account belongs to an individual under 13, Katasaga may restrict or close the account and delete associated personal data, subject to any applicable legal retention requirement.
4. Categories and sources of personal data
Katasaga collects personal data directly from the User, automatically through interaction with the Service, and, where applicable, from payment and infrastructure providers.
4.1 Public waitlist
When a User joins the pre-launch waitlist on katasaga.com, Katasaga may process the User's email address and optional information such as language interest, story preference, how the User heard about Katasaga, campaign source, referrer URL, and any other optional waitlist fields.
Waitlist information is stored in Katasaga's waitlist system and may be transmitted to Kit (formerly ConvertKit) for email-list management and launch communications. Waitlist data is logically separate from authenticated application-account data. Joining the waitlist does not create a Katasaga application account.
4.2 Account and authentication data
When a User creates or uses an account, Katasaga processes the User's email address, authentication identifiers, account timestamps, authentication events, and password credentials managed by Supabase Auth. Katasaga does not receive or store the User's password in readable form.
Katasaga may also process onboarding information supplied by the User, including learning goals, preferred learning language, and starting-level information.
4.3 Learning, voice, and conversation data
The Service processes your conversations and transcripts, session summaries and feedback, level estimates, flashcards, goals, streaks, and story progress.
Katasaga does not record or archive raw microphone audio. During a live voice session, audio is streamed in real time over LiveKit Cloud to the voice agent and to Deepgram for speech-to-text, and is not stored. The resulting text may be kept as described in Section 8.
4.4 Technical and security data
Katasaga and its infrastructure providers process the technical information needed to run and secure the Service, such as IP address, device and browser details, timestamps, and error information.
Katasaga does not use advertising products such as Google Analytics, Meta Pixel, or ad networks. Analytics are described in Section 4.7.
4.5 Subscription and transaction information
Payments are handled by Apple for iOS purchases (with RevenueCat managing subscription status) and by Stripe for web purchases, when available. Katasaga does not receive or store card numbers. Katasaga receives the subscription status needed to provide paid features.
4.6 Push-notification data
If you enable push notifications, OneSignal processes your device token and basic device details to send reminders. No transcripts or audio are sent to OneSignal. You can turn notifications off in Katasaga Settings or in your device settings.
4.7 Analytics
Katasaga uses PostHog (EU cloud region).
- Website: we use analytics to understand how many visitors there are and how they interact with the site.
- App: a signed-in User is identified by their Katasaga account and email address, which we share with PostHog to help us improve our product. Katasaga can record your usage and interactions within the Katasaga app only. We do this to understand how people use the app, to find errors, and to make the app better.
4.8 Problem reports and suggestions
The help and feedback tab lets you report a problem or suggest something. A report contains what you choose and write, plus the screen, app version and platform, and any recent error.
Adding a screenshot is optional: it is only sent if you tick the box, only the Katasaga team can see it, and it is deleted after 30 days. If you tick the box on a report about a conversation, Katasaga may read that conversation to fix the problem. You may ask for a report to be deleted by contacting dev@katasaga.com.
5. Purposes and legal bases
| Purpose | Categories of data | GDPR legal basis |
|---|---|---|
| Create and administer accounts | Email, authentication identifiers, onboarding data | Article 6(1)(b): performance of a contract |
| Provide language-learning features | Transcripts, progress, flashcards, story and scenario data | Article 6(1)(b): performance of a contract |
| Provide live voice conversations | Live audio, transcripts, session metadata | Article 6(1)(b): performance of a contract |
| Provide subscription features | Entitlement and transaction metadata | Article 6(1)(b) and Article 6(1)(c) |
| Operate the waitlist | Email and optional waitlist fields | Article 6(1)(a): consent |
| Send requested service communications | Email and account identifiers | Article 6(1)(b) and Article 6(1)(f) |
| Prevent abuse and protect the Service | Technical data, conversation signals, safety results | Article 6(1)(f): legitimate interests |
| Enforce usage limits and safety rules | Account, usage, session, and safety metadata | Article 6(1)(b) and Article 6(1)(f) |
| Maintain security and troubleshoot failures | Logs, identifiers, error and connection data | Article 6(1)(f): legitimate interests |
| Handle problem reports and suggestions | Report text and choices, screen and app information, optionally a screenshot or the related conversation | Article 6(1)(f): legitimate interests; Article 6(1)(a): consent for reading a conversation |
| Understand and improve the Service (analytics) | Account identifier, email address, usage and interaction data, device and app information | Article 6(1)(f): legitimate interests |
| Meet legal and accounting obligations | Transaction and account records | Article 6(1)(c): legal obligation |
Katasaga's legitimate interests include maintaining a secure and reliable service, preventing misuse, protecting users and providers, enforcing contractual limits, and investigating technical failures. Katasaga balances those interests against the User's rights and expectations.
6. AI processing and automated safety controls
Katasaga uses automated systems for conversations, speech-to-text, text-to-speech, scenario judging, summaries, feedback, placement estimates, and safety screening.
The safety system checks live User turns for harmful or abusive content and manipulation attempts, and may end a session automatically.
AI output is not reviewed by a human and may be inaccurate or inappropriate. Katasaga's AI features are for language practice, not professional, medical, legal, financial, certification, crisis, or emergency services.
Katasaga does not make decisions with legal or similarly significant effects solely by automated means. You can contact dev@katasaga.com about a moderation or access decision, and report any AI response or other problem through the help and feedback tab (Section 4.8).
7. Processors and recipients
Katasaga uses the following providers. Their role and applicable processing may change as the Service develops.
Katasaga uses the providers below as processors on its instructions. Katasaga does not record or keep live voice audio and configures providers not to train on conversation data where such controls are available. The list is updated when providers change.
| Provider | Role | Data processed | Location / transfer context |
|---|---|---|---|
| Supabase | Database, authentication, storage, Edge Functions, and applicable Auth email delivery | Account data, transcripts, learning data, technical data, entitlement status | Primary project region selected in Germany / West Europe. Provider support and other processing locations may differ. |
| LiveKit Cloud | Real-time voice transport | Audio in transit and operational metadata | Processing and logging locations are governed by the LiveKit service configuration and applicable DPA. |
| Deepgram | Speech-to-text | Live microphone audio and transcription requests | United States; Katasaga configures applicable model-improvement opt-out controls where available. |
| Mistral AI | Conversational model, scenario judge, and safety screening | Conversation text and prompts | France / European Union, subject to applicable Mistral terms and DPA. |
| Cartesia | Text-to-speech | Text submitted to generate spoken responses | United States, subject to the API terms and privacy commitments applicable to the Katasaga account. |
| Amazon Web Services (AWS) | Cloud infrastructure and hosting of language, speech-to-text, and text-to-speech models, including third-party models offered through AWS, where used | Conversation text and prompts, and live audio where speech models are used | EU, US, or other regions depending on the region Katasaga selects; subject to the AWS Data Processing Addendum and Section 9. |
| Microsoft (Azure) | Cloud infrastructure and hosting of language, speech-to-text, and text-to-speech models, including third-party models offered through Azure, where used | Conversation text and prompts, and live audio where speech models are used | EU, US, or other regions depending on the region Katasaga selects; subject to the Microsoft Data Protection Addendum and Section 9. |
| Kit | Waitlist and email automation | Waitlist email and optional waitlist fields only | United States; does not receive authenticated app conversations. |
| RevenueCat | iOS subscription status | App-user ID, product and subscription status | United States. |
| Stripe | Web payments, when available | Email, customer and subscription details | Stripe processing locations and transfer safeguards apply. |
| OneSignal | Push notifications, if enabled | Device token, subscriber ID, basic device details | United States; no transcripts or audio. |
| PostHog | Analytics | Account identifier, email address, usage and interaction data, device and app information | EU cloud region. PostHog is operated by a US company, so the safeguards in Section 9 apply. |
Katasaga may disclose personal data to competent authorities where legally required, professional advisers subject to confidentiality, or a successor in connection with a merger, acquisition, restructuring, or transfer of relevant assets.
Katasaga does not sell personal data.
8. Retention and deletion
Conversation transcripts and related session data are retained until deleted by the User or removed under the User's selected automatic-deletion setting. The default setting is indefinite retention. Available automatic-deletion periods are 1 week, 1 month, 3 months, and 1 year, with deletion performed by a scheduled process.
Transcript-linked data includes conversation transcripts, CEFR rationale text, weak-spot evidence text, full session summaries, session-specific skill records, and related conversation records.
The following learning records may remain after transcript-linked deletion: current CEFR-style level and confidence value, weak-spot categories and labels without evidence text, long-term goals, streaks, aggregate progress, flashcards, and flashcard-review records until the User deletes them or deletes the account.
A User may permanently delete the account through Settings. Katasaga will delete associated data from its systems, subject to limited records that must be retained for legal, accounting, security, fraud-prevention, or dispute-resolution purposes. Providers may retain limited records under their own legal or contractual retention rules.
Katasaga does not archive raw microphone audio. Providers may keep limited operational or security logs under their own terms.
9. International transfers and safeguards
Katasaga's primary Supabase project region is located in Germany / West Europe. A User's location does not automatically create a regional copy of the primary database.
Some providers process personal data outside the European Economic Area, including in the United States and other regions. Where required, Katasaga relies on an applicable Data Processing Addendum, Standard Contractual Clauses, the EU–US Data Privacy Framework where applicable, or another lawful transfer mechanism. Safeguards may depend on the specific service, account, plan, and configuration.
10. Data-subject rights
Subject to the GDPR, a User may request access, rectification, erasure, restriction, portability where applicable, information about processing, or object to processing based on legitimate interests. A User may withdraw consent where consent is the legal basis.
Requests should be sent to dev@katasaga.com. Katasaga may request information reasonably necessary to verify the requester's identity and will respond within the period required by law.
A User may lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) at autoriteitpersoonsgegevens.nl.
11. Security
Katasaga uses appropriate security measures, including access controls, encryption in transit, and database row-level security. No internet service can guarantee absolute security.
12. Cookies and similar technologies
Katasaga uses cookies or local storage for authentication, security, preferences, and analytics. The public website uses analytics without cookies. Katasaga does not use advertising cookies.
13. Marketing and communications
Waitlist and marketing emails are sent only where permitted by applicable law and, where required, with consent. Each marketing email includes an unsubscribe mechanism. Unsubscribing stops marketing messages but does not necessarily stop essential service messages such as security, account, or transaction communications.
14. Changes to this Privacy Policy
Katasaga may update this Privacy Policy when the Service, providers, processing activities, or legal requirements change. Katasaga will publish the updated version with a new effective date and provide additional notice for material changes where required or appropriate.
15. Contact
Privacy questions and requests: dev@katasaga.com