1Who we are and why this document exists
“Abby” (the “App”) is a mobile app for activities with children aged 2–6 with autism spectrum disorder (ASD) and developmental delays. The App is built on the principles of Applied Behavior Analysis (ABA) and uses an adaptive BKT (Bayesian Knowledge Tracing) engine to select tasks based on a child’s level of skill mastery.
The personal-data controller (the “Operator”, “we”) is the Abby team. As of the publication date of this policy, the App has no registered legal entity; the policy will be updated once one is established.
You can contact us about privacy at hi@abby.study. This policy is written to account for the GDPR, UK GDPR, the ICO Age Appropriate Design Code, COPPA (16 CFR Part 312) as amended in 2025, Apple App Store Review Guideline 5.1, the Google Play Families policy, and Russian Federal Law 152-FZ “On Personal Data”.
2Who the data subjects are
- Parent / legal guardian — the adult user who creates the account and the child’s profile and gives consent for processing.
- Child — the end user of the activities. We do not give the child independent access to the account, settings, network features, or chat. All decisions about a child’s data are made by the parent.
The “one profile per device” model (B2C): on a personal device, one child = one profile. For centers and specialists (B2B), multiple profiles with adult-operator access are allowed.
3What data we collect
3.1. Parent (account) data
- email for sign-in via magic link or a 6-digit code through Supabase Auth;
- session identifier / authentication token;
- optionally — device country and language for localization.
We do not collect passwords (there are none — sign-in is by link or code), card numbers, phone numbers, geolocation, contacts, or photos.
3.2. Child profile data (entered by the parent)
- name or nickname (the parent may enter a nickname);
- age or date of birth;
- gender (optional);
- verbal / nonverbal status;
- interests (cartoons, food, colors) — for personalization.
3.3. Activity data (generated automatically)
- answer accuracy, response time, number and type of prompts, attempts;
- skill-mastery estimates from the BKT model;
- an activity log at the level of individual trials;
- aggregated weekly plans and recommendations.
3.4. Technical data
- app and OS version, device model, an anonymized device identifier (no advertising identifiers / IDFA);
- error logs (without answer content).
We do not use third-party SDKs for advertising, tracking, or behavioral analytics. We do not use the IDFA and do not run cross-app targeting. The App contains no ads, social networks, or content sharing between users.
The App offers a paid subscription (purchased through the App Store on iOS or on the website) and an AI assistant, “Pingi”, which the parent interacts with. The child has no access to purchases or network features.
4Legal bases for processing (GDPR Art. 6 and 9)
| Purpose | Data | Basis |
|---|---|---|
| Creating the parent account, authentication | email, tokens | Art. 6(1)(b) — performance of a contract |
| Running the App locally on the device | Everything listed in §3 | Art. 6(1)(b) — performance of a contract |
| Cloud synchronization between devices | Everything listed in §3 | Art. 6(1)(a) — explicit parental consent, withdrawable at any time |
| Generating AI plans and tips | Aggregated skill metrics, child profile | Art. 6(1)(a) — explicit parental consent |
| Security, abuse prevention | Logs, IP on the Supabase side | Art. 6(1)(f) — legitimate interest |
Special categories of data (GDPR Art. 9). The fact of using an ABA app and linking activities to a specific child may be interpreted as “data concerning health”. We assume such an interpretation is possible and additionally rely on Art. 9(2)(a) (explicit parental consent) and Art. 8 GDPR (consent of the legal guardian on behalf of a child below the age of consent). The parent may withdraw consent at any time without affecting the lawfulness of prior processing (GDPR Art. 7(3)).
5Parental consent (COPPA — verifiable parental consent)
- for the App’s basic on-device operation without cloud sync, we rely on the “internal operations” exception (§ 312.5(c)(7)), which does not require verifiable parental consent;
- for cloud sync and AI features, we obtain verifiable consent through an adult’s email sign-in with a magic link, a separate consent screen that logs the time, IP, and policy-text version, and — for U.S. users — optionally enhanced verification;
- we do not use the “email plus” method as the sole method for high-risk processing.
6Who we share data with
We engage the following sub-processors under GDPR Art. 28:
| Provider | Role | Jurisdiction |
|---|---|---|
| Supabase, Inc. | Database storage, authentication, Edge Functions | EU region (Frankfurt) |
| OpenRouter, Inc. | LLM routing for AI plan generation | USA; providers with Zero Data Retention |
| Apple, Inc. | Distribution via the App Store, TestFlight | USA / Ireland |
API keys are not stored in the client — all LLM calls go through a Supabase Edge Function. We send OpenRouter only de-identified aggregates: a child’s name is replaced with “child”, age is reduced to a range, and only skills and metrics are sent. We do not sell personal data and do not share it with advertising networks or data brokers.
7Cross-border data transfers
Your data is stored in the EU region (Frankfurt, Germany) regardless of where you access the App from. Transfer to OpenRouter (USA) is carried out on the basis of the Standard Contractual Clauses (Module 2, controller → processor). We perform a Transfer Impact Assessment using the EDPB methodology.
8Russian users and 152-FZ
Russian Federal Law No. 152-FZ (Art. 18(5)) requires the initial recording and storage of the personal data of Russian citizens in databases located within the Russian Federation. Abby’s current infrastructure (Supabase EU) does not fully meet this requirement.
We are working on one of the following solutions:
- moving the initial recording of Russian citizens’ personal data to a server in Russia, with subsequent synchronization to the EU;
- limiting distribution of the App in Russia until the matter is resolved;
- collecting separate informed consent from Russian users with explicit disclosure of the data-storage location.
Until the first option is implemented, Russian users who continue to use the App confirm that they have read this section. This does not remove the legal risk, and a parent may demand deletion of data at any time.
9Retention periods
| Category | Period |
|---|---|
| Child profile and activity data (active account) | Until a deletion request or 24 months of inactivity |
| Parent account data | Until account deletion |
| Error and audit logs | 90 days |
| Backups | 30 days from deletion of the primary record |
| Financial / legal records (if applicable) | 5 years as required by law |
We process a deletion request within 30 calendar days (GDPR Art. 12(3)). Backups are purged automatically on rotation.
10Your rights
As a parent or legal guardian, you have the right:
- to access — obtain a copy of the data (Art. 15);
- to rectification of inaccurate data (Art. 16);
- to erasure / the “right to be forgotten” (Art. 17);
- to restriction of processing (Art. 18);
- to portability — a machine-readable export (Art. 20);
- to object to processing based on legitimate interest (Art. 21);
- not to be subject to automated decision-making (Art. 22) — our BKT/AI does not make legally significant decisions;
- to withdraw consent at any time (Art. 7(3));
- to lodge a complaint with a supervisory authority: in the EU — the DPA of your country of residence, in the UK — the ICO, in Russia — Roskomnadzor, in the U.S. — the FTC.
Under COPPA, a parent additionally has the right to review the child’s collected data, demand its deletion, and refuse further collection. Send requests to hi@abby.study — we identify the requester by the account email and respond within 30 days.
11Security
- encryption in transit: TLS 1.2 and above;
- encryption at rest: AES-256 on the Supabase side, Hive encryption on the device;
- Row-Level Security: all tables are protected, with access only for the owner-parent;
- API secrets are stored in Supabase Secrets and never reach the client;
- minimization: the LLM model receives only the fields it needs.
12Children and the age of consent
The App is made for children, but consent on their behalf is given by the parent. The child never interacts with network features, chat, purchases, or ads. Parental controls (PIN, kiosk mode) restrict leaving an activity. We do not accept accounts created directly by children under 13.
13Changes to this policy
We will notify the parent of material changes 14 days before they take effect — by email and via a re-consent screen in the App. An archive of previous versions is available on request.
14Contact
For any questions about privacy and data processing, write to hi@abby.study.
© 2026 Abby. hi@abby.study