KlioAI logo KlioAI
Home Account deletion Terms

Legal

Privacy Policy

This page explains the high-level privacy posture of KlioAI for the public website, mobile application, and API services.

KlioAI is operated by Eren Ulutas for the Android app listed on Google Play under package name com.VocabMaster.

Last updated: July 9, 2026

1. What we collect

We may collect account details, authentication data, subscription state, usage activity, learning progress, and technical logs needed to operate the service.

If you use AI-assisted features, your prompts and related output may be processed to deliver the requested experience and to maintain product quality and abuse protection.

Speaking and pronunciation practice audio is processed transiently to generate a transcript and is not stored after your report is produced.

2. Why we use data

Data is used to provide the product, authenticate users, enforce quotas and security controls, store learning progress, support subscriptions, and maintain service reliability.

3. Infrastructure and processors

KlioAI runs on production infrastructure that includes application servers, PostgreSQL, Redis, and reverse proxying, plus these named third-party processors:

  • Google Sign-In — the only supported sign-in method; used to authenticate your account.
  • Google Play Billing — processes subscription purchases; KlioAI does not collect or store your payment card details.
  • Firebase Analytics (Google) — aggregate usage and feature-engagement analytics.
  • Firebase Crashlytics (Google) — crash and error reporting to help us fix bugs; reports may include a device-scoped identifier and, when signed in, your account id.
  • Firebase Cloud Messaging (Google) — delivers push notifications (e.g. daily reminders) you have opted into.
  • Groq — processes AI text prompts/output and speech-to-text transcription for AI-assisted practice features.

4. Security

We use transport encryption, authenticated API access, production security headers, segmented cache roles, and backup procedures to reduce operational risk. No system can be guaranteed perfectly secure.

5. Retention

We retain operational and account data for as long as needed to run the service, comply with legal obligations, resolve disputes, or enforce agreements.

Users can request account and data deletion through the public Account and Data Deletion page.

6. Contact

For privacy-related requests, contact the service operator through the in-app support ticket flow or the support contact published in the Google Play listing.