UpToDoPrivacy Notice
How UpToDo processes account and shared-space data.
1. Controller and contact
The controller is Савельев Денис Александрович, a self-employed provider based in Moscow, Russian Federation. For data requests, use the contact form or support@uptodo.space.
2. Data we process
For accounts: name, email address (older accounts may also retain a previous username), selected avatar, language, time zone and a protected password-derived value. For spaces: name, members, roles, permissions and invitations. For plans: events, reminders, suggestions, goals, notes, participants and change history. For security: a session cookie, active-device information and technical logs. If push is enabled, we also process a device subscription endpoint, technical keys and delivery settings.
Free text may include information users enter themselves. The browser stores some data and app files for offline use; clearing site data removes this local copy.
If you choose Yandex, VK, Mail or OK sign-in, we receive a profile identifier and name. The provider processes sign-in under its own rules.
We record terms acceptance and privacy acknowledgement dates, document versions and registration method.
Necessary cookies support registration, sign-in and sessions. They are set automatically when these features are used; no separate checkbox is required. Analytics can be disabled in Cookie settings; a saved opt-out is respected on welcome and in the demo.
On the public welcome and demo pages, Yandex Metrica (tag 113600581) is enabled by default and uses cookies and technical identifiers, IP address, browser and device information, visits, selected actions and error categories to analyse and improve the service. Session Replay runs on the public /welcome/ and /demo/ pages; forms and demo plan content are hidden. Replay is disabled inside accounts; analytics events contain no names, email addresses, plan or note text, passwords or tokens. Collection is disabled for accounts marked as children. The recipient is YANDEX LLC, Yandex Metrica, under its service terms. Change your choice using Cookie settings on the public page, sign-in form or account settings. Declining does not restrict the service. Read the cookies and analytics or use the Metrica opt-out tool.
3. Purposes and legal bases
Account and space data is needed to create profiles, sign users in, display and synchronise plans, invitations and suggestions. For users in Russia, the basis for core processing is performance of the service agreement (Article 6(1)(5) of Federal Law No. 152-FZ); where the GDPR applies, it is performance of a contract (Article 6(1)(b)). Session and technical data help protect accounts and the service on the basis of the provider’s legitimate interests, subject to users’ rights (Article 6(1)(7) of Law No. 152-FZ; Article 6(1)(f) GDPR). Users enable push notifications separately and may withdraw device permission in browser settings. Where consent is required for notification processing, Article 6(1)(a) GDPR or the relevant Russian-law basis applies.
We do not currently send promotional email.
5. Location and retention
The main database and server backups are on a Selectel server in Russia. An additional encrypted copy is stored on the controller’s computer. Account and plan data is retained while in use. Adults may request deletion in account security settings. Sessions, invitations, push and subscription renewal stop immediately. You have 72 hours to sign in and explicitly cancel; signing in alone does not cancel deletion. The profile and personal records are then removed automatically. Cancellation does not resume subscription renewal.
Owners must complete a transfer to another active adult first. If there is no eligible recipient, deletion of your owned spaces and their data requires separate confirmation. Other members keep their accounts. Shared records belonging to remaining members retain their data without the deleted account identifier; free text is reviewed separately on request. Separate contact requests are retained as needed to handle them and are not automatically deleted with an account. Sessions last up to 30 days; invitations last up to 24 hours and are single use.
Minimal test-payment records remain without the account profile. Local copies on other devices and exported files must be cleared separately.
Temporary incomplete-registration details are used for 30 minutes and then cleared; cancellation removes them.
The contact and text of a closed support request are removed from the working database 30 days after closure. Its number, status and dates remain without the content. The security event log is retained for up to 30 days.
A separate data archive is created daily. The server retains the two latest versions and the controller’s computer retains one verified version; the previous copy is replaced only after the new one passes verification. While disconnected, the older version remains until the next successful download. New archives reflect permanent account deletion and support cleanup; an existing encrypted archive remains until replacement. Retaining an older archive does not cancel an erasure request.
6. Children’s data
A space may include an account designated for a child. The adult creating or inviting the account is responsible for having the necessary authority and setting access. Do not enter sensitive information about children in the test service. A legal guardian may send a data request to the controller’s contact address.
7. Users in Russia and the EEA
Data of Russian citizens is initially recorded in a database on a server in Russia. When the service is used from the EEA, data is transferred to the server in Russia.
8. Your rights and requests
Depending on applicable law, you may request access, correction, erasure, restriction, data portability, object to processing or withdraw consent for an optional feature. Send requests through the contact form; identity verification may be needed to protect the account. You may also complain to the competent supervisory authority, including Roskomnadzor or the data protection authority in the relevant EEA country.
9. Changes to this notice
The effective date appears above. Material changes in data categories, purposes or recipients will be reflected here before they apply; separate consent will be requested where required by law.
Payments and consent history
To manage subscriptions we process the account ID, verified email, plan, period, amounts, invoice IDs and payment statuses, consent and withdrawal timestamps, the offer version and consent text. For recurring payments we retain the initial Robokassa invoice ID. Robokassa processes card details; UpToDo does not store the full card number or security code. Email is used to notify you before renewal.
Processing is based on the contract, applicable recordkeeping obligations and separate consent where required. Consent history is retained for up to three years after the contract ends, unless a longer mandatory recordkeeping period applies. When the account is deleted, payment and consent records use a de-identified reference without the account profile. You can stop future charges on the subscription management page without deleting your account.