Personal data processing policy
English translation of the Russian document. Both versions describe the same processing and consent terms.
Updated 18 October 2026 · version 2026-10-18-v1
1. Data controller and contact details
The data controller for sfprod.dev is Meda Sibiri LLC (ООО «Меда Сибири»), Taxpayer ID (INN) 7017484257, State Registration Number (OGRN) 1217000004066. Address: office 21, building 2, 161b Altayskaya Street, Tomsk, Tomsk Region, 634021, Russia. For questions about processing, correction or deletion, or to withdraw consent, contact: 1@meadrf.ru. Use the subject “Personal data sfprod.dev” and include your request number if you know it.
2. What data we process and why
When you contact us through the form, the controller receives your email address, the nickname of an existing game account, its internal ID, topic, messages, game version and request time. The data is used only to handle your request, provide support, respond and maintain the conversation. Nicknames are checked against registered accounts. This does not verify that the sender owns the account; account-related actions may require separate verification.
The date, version and source of your separate consent are stored with the request. The request’s IP address is processed to limit abuse; the feedback database stores a hash with a server-side salt. The server also processes technical HTTP request information when establishing a connection. Do not send passwords, payment details, identity documents, health information or anyone else’s personal data.
3. Legal basis and processing activities
The basis for processing form data is your separate, voluntary consent before submission. Visiting the site alone is not consent. Processing includes collection, recording, organisation, accumulation, storage, correction, retrieval, use to handle the request, access restriction, deletion and destruction. Processing is automated and carried out by authorised staff. Your email address is not used for marketing. This form does not send automatic email replies: replies appear in your conversation on the site.
4. Storage and access
Conversations are stored in the server admin panel’s private database. Only authorised staff can access them. Data is transmitted over HTTPS. Requests are not published or shared with other visitors. The CAPTCHA runs on our server and does not send data to a third-party CAPTCHA service.
The current website and feedback database server is hosted in Germany by Play2Go. Stating its location describes the actual infrastructure and does not confirm that the controller has met legal requirements for data localisation or cross-border transfers.
Requests are kept in the working database for no more than one year after the last message, or until the processing purpose ends or consent is withdrawn, unless an independent legal basis requires longer retention. Expired records are removed when the service starts and during operation. Access to backups is restricted; deletion requests also apply to any later restoration from backups.
5. Browser data and CAPTCHA
A random access key and conversation number are stored in your browser’s localStorage. Your email address and messages are not stored there. The key lets you read replies on this device; do not share it. Clearing browser data removes your access to the conversation but does not delete it from the server. The CAPTCHA code is single-use, expires after five minutes and is tied to your browser key. Rate-limit records are removed as they expire.
6. Your rights
You may request information about processing, correction, restriction or deletion, or withdraw consent by emailing 1@meadrf.ru or by writing in your conversation on this site. The controller may request proportionate evidence linking you to the request to protect it from disclosure to others. Requests are handled within the periods set by applicable law. After consent is withdrawn, processing stops and the data is deleted unless an independent legal basis permits continued processing. You may also contact Roskomnadzor or seek a remedy in court.
7. Updates to these documents
The current version is available on this page. If the consent text changes, the site will request separate confirmation before you send another message. Read the consent text on a separate page.