Privacy Policy
How TinyLeap handles family and child information
Effective: August 22, 2026 · Version 2.4
Scope and operator
This Privacy Policy explains how TinyLeap handles information entered, generated, displayed, stored, or synchronized when you use the app and its Apple-device extensions. TinyLeap is intended for adults who are parents, legal guardians, or authorized caregivers and is not intended for independent use by children.
The data controller and operator of TinyLeap is Guy Aharonin, the individual developer and sole proprietor operating TinyLeap in Israel (“Operator”). Public Privacy and Support contact: tinyleapsupport@gmail.com. In the rest of this Policy, references to “TinyLeap,” “we,” “us,” or the “Operator” refer to that operation as appropriate.
Information you may provide or create
Depending on the features you use, information may include a child’s name or nickname, date of birth, expected due date, premature-birth status and gestational week, profile photo or selected avatar, caregiver names or permissions, feeding and diaper records, sleep sessions and awakenings, growth measurements, milestone observations and status, notes, reminders, preferences, and photos or videos attached to developmental moments.
TinyLeap is designed for routine child-care, wellness, growth, development, feeding, sleep, and family records rather than medical records. TinyLeap does not ask you to enter diagnoses, medical conditions, prescriptions, medications, treatment plans, laboratory results, clinical records, HealthKit data, or Clinical Health Records data. Some privacy laws use broader definitions under which particular body measurements, bodily-function records, or derived wellness information may still be treated as sensitive or health-related. Only enter information that you are authorized to provide. You may use a nickname instead of a full legal name where that is sufficient for your needs.
TinyLeap offers a selection of static, ready-made illustrated avatars. Choosing an avatar does not scan a face, perform facial recognition, or create a biometric template.
A profile photo and selected avatar are part of the child profile. They remain local unless you choose to use a TinyLeap cloud feature that includes the profile. If you use TinyLeap iCloud Backup or Family Sync, that profile information may be stored or synchronized through Apple iCloud/CloudKit.
Providing information to TinyLeap is voluntary unless a specific law requires otherwise. There is no general legal obligation to provide child or family information to TinyLeap. If you choose not to provide particular information or permission, the related feature, calculation, personalization, synchronization, report, reminder, or device integration may be unavailable or less useful.
No TinyLeap server or central family database
TinyLeap is designed so that the Operator does not receive or maintain a central copy of the child and family records you create in the app. Core records are processed and stored on your device. TinyLeap does not provide a separate TinyLeap account system for storing these records on an Operator-controlled server.
If you choose TinyLeap iCloud Backup, the app writes the backup to your private Apple CloudKit database. If you choose Family Sync, Apple CloudKit sharing makes selected records available only to Apple accounts included in the share. Apple states that private CloudKit data is not visible in the developer portal and that shared CloudKit data is not visible there or to people who do not have access to the share.
This architecture limits the Operator’s possession of family records, but it does not remove privacy obligations that may apply to the way the app is designed to process information on a user’s behalf. This Policy therefore continues to describe applicable rights and regional protections even where the Operator does not hold a server-side copy of the records.
Why information is processed
Information is processed to provide the features you request, including care tracking, sleep and developmental calculations, growth and milestone records, reminders, exports and reports, profile personalization, family or caregiver features when enabled, and device integrations such as Widgets, Live Activities, Apple Watch, and Siri/App Intents.
Where the GDPR, UK GDPR, or another law requires a legal basis, core processing used to provide a feature you request may rely on performance of the service or steps you request; optional permissions, sharing, and other optional processing may rely on consent; security, fraud prevention, app integrity, and limited operational needs may rely on legitimate interests where permitted; and some processing may be necessary to comply with legal obligations. TinyLeap does not use legitimate interests to override a requirement for consent to process special-category information.
Routine care, growth, development, feeding, sleep, premature-birth, and similar records are not medical records in TinyLeap. Depending on the jurisdiction and the context, however, a particular record may still fall within a statutory category of sensitive, special-category, or consumer-health data. Where explicit consent is required, TinyLeap records a separate in-app consent for the child or family information you choose to enter for the features you request. Withdrawal of consent does not affect processing that was lawful before withdrawal. Because a feature cannot calculate or display information that has been deleted or withheld, withdrawing consent may require deleting the relevant information and stopping use of the related feature, subject to applicable legal retention duties and technical limits.
Local storage, App Group, and backups
Core TinyLeap records are stored locally on your device using Apple platform storage. Limited information may also be copied to TinyLeap’s shared App Group so the app and its authorized extensions can present current information in Widgets, Live Activities, controls, Siri/App Intents, or paired-device features.
TinyLeap iCloud Backup is an optional backup stored in your Apple iCloud account through your private CloudKit database. Automatic backup is off by default on a fresh install. Cloud backup occurs only after an explicit user action, such as enabling Automatic TinyLeap iCloud Backup or choosing a manual Back Up/Sync action. TinyLeap does not copy this backup to a TinyLeap-operated server or central database. Apple states that records in a private CloudKit database belong to and are accessible by that user and are not visible in the developer portal.
Separately, data stored by the app may be included in Apple’s device iCloud Backup or a computer backup depending on your Apple device and backup settings. Apple device backups are controlled by you and Apple and are not the same as TinyLeap iCloud Backup or Family Sync. TinyLeap and the Operator do not control Apple’s independent device-backup process.
Optional Family Sync and caregiver sharing
If you choose to use Family Sync, TinyLeap uses Apple iCloud/CloudKit sharing to synchronize selected family records only between Apple accounts you authorize. Family Sync is separate from TinyLeap iCloud Backup. Depending on the feature, shared data may include child profiles, profile photo or selected avatar, care records, sleep, growth, milestones, notes, caregiver permissions, and milestone media. Shared CloudKit records are available only according to the permissions of the Apple share and are not visible in the developer portal. TinyLeap does not operate a separate application server or central database for this family data.
A caregiver you invite may be able to view, add, change, synchronize, or delete shared information according to the permissions and Apple sharing mechanisms available in the app. You are responsible for inviting only people who are authorized to access the child’s information and for removing access when it is no longer appropriate. TinyLeap and the Operator are not responsible, to the maximum extent permitted by law, for misuse by a person whom a user authorized to receive shared data; this does not reduce any security or privacy duty that the law places on the Operator.
Photos, notifications, Siri, Watch, and other Apple features
When you select photos or videos, TinyLeap uses Apple’s system interfaces to import only the items you choose. Imported media is stored as part of the app’s data and may be stored through Apple CloudKit when you explicitly use TinyLeap iCloud Backup or use Family Sync that includes media. Avatar selection does not use facial recognition or biometric identification.
If you enable notifications, Widgets, Lock Screen features, Live Activities, Apple Watch, Siri, or App Intents, limited care or child information may be displayed on device surfaces or passed through Apple system services as necessary to perform the requested feature. You control many of these permissions and display options in iOS/watchOS settings.
What TinyLeap does not currently do
The current app does not include third-party advertising SDKs, third-party behavioral analytics SDKs, an external generative-AI service, a TinyLeap user-account backend, a central child/family database, or data-broker functionality. TinyLeap does not import HealthKit or Clinical Health Records data. TinyLeap and the Operator do not sell child or family information or share it for third-party targeted advertising.
If data practices change materially, this Policy and the App Store privacy disclosures must be updated before or when the changed processing is introduced, as required by applicable law and Apple rules.
Apple and external services
Apple may independently process App Store, purchase, iCloud/CloudKit, device, diagnostic, backup, Siri, Watch, notification, and related information under Apple’s own agreements and privacy practices. TinyLeap and the Operator do not control Apple’s independent processing. External child-care, development, safety, public-health, or public-information links are controlled by their respective publishers and are subject to their own privacy practices.
Recipients and disclosures
Under the current architecture, TinyLeap does not send child or family records to an Operator-controlled backend. The current recipients relevant to those records are Apple platform services needed for features you choose, such as private or shared iCloud/CloudKit, and caregivers or family participants whom you explicitly authorize. Support or legal correspondence that you send directly to the Operator may be seen by the Operator and, only when genuinely necessary, by professional advisers or service providers engaged for support, security, or legal purposes. If a future provider receives user data on TinyLeap’s behalf, TinyLeap will require privacy and security protection that is the same as or equivalent to the protection described in this Policy, as required by applicable law and Apple rules. Information may also be disclosed where required by law or necessary to establish, exercise, or defend legal rights.
TinyLeap does not disclose child or family information to data brokers or third parties for their targeted advertising. If a new category of recipient or materially different disclosure is introduced, the Privacy Policy and, where required, consent or notice will be updated before that processing begins.
International data transfers
Apple platform services, including private or shared iCloud/CloudKit, backup, purchase, diagnostic, and related services, may process or store information in countries other than the country in which you live under Apple’s own arrangements. The Operator does not maintain a central copy of child or family records and therefore does not independently choose a cross-border hosting location for those records. If the Operator itself receives personal information, for example through support or legal correspondence, and later transfers or makes that Operator-held information available across borders, any transfer regulated by applicable law will use an available lawful mechanism and the safeguards required by that law.
Where Israeli, EEA, UK, or other privacy law regulates a transfer of personal information that is actually held or controlled by the Operator, the Operator will apply the transfer mechanism and safeguards required by that law. Apple’s independent handling of Apple-service data is governed by Apple’s terms and privacy arrangements.
Calculations and automated processing
TinyLeap uses rules and calculations to create sleep windows, summaries, age-adjusted guidance, development timing, growth displays, reminders, and similar app outputs. These outputs are informational and organizational. TinyLeap does not use them to make solely automated decisions that produce legal effects or similarly significant effects about a child or caregiver.
Retention, deletion, and copies
The Operator does not maintain a central server-side copy of child or family records and therefore does not impose a commercial retention period on such a database. Records remain on the device, in an optional private iCloud/CloudKit backup, or in a user-authorized CloudKit share until the user edits, deletes, restores, disables, or stops the relevant feature, subject to Apple’s platform behavior and technical propagation time. Support, privacy, legal, or other correspondence that a user sends directly to the Operator may be retained only for as long as reasonably necessary for the request, security, dispute handling, legal compliance, or another lawful purpose.
When you use Delete Child Data, TinyLeap removes the local family data and requests deletion of the TinyLeap private CloudKit family zone, or leaves the shared CloudKit family when the device is a participant. If CloudKit is temporarily unavailable, the cloud deletion remains pending locally and ordinary TinyLeap cloud synchronization is paused until cleanup succeeds, to reduce the risk that an older cloud snapshot is restored into the empty local store. Keep the app installed until the pending cleanup finishes. Apple device backups, exports, and copies already stored by another authorized person are separate and may require their own deletion or backup rotation; TinyLeap and the Operator do not control copies another user lawfully exported or stored outside systems controlled by the Operator.
You may use the app’s available edit and deletion tools. Requests that must be handled by the Operator under applicable privacy law may also be sent to tinyleapsupport@gmail.com.
Security
TinyLeap uses Apple platform protections and reasonable technical measures appropriate to the app’s architecture, but no device, storage, cloud, synchronization, or communication method can be guaranteed to be completely secure or error-free. Keep devices protected with a passcode or biometric lock, keep system software updated, review Lock Screen and Widget visibility, and control who has physical or shared access.
Children and authority to provide data
TinyLeap is an adult caregiver tool. It is not directed to children for independent use and does not intentionally ask a child to create an account or submit information directly. Adults using TinyLeap are responsible for having the legal or other appropriate authority to enter, store, share, or synchronize information about a child or another caregiver.
A child can be the person the information is about even though the information is entered by an adult. The source of child information in TinyLeap is the parent, legal guardian, or authorized caregiver who enters or shares it, together with calculations TinyLeap performs from those user-entered records. TinyLeap does not collect information directly from a child.
Privacy rights by region
Israel: core child and family records are managed by the user in the app rather than in a central TinyLeap database, and the app provides tools to view, edit, export, and delete those records. If the Operator separately holds personal information about you, for example support or legal correspondence, rights available under Israeli privacy law, including applicable access or correction rights, may be exercised subject to the conditions and exceptions of that law.
EEA and United Kingdom: where the GDPR or UK GDPR applies, you may have rights of access, rectification, erasure, restriction, objection, data portability, withdrawal of consent, and complaint to the competent supervisory authority, subject to the applicable conditions and exceptions. Most child and family records can be handled directly with TinyLeap’s in-app view, edit, export, delete, backup, and sharing controls because the Operator does not keep a central server-side copy. For personal information actually held by the Operator, or for a right that cannot be completed in the app, contact tinyleapsupport@gmail.com. Withdrawal of consent affects future processing and does not undo processing that was lawful before withdrawal.
United States: privacy rights vary by state. Some state laws use a broad definition of consumer health data that can cover routine measurements or information about bodily functions even when an app is not a medical or healthcare service. TinyLeap therefore provides a separate U.S. State Consumer Health Privacy Notice describing the potentially covered categories, purposes, storage and user-directed sharing, and available rights. TinyLeap does not sell child or family information, use it for third-party targeted advertising, or maintain a central child/family database.
Many records can be viewed, corrected, exported, or deleted directly in TinyLeap. For a right that cannot be completed in the app, contact tinyleapsupport@gmail.com. The Operator may need to verify a requester’s identity or authority before acting on a request and may retain information when the law permits or requires it.
Changes and contact
This Policy may be updated when TinyLeap’s features, legal obligations, or data practices change. A material change may use a new policy version and require renewed in-app acknowledgment. The App Store privacy disclosures must be kept consistent with the release configuration.
For privacy questions, support, or requests to exercise privacy rights, contact TinyLeap at tinyleapsupport@gmail.com.