Privacy Policy
Revision of August 30, 2026.
1. General
1.1. This policy is prepared in accordance with Federal Law No. 152-FZ of July 27, 2006 "On Personal Data" and describes how the Operator processes personal data of website visitors and users of the env-master Service (https://env.aistastudio.ru).
1.2. The data operator is Общество с ограниченной ответственностью «СТУДИЯ АИСТА», OGRN 1267800056260, INN 7814865711, registered office: 197706, г. Санкт-Петербург, вн.тер.г. город Сестрорецк, ул. Всеволода Боброва, д. 30, литера А, помещ. 1-Н, офис 13. Contact for questions, requests and withdrawal of consent: env-master@aistastudio.ru.
1.3. The notification about personal data processing filed with Roskomnadzor (Art. 22 of 152-FZ): уведомление готовится к подаче.
1.4. The policy applies in the revision published on this page; the date of the last change is stated in the heading.
2. Data subjects
The policy covers:
- registered users of the Service — individuals, including those acting on behalf of an organization;
- persons invited to an organization who have not yet accepted the invitation;
- website visitors — as far as processing without registration goes (cookies, support correspondence).
3. Data we process
| Category | Contents | Source |
|---|---|---|
| Account | email address; display name; password — stored only as a non-reversible hash; creation date; email-confirmation flag; public key, if the User set one | the User, at registration and in settings |
| Email confirmation | a one-time link (only its hash is stored), valid for 24 hours | generated by the Service |
| Organization invitations | invited person's email address, role, expiry, acceptance fact | the inviting member |
| Sign-in address history | up to 50 most recent addresses (IP) the account was signed in from | generated by the Service |
| Sessions | refresh tokens — stored only as hashes, with a 30-day lifetime | generated by the Service |
| Audit log | actor, event type, time, address (IP), client type (browser, portal, SDK, CLI, mobile app); for secret operations — key names and an impersonal value fingerprint (HMAC); the values themselves are never recorded | generated by the Service |
| Inquiries and claims | the letter's content, the sender's address, and any other details the sender included | the sender |
| Cookies | see section 9 | generated by the Service |
The Operator does not process special categories of personal data (health, beliefs and the like) or biometric personal data, and storing them in the Service is prohibited.
4. Purposes and legal bases
| Purpose | Data | Basis |
|---|---|---|
| Registration, account maintenance, email confirmation, organization invitations | account data; confirmation data; invitations | consent (para. 1 part 1 art. 6 of 152-FZ); performance of the Service agreement to which the subject is a party (para. 5 part 1 art. 6 of 152-FZ) |
| Providing access to the Service, keeping the organization's audit log, tracing the sequence of actions | audit log; sessions | performance of the Service agreement (para. 5 part 1 art. 6 of 152-FZ) |
| Security: rate limiting, sign-in from a new address, detection of a stolen token being reused, blocking violators | addresses (IP); client type; sign-in address history; block records | the Operator's legitimate interests and security obligations (para. 7 part 1 art. 6 of 152-FZ) |
| Communication: email-confirmation and invitation letters, answers to inquiries, claims work | email address; inquiry content | performance of the agreement (para. 5 part 1 art. 6 of 152-FZ); consent |
| Compliance with the law and requests from authorized bodies | the volume required by the request | legal obligations (para. 3 part 1 art. 6 of 152-FZ) |
5. Retention
- account data — while the account exists; after account deletion — for the periods below;
- one-time confirmation links and invitations — until expiry (24 hours for a confirmation link; the invitation expiry is set by the inviter) or until used;
- session refresh tokens — the 30-day token lifetime; revoked and expired tokens are kept for up to 30 more days so the log can still show a token being used after its death;
- audit log — for as long as the organization exists; there is no scheduled deletion. Log events are linked into a chain in which every record vouches for the previous one: deleting part of the events breaks the chain and strips the log of its evidential value — the very property it is kept for. The plans state how far back the log is shown in the interface (7 days, 90 days, 1 year); that is display depth, not a retention period. The log is deleted together with the organization;
- sign-in address history — no more than the 50 most recent addresses per account;
- webhook delivery records — 30 days;
- database backups — daily, each copy kept for 14 days; secret values remain encrypted in backups;
- inquiries and claims — 6 months from the moment the inquiry is closed.
6. Storage and location
6.1. Data is processed by the Operator's automated means and stored on servers located in the Russian Federation. Cross-border transfer of personal data does not take place.
6.2. Access to data is granted to the Operator's personnel involved in operating the Service and maintaining its security, to the extent necessary for their tasks.
7. Disclosure to third parties
7.1. The Operator does not sell and does not disclose personal data to third parties, except:
- Service letters (email confirmation, invitations, notifications) are sent through VK Workspace (Mail.ru), operated by OOO «VK Digital Technologies», OGRN 5177746017158, address: 125167, Moscow, Leningradsky prospekt 39, bldg. 79, floor 17. It receives the recipient's email address and the letter's text;
- the Operator's servers are housed in the IXcellerate Moscow Five (MOS5) data centre, Moscow, Southern Administrative District, operated by OOO «Oblachnye Tekhnologii», OGRN 5167746080057, address: 123100, Moscow, Presnensky municipal district, 2-ya Zvenigorodskaya st. 28. The equipment is housed physically; the data centre operator is given no access to the contents of the databases;
- if a web-analytics counter is enabled on the website, de-identified information about visits to the marketing pages (IP address, page address, browser data, actions on the page) is passed to Yandex LLC, OGRN 1027700229193, address: 16 Lva Tolstogo St., Moscow, 119021 — the Yandex.Metrica service. The transfer happens only after the visitor's explicit consent and only on pages outside the cabinet;
- authorized state bodies, as prescribed by law.
7.2. In each case the disclosure is limited to the volume necessary for the corresponding purpose.
7.3. The values a User stores inside the Service as secrets are not processed by the Operator for its own purposes and are not disclosed to third parties; responsibility for the lawfulness of storing them lies with the User.
8. Rights of the data subject
8.1. The data subject has the right:
- to receive information about the processing of their personal data and a copy of it (art. 14 of 152-FZ);
- to demand correction, blocking or erasure of data that is incomplete, outdated, inaccurate or processed unlawfully;
- to withdraw consent to processing;
- to challenge the Operator's actions before Roskomnadzor or a court.
8.2. How to make a request: send it to env-master@aistastudio.ru from the account's email address, or by letter to the Operator's registered office. The request should identify the subject (normally the account's email address) and state its substance.
8.3. The answer is sent within ten working days of receipt; where necessary the term is extended by no more than five working days with notice to the applicant, within the limits set by 152-FZ.
8.4. Withdrawal of consent does not deprive the Operator of the right to process data where processing is required or permitted by law; before deletion the Service stops processing based on consent.
8.5. An account and all data associated with it are deleted on request sent to privacy@aistastudio.ru from the email address stated in the account. Deletion is carried out within no more than 30 calendar days of the request being received.
Deleted are: the account; organizations in which the User is the sole owner, together with their projects, environments, secret values, machine identities and logs; sessions; sign-in address history. Organizations with other members are not deleted — the User's membership and project roles are removed from them.
What is deleted cannot be restored: secret values go along with the data keys of their environments. Backups taken before the deletion are kept for up to 14 more days and are then destroyed on the general schedule; during that period the data exists only in encrypted form and is not used to serve requests.
9. Cookies
9.1. Strictly necessary cookies, without which the Service cannot work:
- the cabinet session — an httpOnly cookie holding the API access tokens; inaccessible to browser code;
- the selected interface language;
- the selected organization and project in the cabinet.
9.2. Advertising cookies are not used.
9.3. Analytics cookies (Yandex.Metrica) are used only if the counter is enabled on this website, and only after the visitor's explicit consent. Before consent the counter script is not loaded, no cookies are set and nothing is sent anywhere; silence does not count as consent. Consent is given with the “Accept all” button in the storage notice and withdrawn in the same place — the “Cookie settings” link in the site footer reopens that notice. Withdrawal stops collection going forward.
9.4. The counter does not run in the cabinet: its page addresses contain the names of the User's projects and environments, and passing those to a third party for analytics purposes is not performed.
9.5. Cookies can be deleted or blocked in the browser; the cabinet will stop working as a result.
10. Changes to the policy
The Operator may change the policy. A new revision is published on this page with the date in the heading. A substantial change of processing purposes is accompanied by obtaining a new consent where it is required.