TriarDo Privacy Policy
and Data Processing

Version of 16 October 2026

This is an English translation provided for convenience. In case of any discrepancy, the Russian version at triard.tech/privacy prevails.

1. General Provisions

1.1. This Policy describes how information is processed when you use the TriarDo mobile application and the triard.tech website.

1.2. TriarDo is owned by, and its rights holder is:

Georgiy Vladimirovich Fedorov

an individual applying the special tax regime “Professional Income Tax” (self-employed)

Taxpayer ID (INN): 503239280388

City: Moscow

E-mail: TRIARDD@yandex.com

Website: triard.tech

Hereinafter the “Rights Holder”.

1.3. TriarDo is designed on the principle of data minimization.

To create an account, the User does not need to provide:


2. TriarDo Account

2.1. To create an account, the User chooses a unique pseudonym (account name).

Example: StoneSnake

2.2. The User does not have to use their real name or other information that identifies them as the account name.

2.3. For the account to work, the TriarDo server may store:

2.4. The User’s password is not stored in plain text.

2.5. The recovery code is not stored in plain text on the server.

2.6. When the User signs in, the server issues a session token to the app. The server stores only the token hash, the account’s internal identifier, and the session creation and expiry times. Expired sessions are deleted automatically; signing out ends the session.

2.6.1. For signing in on the website with a code from the app, the server stores a hash of the one-time code, the account’s internal identifier and its validity time. The code is valid for 5 minutes, works once and is then deleted.

2.7. To make a payment, the app may receive a random technical identifier and access token that are not tied to the device. They contain no information about the device, its model or location.


3. Recovery Code

3.1. When an account is created, TriarDo may give the User a unique recovery code.

3.2. The recovery code is used to restore access to the account if the password is lost.

3.3. The User is responsible for keeping the recovery code in a safe place.

3.4. The Rights Holder does not request an email address or phone number for account recovery.

3.5. If the User has lost both the password and the recovery code, it may be technically impossible to restore access to the account.


4. Local Storage of User Content

4.1. The following content created by the User:

is stored only on the User’s device.

4.2. This content is not sent to the TriarDo server.

4.3. The Rights Holder:

4.4. The User controls the information they store locally in the application.

4.5. Sign-in with a fingerprint or other biometrics is performed by the Android system. TriarDo receives only the result of the check and does not receive biometric data.

4.6. Reminders and notifications are created on the device and are not sent to the server.


5. No Synchronization of User Content

5.1. Signing in to one TriarDo account on several devices gives access to the subscription status and the corresponding paid functionality.

5.2. User content is not automatically synchronized between devices.

For example, a task created on one device does not automatically appear on another device.

5.3. Each device has its own separate local storage of user content.


6. Analytics and Advertising

6.1. The TriarDo mobile application does not use built-in advertising or analytics systems to track the User’s actions.

6.2. The Rights Holder does not build an advertising profile of the User based on their use of the application.

6.3. The contents of tasks, projects, habits and notes are not used for analytics.


7. Subscription Information

7.1. To provide one subscription on several devices, TriarDo stores the subscription status on the server.

This information may include:

7.2. This information is used solely to provide and control access to the paid functionality of TriarDo, to perform the agreement, to process refunds and to prevent errors.


8. Payments

8.1. The subscription may be paid for through the Robokassa payment service.

8.2. The User enters bank details directly in the payment infrastructure of that service.

8.3. TriarDo does not store:

8.4. TriarDo may receive from the payment system the technical information needed to confirm a payment, for example:

8.5. The Rights Holder aims not to request from the payment service any information about the User that is not needed to perform the agreement.

8.6. Robokassa receives the order number, amount and plan name, including for issuing a receipt. The pseudonym and other account data are not sent to Robokassa.

8.7. Card data, as well as an email address or phone number if the User provides them to receive a receipt, are processed by Robokassa in accordance with its own documents. The income receipt is registered with the Federal Tax Service of Russia through the “My Tax” (Moi Nalog) application.


9. Server Infrastructure

9.1. TriarDo’s server infrastructure is located in the Russian Federation, in Moscow.

9.2. The user content listed in Section 4 of this Policy is not sent to the TriarDo server.

9.3. Data exchanged between the app, the website and the server is protected by HTTPS (TLS).

9.4. The web server keeps technical request logs: IP address, time and address of the request, response code, and browser or app information. The logs are used to protect against attacks and to fix failures, are not linked to the account and are deleted automatically within 14 days.

9.5. To protect against data loss, the server creates a daily backup of the database of accounts and payments. No more than the three most recent copies are kept.


10. Personal Data

10.1. TriarDo does not require the User to provide information specifically intended to establish their identity.

10.2. The User chooses the pseudonym.

10.3. The User is advised not to use as a pseudonym:

10.4. If information technically processed by TriarDo is, in a particular case, classified as personal data under the laws of the Russian Federation, it is processed in accordance with the applicable requirements of the laws of the Russian Federation.


11. Account Security

The Rights Holder takes reasonable technical and organizational measures to protect server information from:

The User is responsible for keeping safe:


12. Account Deletion

12.1. The User may delete the account directly in the TriarDo application (More → Account → Delete account) or on the page triard.tech/delete-account.

12.2. After the account is deleted:

12.3. Before deleting the account, the User is advised to check the active subscription and turn off automatic renewal if it is on.

12.4. Deleting the account does not necessarily delete local tasks, notes and other materials from a particular device.

12.5. The User may delete local data using TriarDo or the operating system.

12.6. If the User has lost both the password and the recovery code, they may send a deletion request to TRIARDD@yandex.com. How account ownership is confirmed is described on the page triard.tech/delete-account.


13. Uninstalling the Application

13.1. Uninstalling TriarDo from a device may delete local tasks, projects, habits and notes.

13.2. The Rights Holder cannot restore these materials from the server, because no server copy of them is made.

13.3. The User is advised to use the export or backup functions, if the relevant version of the application provides them.


14. Changes in Architecture

If in the future TriarDo starts using:

this Policy must be updated before such processing begins.


15. Changes to the Policy

The current version of this Policy is published at:

triard.tech/privacy


16. Contacts

For questions about TriarDo:

Georgiy Vladimirovich Fedorov

Taxpayer ID (INN): 503239280388

City: Moscow

E-mail: TRIARDD@yandex.com

Website: triard.tech