Privacy Policy

Dental Kid Brush

Effective date: 2026-10-12

This policy explains how this application handles information and how to contact us about privacy.

Information we process

Dental Kid Brush stores game progress, a partially completed round, earned stickers and brushing-calendar entries, the patient collection, and settings on the device. No names, email addresses, passwords, photos, recordings or precise location are requested. The app does not use the camera or microphone. A random installation UUID is stored in the device Keychain and sent to our backend to register or delete that installation. The backend stores only a SHA-256 hash of the UUID and the registration timestamp; it also stores shared daily guest dates and game configurations. Local progress and brushing-calendar entries are not sent to the backend. Requests necessarily pass through hosting infrastructure, which can process network addresses, request metadata and operational logs. The backend temporarily uses direct peer network addresses in memory for rate limiting.

How we use information

Local data lets the child resume rounds, unlock levels, view the patient collection, and see earned brushing stickers. Settings remember language and parent-selected preferences. The shared daily guest service provides optional daily game content without requiring an account or identifying the child. The installation hash supports deletion of that installation's server record. Temporary rate-limit state and database health checks support service availability. Local notifications, if enabled by a parent, remind the device about brushing times. We do not use this information for advertising, profiling, analytics, purchases or email delivery.

Service providers and sharing

The backend and its PostgreSQL database are hosted on Railway. Railway and its infrastructure providers process service requests and the information needed to operate that hosting. The app does not integrate advertising, analytics, social-login or messaging services, and does not sell information or publish a child's progress. Infrastructure providers may process operational and access logs under their own service practices. We have not specified or independently established an exact provider log-retention period. Apple processes device notification permission decisions and Keychain storage through system features; these reminders are scheduled locally and do not require a push-notification backend.

Data retention

Game progress, calendar stickers, patient collection and settings remain locally until reset or deleted, or until the device removes the app's local storage. Keychain credentials can remain after app removal according to device behavior. The installation hash and registration timestamp remain on the server until a deletion request for that credential succeeds. Shared daily configurations are retained as non-personal game content. The backend keeps rate-limit network addresses only in bounded process memory for approximately one minute and does not write them to its database or application logs. Railway infrastructure log and backup retention depends on the hosting configuration and provider practices; no exact period or immediate backup purge is promised. The app does not provide a cloud backup or account-based restoration of game progress.

Deleting your information

Parents can open the protected Settings and delete local game data and request deletion of the installation's server record. The server request uses the installation UUID in an authorization header and removes only its matching stored hash; shared daily game configurations remain. The app reports a network failure and allows retry rather than claiming that server deletion succeeded. The credential must remain available until the deletion is confirmed. Deleting the live record does not guarantee its immediate removal from infrastructure logs or provider backups. If the credential is lost, we cannot identify the corresponding anonymous installation record or promise restoration. Privacy questions or requests can be sent to the contact email below; no in-app email or support form is used.

Permissions and your choices

Notifications are optional. A parent must pass the parent gate and explicitly enable reminders before the app requests the system notification permission. Reminders are local to the device. Parents can change reminder times or disable them in the app and can withdraw notification permission in iOS Settings. The game remains usable without notifications or network access; an unavailable daily guest uses bundled fallback content with an offline label. Camera, microphone, contacts, photos and location permissions are not required. The parent gate also protects settings and external privacy links.

Your privacy rights

Depending on applicable law, you may have rights to request information about processing, correction, deletion, restriction or to raise a privacy concern with the appropriate authority. Contact inigo.ridgely@icloud.com for privacy questions and requests. Most game information is stored only on your device, so local controls are the direct way to reset or remove it. The backend cannot retrieve a child's calendar or progress because it does not receive that data. We may need enough information to understand a request, but do not ask you to disclose a child's name or send an installation credential by email. This policy does not promise account recovery or access to a record after its credential has been lost.

Security

The deployed app communicates with the public backend over HTTPS. The random installation credential is kept in the device Keychain, sent in a JSON registration body or deletion authorization header, and hashed before storage. Database credentials stay on the server. Parameterized database queries, limited body sizes, request timeouts and bounded rate limits protect API operations. The application does not log installation secrets, their hashes, authorization headers or request bodies. Hosting infrastructure can maintain its own operational logs. No method of storage or transmission is guaranteed completely secure, and no security certification is claimed.

Children’s privacy

Dental Kid Brush is designed for children aged 4 to 8 with parents managing settings and optional reminders. Play does not require a user account, a child's identity or contact details. Game activity and the brushing calendar stay on the device; optional server content is shared daily game data rather than a child profile. There are no advertisements, in-app purchases, analytics or social features. Settings, deletion, reminder permission requests and external links are protected by the parent gate. Parents may use the deletion controls and contact the privacy email if they have concerns about their child's information.

Changes to this policy

We may update this policy when the application's features, hosting or information practices change. The effective date above identifies the current policy, which is available from the app's protected Settings and at the public privacy page on the same service. Changes to processing will be reflected in this document; an updated policy is not a promise of email notice or an account notification. Parents should review the policy when updating the app and can contact inigo.ridgely@icloud.com with questions.