Saqroon
Saqroon app privacy
This notice covers the Android app: what it keeps on the device, what reaches the server once a family is paired, and the optional services. Signing up on this website is covered by the site privacy notice.
For pilot support or data-deletion requests: fatoh.haj@gmail.com.
Optional QR pairing camera
Opening the pairing scanner requests camera access to read a parent's Saqroon QR code. Pairing camera frames are processed on the device and are not saved or uploaded by the app. Only the decoded short-lived pairing code is sent to Firebase to link the phones. You can type the code instead without camera access. This differs from the optional learning-page scan described below.
For parents and guardians
Saqroon is being prepared for an Android pilot with Arabic-speaking families and children ages 5–12. A parent or guardian reviews this notice and completes setup. This pilot draft still needs a verified operator name, direct support contact and privacy review before family invitations.
What stays on the device
The app stores a child nickname, age experience, learning level, answers and completion history, XP, reward tokens, reward receipts and settings. Usage monitoring, when a parent enables it and grants Android permissions, reads application usage on the device to decide when to show a checkpoint. The device may store app names/categories and usage duration. Precise location, contacts and browser-page history are not requested by this implementation.
When a family is paired
Firebase stores account and device identifiers, family membership, settings and remote-lock instructions. A paired child device sends its nickname, progress totals, accuracy, focus minutes, streak, screen-credit balance and daily summaries. It also sends up to five leading app names, categories and usage minutes for the current day. Detailed raw usage events are processed locally. The parent dashboard reads the permitted family summaries.
Optional cloud learning and voice
If an adult requests AI questions, the topic, subject, learning band and language are sent through the backend to configured AI providers. If the adult chooses scanning, the selected page images are also sent for processing; avoid child faces, names and sensitive material. Generated questions wait for parent approval. Cloud narration sends the requested text and language to the voice provider. Reviewed bundled narration can play offline. These features use Firebase, ElevenLabs and configured AI providers such as Anthropic or OpenAI; which provider handles a request depends on backend configuration. Provider retention and transfer arrangements require operator review.
Consent and optional services
Cloud startup and native monitoring are gated on completed parental consent and setup. Monitoring additionally depends on device role, parent settings and Android permissions. Crashlytics automatic collection is disabled in the pilot configuration. The code includes a crash SDK and a billing SDK, but paid billing is disabled by default. No advertising SDK or advertising is included in the app. Fresh-install network behavior still requires device verification.
Access and operational records
The server records entitlement source and expiry, pilot invitation redemption, quota reservations, request-rate counters and operational logs. Invited access lasts 30 days without payment details; expiry preserves local progress. Existing verified legacy grants keep their original expiry. No sale of personal information is part of this pilot plan. Service providers process data to operate the requested cloud features.
Unlinking and deletion
Unlinking a child device removes its cloud membership, settings override and synced history, while preserving local progress. Deleting from a child device removes that device/account’s data; deleting the owner account removes the owner family’s cloud records. Cloud erasure needs a connection and failures are shown for retry before local deletion is reported complete. A minimal protected account-deletion marker remains to prevent stale credentials recreating erased data. Its retention period and provider/backup deletion arrangements need final operator review.
Storage and security
Local progress remains until it is deleted from the app or device. Cloud family records are currently retained until deletion. Firebase access rules isolate families; traffic uses HTTPS. Backend functions are configured in us-central1; the actual Firestore location, provider retention and cross-border arrangements must be verified before invitations. No implementation can promise perfect security or controls that survive every operating-system restriction.
Pilot signup and feedback
The separate marketing signup collects parent contact information, town, a broad child age band, Android availability, consent and campaign source. It does not ask for child names. The app’s feedback tool copies a report for the parent to share; it does not send it automatically. Do not include sensitive child information.
Contact and changes
For access, deletion or support requests, write to support@saqroon.com. Pilot families may also use the coordinator contact supplied with their invitation. A material data-use change triggers renewed parental consent. The responsible operator, and the retention period for the account-deletion marker, are still under review; this notice is not a completed legal review.