Privacy Policy

Effective October 5, 2026

The data controller and owner of Rytmi is its developer, Dmitrii Kurbakov. You can contact the controller through the support form. Rytmi is intended for adults; children do not create separate accounts.

Data we process

• email address, account identifier, and consent date;
• the child's nickname, date of birth, time zone, and selected diary event types;
• feeding, sleep, diaper, measurement, and milestone records, including their time, duration, and notes;
• family roles, invitations, and the author of each entry;
• technical synchronization identifiers, record versions, and the device token used for notifications;
• notification settings: quiet hours, alerts about the other adult's timers, and whether the sleep reminder is on - only yes or no, never the reminder time. We use this answer to count how many families use reminders;
• the platform, app version, build number, operating system version, and interface language of the device you signed in from. We keep this to know when a released version may stop being supported, to offer you an update, and to write notifications and sign-in emails in the app's language;
• anonymous daily counts of first launches, successful sign-in methods, opening the record menu, quick actions, and the daily Pulse report, grouped by platform, app version, and build. These counts contain no account, device, IP address, or diary content; an individual's action history is not stored;
• the email address and message voluntarily submitted through support.

Why we process data

We use this data only to sign adults in, maintain and synchronize the shared diary, provide personalized forecasts and analytics, deliver selected notifications, count how many families use reminders and measure use of released features, export or delete data, and answer support requests. Rytmi does not sell data, display advertising, or use cross-app tracking.

Storage and security

The primary server database is hosted in Russia. Data in transit is protected by HTTPS, the local iPhone database is encrypted, and session tokens are stored in Keychain. Only invited adults can access a diary; the server verifies ownership and the adult's role for each operation.

Apple receives only the credentials or device token needed for sign-in and push notifications, subject to Apple's terms. Transactional sign-in emails are delivered by Unisender Go; diary contents are not shared with that provider.

Retention and deletion

Active data is kept while the account or shared diary exists. Deleting a child profile immediately removes access and sends a deletion marker to connected devices. Deleting an account deactivates it and removes local diary data, sessions, device registrations, and invitations. If Apple sign-in was used, its grant is revoked before deletion.

After deletion, the account email is anonymized within 30 days. Deleted entries and profiles remain inaccessible for up to 90 days only so that a long-offline device cannot recreate them during synchronization; their contents are then irreversibly erased, leaving only a technical deletion marker. Daily server backups rotate within 7 days and are used only for disaster recovery. Deleted data is not restored to an active account from a backup.

Your choices

In the app settings, an adult can export a child's data, delete a child profile, and delete their account. An owner must first delete any child profiles they own so that a family is not left without an owner. For access, correction, export, or deletion questions, use support.

If you are in the European Economic Area or the United Kingdom

The EU General Data Protection Regulation (GDPR) or the UK GDPR applies to how we handle your data. This section adds to the rest of this policy; the controller and how to reach them are named at the top.

Why we may process your data:

• your account, sign-in, the shared diary and its synchronization, invitations, forecasts, export and deletion: to provide the service you asked for (performance of a contract);
• details of the device and app version you use, and the records that keep the service secure: our legitimate interest in keeping Rytmi working, supported and safe;
• support requests: to answer the request you sent.

You can ask us for access to your data, for its correction or deletion, to restrict its processing, and for a copy in a portable format, and you can object to processing based on our legitimate interests. Export and deletion are available in the app's settings; for anything else, write to support and we will answer within one month. You can also complain to the data protection authority where you live or work; in the UK, that is the Information Commissioner's Office.

Rytmi's server is in Russia, and when you use Rytmi you send your data to us there. Neither the European Commission nor the United Kingdom has recognized Russia as providing an adequate level of data protection. Sign-in emails are delivered by Unisender Go and contain no diary records; push notifications and Sign in with Apple go through Apple.

Forecasts and ranges in Rytmi are calculated automatically from your records to help you plan the day. They are not decisions about you and have no legal or similarly significant effect. Rytmi is used by adults: a child has no account, and the adult who keeps the diary provides the child's data.

Changes

An updated policy will be published at this address with a new effective date. Material changes to processing purposes or data categories will be communicated and, where required, will request new consent.

Your optional fixed-category answer about how you heard of Rytmi, or closing the question, is stored with your account so it is not asked again. Reports show aggregate sources; no free text or diary contents are collected by this question.

An optional answer about a break, skipping that question, and a decision about a reminder offer are stored with your account to avoid repeated questions. Only fixed categories are accepted, with no free text. Technical signals for foreground use, a first result, save/sync failures and confirmed crashes are stored as daily totals by platform and version. Error messages, stacks and diary content are not sent.

Web, Telegram and MAX diary

Additional processing information for the web diary and subscriptions is available in the subscription privacy supplement (Russian).