robiko Join the alpha
Back to Robiko

Privacy Policy

Effective date: 2026 Contact: oleh.kostashchuj@kostcode.com

This Privacy Policy describes how the Robiko app (“we”, “the app”) collects, uses, and protects user information, including information about young students who use the app in a classroom setting via a class code provided by their teacher.

If you have questions about this policy, please contact us at oleh.kostashchuj@kostcode.com.

1. Who this policy applies to

Robiko is an educational app for practicing reading aloud, designed for primary-school students, their teachers, and their parents. Students join the app using a class code issued by their teacher — meaning a child's use of the app happens under school supervision, not as an independent, self-registered internet user.

If you are under 16, please only use the app together with a teacher or parent.

2. What information we collect

2.1. Account information

  • Teachers and parents: name, email address, password (stored hashed — we never see or store your password in plain text).
  • Students: name or nickname, a chosen avatar, and class membership — no email address or other direct contact information, unless required for the parent-linking feature.

2.2. Reading and progress data

Books a student reads, pages read, reading session duration, points earned (XP), badges/achievements, and weekly challenge results — used exclusively to show progress to the student, their teacher, and their parents within the app.

2.3. Voice recordings

While a student practices reading aloud, the app records their voice only for the duration of a single analysis session. This recording:

  • is sent to our server and immediately forwarded to a speech-recognition service to produce a transcript and a reading/pronunciation score;
  • is never stored on our servers — the file is deleted immediately after processing, whether or not the processing succeeds;
  • is never listened to by a human, and is never used for any purpose other than automatically scoring the reading session;
  • is only held temporarily on the device itself, in a system cache/temporary directory during recording and upload, not in permanent device storage.

We only retain the result of processing the voice recording — the recognized text and the reading score (e.g. which words were read correctly) — never the audio itself.

2.4. Technical data

Basic technical information used for diagnosing app errors (device type, OS version, error message) — used solely to fix technical issues.

2.5. Payment data (in-app purchases)

If in-app purchases are available in the app, they are processed directly by Google Play / the App Store, not by us — we never see or store your payment card details. We only receive confirmation that a purchase was completed.

3. How we use information

  • Showing reading progress to the student, their teacher (for their own class), and their parents (for their own child);
  • Automatically scoring pronunciation and reading aloud;
  • Gamification (badges, in-class leaderboards, weekly challenges);
  • Technical support and bug fixing;
  • Fulfilling in-app purchases, where applicable.

We do not use children's data for advertising, do not show personalized/targeted ads to children, and do not sell user data to third parties.

4. Who we share data with

  • Teachers — progress data for the students in their own class.
  • Parents — progress data for their own child (once a verified parent-child link exists).
  • Our processing providers — Audra receives book files and performs extraction and reading analysis; Microsoft Azure Speech processes transient voice audio for scoring. Audra may use OpenAI for embeddings/LLM features and Unstructured for PDF extraction. These providers are subject to our processor review and must have an approved DPA, region, retention, and deletion arrangement before production child data is enabled.
  • Error diagnostics (Sentry) are disabled by default. If enabled for a specifically approved support window, we send technical error context only and do not enable PII collection.

We do not sell and do not share data with advertisers or any third party for marketing purposes.

5. Data security

All data transmitted between the app and our servers is sent over a secure connection (HTTPS/TLS). Passwords are stored hashed and are never stored in plain text.

6. Data retention and deletion

Student and parent account and reading-progress data is retained for up to 730 days after the last authenticated use, followed by a 30-day deletion-candidate period. Teachers or parents may request deletion of a student's data at any time by contacting oleh.kostashchuj@kostcode.com — we will delete it within 30 days.

Class-owned books are not deleted when one student leaves. Student-owned books are deleted from Reader and the Audra service as part of the student's permanent deletion. Voice recordings are intended to remain transient; Audra STT archiving is disabled.

7. Parent and teacher rights

Parents and teachers may:

  • request a summary of what data has been collected about a student;
  • request correction of inaccurate data;
  • request full deletion of a student's account and associated data.

8. Changes to this policy

We may update this policy from time to time. We will notify teachers/parents of material changes through the app or by email.

9. Contact

For privacy-related questions, contact us at: oleh.kostashchuj@kostcode.com