Children's Privacy Statement

WakeKids is designed around a narrow principle: the parent is in control, and the child is a recipient of routine wake-up alarms rather than a tracked subject.

We collect only the information needed to prepare a short-lived pairing request, connect the devices after the parent authorizes pairing, deliver alarms, show the correct family identity, and protect the service from abuse.

WakeKids is operated by SOFTWARECARAFT SRL. Registered office: Calea Rahovei no. 303, building 66, entrance 1, apartment 42, Sector 5, Bucharest, Romania. Fiscal Code: 51542766. Registration: J2025022901007. EUID: ROONRC.J2025022901007. Email: softwarecaraft@gmail.com. Telephone: +40 766 239 722.

The child does not create a conventional account and does not sign in with an email and password. The child device requests an anonymous, short-lived pairing session. A random, pairing-scoped identity is created by our backend only after the parent authorizes the connection, and only then can the device receive alarms.

The child app may show the child's first name, the next scheduled alarm, the connected parent identity, a full-screen alarm when one fires, and settings for theme, notification permissions, and legal information.

The paired-child Settings screen provides a confirmed disconnect control. The authenticated parent can also disconnect the pair, and a parent or child can contact us for deletion support.

WakeKids does not provide public profiles, messaging, social posting, content feeds, behavioral recommendations, or advertising surfaces for children.

Pairing records affirmative authorization by an authenticated parent or legal guardian. The parent first verifies control of the parent-account email, scans the QR code shown on the child phone or enters its six-character code manually, reads an on-screen notice listing exactly what will be stored about the child device, confirms authority, and actively connects the device. The pair record stores the authorization method, time, and policy version associated with that action.

Camera frames used to scan the QR code are processed only on the parent device to read the code; they are not stored or uploaded. Scanning alone does not complete pairing.

Before the parent authorizes the connection, the child device sends no name, year of birth, hardware identifier, push token or Firebase identity. The pairing session holds only a random six-character code, the hash of a separate secret held on the child device, and its creation and expiry times. The code expires after 15 minutes.

Approximately 24 hours after pairing, we email the verified address on the authenticated parent account a second copy of the notice, listing what is stored about the child and containing a link that disconnects the device and starts permanent deletion of the stored child data. Active pairing records are removed as part of that cleanup; the disabled technical Auth identity is deleted after the two-hour safety window described below. The delay gives a parent who did not authorize the connection a realistic opportunity to discover and undo it. A notice reported as undeliverable, or whose delivery remains unconfirmed after 48 hours, is flagged for operational review. Delivery tracking cannot prove that a person read the message.

Removal requires a deliberate action on the linked page, so link-preview and email-security scanners cannot delete a pairing by fetching the URL.

An authenticated account and authorization record do not independently prove the person's identity or legal relationship to the child. The operator confirmed on July 31, 2026 that qualified legal counsel approved the consent method and complete pairing flow for the intended launch configuration.

In the app, the parent can review everything stored about their child under Privacy settings, disconnect a child device, remove alarms, and delete the parent account where available. By web or email request, the parent can ask for data export, deletion support, correction, restriction, objection, or other privacy help.

If a child device was paired without proper authority, contact softwarecaraft@gmail.com so we can review and delete the relevant data where appropriate.

We collect a nickname, chosen and entered by the parent, so the parent can recognize the paired child and the child can recognize the wake-up screen. We ask parents to use a nickname rather than a full name.

We do not collect a child's year of birth, date of birth or age, and we do not perform automated age assurance. We process a device push notification token as personal technical data so alarms can ring on the child phone.

We do not collect any hardware device identifier from the child phone. The child's identity is a random value generated by our backend after the parent authorizes the connection, and it is scoped to that single pairing. We also process alarm schedules, whether the wake screen was acknowledged, pairing status, and authorization records related to the child device.

The child profile, pairing information, and alarm activity are not sent to RevenueCat. RevenueCat is configured only for the authenticated parent account.

We do not collect child location, GPS, Wi-Fi location, contacts, calendar, photos, microphone content, camera content, other installed apps, app usage outside WakeKids, screen time, web browsing, search history, advertising identifiers, biometric data, voice recordings, or behavioral profiles.

We do not sell child data, rent child data, use child data for advertising, or share child data for third-party marketing or profiling.

Child profiles and pair records are kept until the parent disconnects the pair, withdraws consent through the link in the notice, deletes the parent account, or a verified deletion request is completed.

Alarm events are intended to be kept for no more than 180 days and are deleted earlier when the relevant pair or account is removed. Production TTL must be enabled and verified before automatic expiry is treated as operational.

Pairing tokens cannot be used after 15 minutes and are intended to be removed by expiry cleanup after production TTL is enabled and verified. Deletion requests may take time to propagate through active systems and provider backups, as described in the Privacy Policy.

Disconnecting, withdrawing consent through the notice, or deleting the parent account immediately blocks the pairing and starts removal of active pair, alarm, and event records. The child's pairing-scoped Firebase Authentication identity is disabled and its refresh tokens are revoked immediately; final deletion follows a two-hour custom-token safety window and is retried automatically if cleanup is interrupted.

Parents can review child information in the app where available, including paired child details and alarm-related status.

In the app, parents can disconnect a child device, remove alarms, and delete the parent account where available. The paired-child Settings screen also provides a confirmed disconnect control. These controls withdraw consent for future child data processing tied to the removed pairing or account.

By web or email request, parents can ask for access, correction, export, deletion support, restriction, objection, and other privacy help that is not available directly in the app. Contact softwarecaraft@gmail.com. We aim to respond within 30 days, or sooner where required by law.

COPPA may require direct notice and verifiable parental consent before personal information is collected from a child under 13. Our current method is the authorization action taken from the authenticated parent account, followed by the delayed confirming notice described above.

That structure is available only to operators that do not disclose children's personal information to third parties. We rely on that condition: information about a child is used solely to operate the alarm service, is never sold, and is never shared with advertisers or other third parties. WakeKids contains no advertising and no advertising SDKs, and the child role sends no analytics.

The flow first requires a verified parent-account email, records an authenticated adult's affirmative authorization, and sends that address the delayed confirming notice with a time-limited removal link. This verifies control of the email address but does not independently verify that adult's identity or legal relationship to the child. The operator confirmed on July 31, 2026 that qualified legal counsel approved the consent method and complete pairing flow described above for the intended launch configuration.

WakeKids is designed to collect only information reasonably necessary to provide the wake-up alarm service, not condition child participation on unnecessary disclosure, provide no public disclosure surface, and let parents review, delete, and refuse further collection of child data.

For users in the United Kingdom, WakeKids is designed to align with Children's Code principles for a narrow routine wake-up function.

Our approach emphasizes data minimization, privacy-protective defaults, plain-language transparency, no profiling, no advertising, and no detrimental use of child data. Paired-child settings expose legal information, notification-permission status, an offline child-readable privacy summary, and a confirmed disconnect control.

This design statement does not replace a documented best-interests assessment, age-assurance analysis, or data-protection impact assessment.

For questions, parental requests, privacy requests, or complaints relating to a child's data, contact SOFTWARECARAFT SRL at softwarecaraft@gmail.com or +40 766 239 722. Registered office: Calea Rahovei no. 303, building 66, entrance 1, apartment 42, Sector 5, Bucharest, Romania.

You may also contact your national supervisory authority, such as ANSPDCP in Romania, the ICO in the United Kingdom, or the FTC or your state Attorney General for COPPA-related matters in the United States.