Tanya Pescada
<<<
TuaDao — Legal

Privacy Policy for “Chapters About You”

Effective date: August 17, 2026

Russian localization: “Главы о тебе”
International brand: TuaDao
Developer: Tatiana Dobrynina
Creative brand: Tanya Pescada
Contact: info@tanyapescada.com

This Privacy Policy explains how the TuaDao mobile application (Russian localization — “Главы о тебе”) processes user data and the content that the user adds to the application. Hereinafter, the “Application”.

In brief about the current version 1.0: entries, photographs, and information about the child are processed only on the user’s device. The Application does not send them to the developer and does not use accounts, cloud synchronization, analytics, advertising, or artificial intelligence services.

1. Data processed by the Application

The user may independently add to the Application information and materials related to keeping a personal record of a child’s life, including:

These data are used only to provide the functions of the Application.

The current version of the Application does not use advertising SDKs, advertising identifiers, user behavior analytics, cross-site or cross-application tracking, automated decision-making, or profiling.

2. Where data are stored

The contents of the record are stored locally on the user’s device.

The developer does not receive the contents of the record, does not store them on its servers, and does not have remote access to the user’s entries or photographs.

The current version of the Application does not require creation of a user account or cloud storage in order to keep the record.

The Application and the software components included in it do not send the contents of the record to the developer or to providers of such components. This statement applies to the current version 1.0 and does not include transmission of a file that the user initiates through the system save, print, or share menu.

3. Photographs and metadata

Photographs selected by the user for inclusion in the record are processed on the device.

The Application creates a local copy of the selected image, re-encodes it, and removes embedded metadata from the saved copy, including EXIF data, available GPS coordinates, and information about the device used to take the photograph. If the image cannot be processed safely, it is not added to the record.

The original photograph in the user’s gallery is not changed or deleted by the Application.

The developer does not receive photographs added by the user to the record.

4. Access protection

The Application may use a PIN code, the device’s biometric authentication, and a recovery code to protect access to data and backups.

Biometric verification is performed by the device operating system. The Application does not receive or store the user’s biometric templates; it receives only the verification result.

Data required to protect and restore access are stored separately from the contents of the record using secure storage mechanisms provided by the device operating system.

In the current version of the Application, the developer does not receive the user’s PIN code or recovery code and cannot provide or restore them upon request.

5. Backups and export

The user may independently create backups and export the contents of the record, for example as a PDF.

Such files are created at the user’s request. The user independently chooses where to save them and how to transmit them further.

If the user saves or transmits a file through a third-party service — for example, cloud storage, a messenger, an email application, or another service — further processing of that file is governed by the terms and privacy policy of the selected service.

In the current version of the Application, the developer does not automatically receive backups or exported files created by the user.

6. Disclosure of data to third parties

In the current version, the Application does not transmit the contents of the record to the developer or to third parties without a separate action by the user. It does not include cloud synchronization, remote backup, analytics, advertising, or transmission of data to artificial intelligence services.

User files may be transmitted to a third party only when the user independently chooses the relevant system function or third-party application to save, print, or send the file.

7. Data retention and deletion

The contents of the record are stored on the device until the user independently deletes individual data, all local Application data, or the Application itself.

All local record data can be deleted in the Application: Settings → Data → Delete family book. Deletion is irreversible if the user has not created a backup in advance.

The developer cannot remotely delete local data because it does not receive them and does not have access to the user’s device.

Files that the user previously saved outside the Application’s internal storage, including backups and exported documents, remain under the user’s control and must be deleted separately by the user.

Permissions to access selected photographs, the camera, or biometric verification can be changed or withdrawn in the device system settings. Withdrawing a permission may make the corresponding function unavailable, but it does not transmit previously stored local data to the developer.

8. Children

The Application is intended for parents and other adult users who keep a personal record about a child.

The Application is not intended for independent use by children.

The adult user independently determines what information about the child to add and must have a lawful right or other appropriate legal basis to store and use photographs and information about the child and other persons depicted.

9. Changes to the Application and this Policy

The functions of the Application may evolve and change. Future versions may include, for example, accounts, access recovery by email, cloud synchronization or storage, crash reporting, analytics, artificial intelligence functions, or payments. These features are not part of the current version 1.0.

Changes to the interface, section structure, prompt content, or other functions that do not change the ways in which data are processed do not, by themselves, require changes to this Policy.

Before enabling a function that sends data outside the device, this Policy and the information in application stores will be updated. The user will be provided with clear information about the identity and contact details of the party responsible for processing (including an address where required), categories of data, purposes and legal bases, recipients and processors, countries of processing or transfer, retention periods, deletion methods, and applicable rights. Where required, the Application will separately request the user’s consent before such processing begins.

If accounts are introduced, account deletion from within the Application and a public page for requesting deletion will be provided in accordance with applicable store requirements and law. Before personal data are transmitted to a third-party artificial intelligence service, a separate notice will be shown and explicit permission will be requested if such transmission is implemented.

A general provision about future changes does not mean that the user has given advance consent to future collection, cloud storage, analytics, advertising, or disclosure of data to third parties.

The current version of this Policy is published at a permanent public link and is available from the Application. In the event of material changes, the user will be shown a notice before they take effect where required by applicable law.

10. Contact

Because the contents of the current version are stored only on the device and are not accessible to the developer, the user manages access, correction, export, and deletion of such contents directly in the Application.

For privacy questions or to exercise applicable rights in relation to data that may be processed by the developer in future versions:

Tatiana Dobrynina / Tanya Pescada
info@tanyapescada.com