Sign inGet started

Privacy

Last updated: 12 May 2026

BlueCare is engineered to handle children's data with care. This page describes what we collect, why, where it lives, and what choices you have. It reflects how the product actually works — not generic templates.

Who we are

BlueCare is operated by the BlueCare team, originating from a senior project at Jeddah International College, Computer Science department. For data-protection inquiries, email privacy@bluecare.app.

What we collect

Account-level data: caregiver email, name, locale, theme preference. Child-profile data (only data the caregiver enters): preferred name, age, language, sensory profile, vocabulary level, voice selection. Usage events: which symbols a child selected, when, and via which input modality (symbol/voice/gesture). We do NOT store raw transcripts of a child's speech. We do NOT keep video frames from gesture mode beyond the moment they are processed.

Why we collect it

(1) To run the product — without a profile we cannot show a board. (2) To personalize vocabulary suggestions, which a caregiver reviews before they take effect. (3) To build progress views for caregivers and therapists. We do NOT collect for advertising. We do NOT sell data. We do NOT train models on child input.

Lawful basis

For caregivers in Saudi Arabia, we process under PDPL Article 5 with explicit caregiver consent. For users in the EEA / UK, we process under GDPR Articles 6(1)(a) (consent) and 6(1)(b) (contract). Each consent scope (data processing, voice recording, webcam processing, AI personalization, analytics dashboard) can be granted or revoked independently.

Third parties

We use Supabase (managed Postgres + Auth + Storage) for application data, hosted in Sydney. Voice synthesis routes through two TTS providers: ElevenLabs Multilingual v2 (Charlotte voice) for Arabic, and OpenAI tts-1-hd (Nova voice) for English; both transparently fall back to each other on outage. Speech recognition uses OpenAI Whisper. Optional vocabulary personalization uses Anthropic Claude Sonnet ONLY when a caregiver explicitly enables it. Every cloud TTS call is metered against a per-child 0/month cost cap. Audio data sent to the speech provider is never persisted on our side; it lives in memory only for the duration of the request.

How long we keep data

Active accounts: as long as you keep them. Audit log entries: 24 months. Anonymized aggregate metrics: indefinitely (no individual identifiable). On account deletion: tombstoned immediately, purged within 30 days end-to-end, including from backups within their retention window.

Your rights

Access, rectification, erasure, restriction, portability, and objection — all available from the dashboard or by emailing privacy@bluecare.app. We respond within 30 days. You can also lodge a complaint with the Saudi Data & AI Authority or your local supervisory authority.

About children's data

Children do not authenticate directly. A child's profile is owned by a caregiver. Caregivers attest to consent on behalf of the child for each scope. We minimize the data we collect about children, never expose it to third-party analytics, and treat it as the most sensitive class of data in the system.

Changes

We will update this page whenever the data flows or providers change, and we will email caregivers about any material change at least 30 days before it takes effect.