User data
Personal data processing at Rosterama
What data the service uses, why it is needed and how to contact the data controller
Revision dated · Translation updated
This translation is provided for information only. Only the Russian-language version is legally authoritative. In the event of any discrepancy, the Russian-language version prevails. This does not limit any rights that cannot be excluded under applicable law. Russian original
1. Controller and sign-in
1.1. The personal data controller at Rosterama is Individual Entrepreneur Pavel Alekseevich Lysenko, INN 770172764919, OGRNIP 317774600603504. Sign-in uses the OAuth provider name, the user identifier at that provider and the profile name.
2. Data processed
2.1. Data processed includes the account identifier, OAuth profile name, optional public nickname, OAuth profile email if supplied by the provider, and the receipt email chosen by the user. Account-linked session information and Service usage information are also processed. Support inquiries use the contact and other personal information included in the inquiry. For a paid subscription, data also includes user-linked order and transaction identifiers, the amount, currency, time and transaction status, refund and receipt information, the versions of terms presented, authorization for automatic renewal and its cancellation. When Telegram is connected, the user identifier and associated chat identifier are used.
2.2. A roster, image, message or file is not personal data merely because a user submitted it. This policy applies to information about a person contained in those materials and to links between materials and an account where these allow a person to be identified directly or indirectly.
2.3. While automatic renewal is active, Rosterama stores an encrypted payment token and email for receipts for subsequent charges and mandatory subscription notifications. The token identifies a payment method at the payment service and does not contain a full card number or security code.
3. Purposes and parties involved in processing
3.1. Processing serves sign-in and account protection, fulfillment of requests, delivery of results, plan and payment accounting, notifications about forthcoming charges, payment outcomes and refunds, and support. Necessary data is exchanged with the selected OAuth provider, Telegram where used, the payment service and transaction participants identified at checkout, and infrastructure providers.
3.2. For payment, Rosterama sends CLOUDPAYMENTS LLC the account and order identifiers, amount, currency, payment description and selected receipt address if known. The payment service obtains payment credentials directly through its secure form, which also allows the email to be entered or changed. Electronic receipt data is transmitted to the fiscal solution operator, fiscal data operator and Federal Tax Service to the extent required by law.
4. Payment data
4.1. The full card number and security code are entered inside the CloudPayments iframe and sent directly to the payment service. They do not reach Rosterama’s server. The expiry date and masked card details may pass through a provider notification, but Rosterama does not include them in application storage or logs. The OAuth profile email is used as the preselected receipt address. Before payment, it can be changed in Rosterama and saved for future purchases. This choice is stored separately from the original OAuth address and is not overwritten on later sign-in. If no address is known, the CloudPayments form requests it.
4.2. Rosterama verifies payment confirmation on the server. When automatic renewal is explicitly enabled, the verified payment service may send Rosterama a token and email. They are encrypted and used only for agreed future charges, receipts and subscription notifications provided for in the checkout terms. If a verified token or email is unavailable, paid access may be granted, but automatic renewal is not enabled.
4.3. After automatic renewal is disabled, Rosterama stops using and deletes the token and encrypted email for that charge authorization from its operational database. The separate profile email and saved address for new purchases remain account settings. Copies of deleted payment data in isolated backup sets are permanently retired within 30 days. The technical notification queue does not store a copy of the token. This does not delete information that a payment service, cash register operator, fiscal data operator or government agency must retain under law or contract.
5. Cookies and retention
5.1. Cookies and browser storage are used for sessions, drafts and settings. Browser storage may persist after sign-out and can be cleared through the browser’s site settings. If a saved copy of a linked roster contains personal information, deleting the original at a third-party service does not by itself delete information from the copy.
5.2. The analytics choice is saved permanently in the current browser. Signing out does not delete it. The choice can be changed in Analytics settings. A new choice is needed if the saved record is lost or damaged, or changes in processing require new consent. Analytics remains disabled until new permission is granted in these circumstances.
5.3. Information about completed transactions, refunds and fiscal outcomes is retained for five years after the end of the corresponding reporting year, or until an unresolved dispute or other legal requirement is resolved. Evidence of the terms presented and charge authorization is retained during the subscription and for three years after it ends, up to the retention limit of the related mandatory transaction record. Unused quotes without an order are deleted 30 days after expiry. The content of completed technical notifications is cleared after 90 days. Minimal keys, digests and final statuses are retained within the related transaction record’s retention period for idempotency and audit. Conflicting notifications and those requiring reconciliation are retained until the situation is resolved.
6. Analytics
6.1. After separate user permission, Yandex Metrica, including Webvisor session replay, runs on website, editor and account pages. Its purpose is to analyze visits and actions, improve the interface and find technical issues. YANDEX LLC receives and processes this information. Cookie identifiers, IP addresses, device and browser details, visited pages and actions on them may be processed. The analytics script does not load before permission. After registration, confirmation of a Premium purchase, linking a promo code or linking Telegram, only the relevant event name is sent, without an account identifier, order identifier, code or Telegram ID. More about the technology Yandex Metrica.
6.2. Declining analytics does not restrict sign-in, roster recognition or image creation. Permission can be revoked at any time using Analytics settings on public pages. Revocation stops further collection on the website and removes analytics cookies accessible to Rosterama. It does not automatically delete information already sent to Yandex. Questions and deletion requests can be sent to info@rosterama.ru.
6.3. To confirm the choice, Rosterama retains a minimal server record indefinitely, without automatic deletion. It contains a random consent identifier, the decision, the text revision and server time. IP address, User-Agent, profile, OAuth identifiers and roster content are not included in this journal.
6.4. Roster text, file contents, profile, public nickname, the account window and previews are masked from Webvisor. Analytics does not run on OAuth callbacks, administrative or other technical routes, or where the address contains arbitrary parameters. You can also use the Yandex Metrica blocker. It does not replace the choice in Rosterama settings.
7. User publication
7.1. The roster title, labels and optional public nickname may appear on the PNG. The OAuth profile name does not automatically become a public attribution. The User should consider this when publishing or using the bot in a group chat and should not include another person’s personal data or confidential information in a request without a legal basis.
8. User inquiries
8.1. Questions about processing, access, correction, data deletion and consent withdrawal can be sent to info@rosterama.ru. After account deletion, only information necessary for mandatory transaction accounting and justified consideration of contractual claims may be retained for the period needed for those purposes.