Personal data processing policy

1. General

This policy describes how personal data of users of the Usuba information resource (the “Service”) is processed. The personal data operator is [Owner full name], TIN [TIN]. Document version: 2026-09-27. For questions about processing and about your rights, write to hello.usuba@yandex.ru.

2. Personal data stored on the server

In connection with an account, the operator’s servers may process:

• email address;
• first name, last name, and display name;
• profile image (avatar);
• subscription details: active flag, end date, and how it was connected;
• identifiers of favorite, cooked, and recently viewed recipes;
• folder names, folder contents, and a public link token if a folder is shared;
• cleaned meal plans: title, dates, slots, recipes, servings, grocery budget, and cooking frequency;
• shopping lists and a public link token;
• IP address and User-Agent of sign-in and consent events.

Email, name, and avatar come from Yandex ID sign-in, in the scope the user allowed at the provider. The operator does not request or store a phone number, sex, or date of birth. Anyone with a shopping-list link can open that list and check items without signing in. A published folder opens by its own link.

3. Data that stays on the user’s device

The inputs used to calculate intake (height, weight, date of birth and sex for the calculation, activity, goal), the list of excluded foods, and the encrypted transfer capsule are stored in the browser’s local storage (IndexedDB) on the user’s device. The operator does not receive or store those source values.

4. Transient processing when a plan is generated

To build a meal plan, the client sends the server, for the duration of one HTTP request, a calculated calorie range, neutral selection rules, a meal-structure template, and a flat list of excluded ingredients. Those data are processed in request memory, are not saved in the plan database, are not written to application logs, and are not sent to external AI services. The account keeps the cleaned result: the dish schedule and servings.

5. Purposes

• registering and authenticating the user in the Service;
• providing the account, collection sync, and cleaned plans;
• generating a menu transiently at the user’s request;
• security, abuse prevention, and technical logs;
• complying with the laws of the Russian Federation.

6. Legal bases

Personal data are processed on the basis of the data subject’s consent (Article 6 of Federal Law 152-FZ), including acceptance of the consent to personal data processing at sign-in; performance of the terms of use; and the operator’s legitimate interests in security and stable operation of the Service.

7. Retention

Account data, favorites, cooked recipes, folders, and cleaned plans are kept until the user deletes them or deletes the account, unless the law requires otherwise. Browsing history is at most the last 50 recipes; records older than 90 days are deleted. Shopping lists are deleted with the plan and 30 days after the plan’s last day. Sign-in IP address and User-Agent are kept for 90 days. The consent record, including IP address and User-Agent, is kept until the account is deleted: it is the evidence of consent. Infrastructure logs (Loki) are kept for no more than 168 hours. You can delete the account from the account-deletion page: that also deletes the profile, consent, collections, plans, shopping lists, and remaining sign-in records.

8. Sharing with third parties

For Yandex ID sign-in, profile data are sent to the authorization provider, Yandex LLC, under the OAuth protocol at the user’s initiative. Yandex Metrica and Varioqub are connected only with analytics consent. On intake, plan, exclusion, and shopping screens the counter, click map, and webvisor are not connected. Other transfers are possible only where the law requires them or with a separate consent.

9. Rights of the data subject

• receive information about processing of your personal data;
• require correction, blocking, or deletion of the data;
• delete the account and the related server-side personalization;
• withdraw consent to processing;
• complain about the operator to Roskomnadzor or a court.

Deleting the account does not erase the local vault on the device — the user deletes it separately in the browser or through export and clear in the interface. To exercise your rights, write to hello.usuba@yandex.ru.

10. Cookies and local storage

How cookies, localStorage, and IndexedDB are used is described in the cookie policy.