Privacy and personal data

1. Controller and contact

The controller of wopblockstudio.ru is Храпов Андрей Алексеевич (Woparh). The public contact for personal data matters is support@wopblockstudio.ru. Include your username or account email and the nature of your request. Do not send passwords, emailed codes or secret keys.

2. Registration, sign-in and security

Account data includes username, email, password hash, registration date, email verification and last sign-in details. The site records the document version and acknowledgement time at registration. Passwords are checked against hashes rather than stored as plaintext account fields.

Sign-in and email verification create a record with a one-time code hash, purpose, request IP, attempt count and creation, expiry and use times. Codes are valid for 10 minutes. Device records contain the session identifier, IP address, browser string and first and last seen times.

3. Public profile

Your username, role prefix, avatar, banner, registration date and any biography, status, city or social links you provide may appear in your public profile and member cards. Available activity, profile-view, friend and follow counts also appear there. Account email and device IP are not public profile fields. Do not put information you want to keep private in public fields.

4. Activity and views

An authenticated browser sends periodic activity signals while the page is visible. The server records last seen and accumulated active time and updates device details. This is not a recording of every mouse action or screen content.

Tools keep aggregate visit counts and per-account counts for signed-in users; part of a guest's personal count is stored in the session. Profile visits are counted at most once per visitor per day. Deduplication uses an HMAC key derived from the profile, date and user identifier or a guest's IP and browser string. That table does not store raw IPs or browser strings. The key is a pseudonymised technical record, not a promise of complete anonymity.

News records include page openings and, when a signed-in member reacts, a link between the like and the account.

5. Friends, follows, reports and notifications

The site stores the parties and status of friend requests, follows, blocks, action dates, report text and report status. Notifications include recipient, event type, title, body, link, time and read status. Notification preferences, selected sound, volume and news subscription preference are linked to the account. Reports are intended for administrator review, not public display.

6. Avatars, banners and Minecraft skins

Uploaded images are processed on the server: an avatar or banner receives a generated filename, is resized to supported dimensions and saved as WebP. The resulting image is used in the profile and member cards. Selecting a head by nickname makes the server contact Mojang/Minecraft services with the supplied game nickname and retrieve skin details. You can choose a preset or upload a PNG skin instead.

7. Tool data

Font conversion and construction geometry run in the browser. Saved construction projects and favourite styles use device-local browser storage rather than cloud storage. Page requests and visit counts are still processed by the server. Some command editors send generation parameters to the site's server. Do not put passwords or other people's confidential information in tool names, descriptions or other input fields.

8. External services

Cloudflare Turnstile checks registration and sign-in and receives browser signals, including IP and User-Agent, under its own policy. It is an external service; a claim that data never leaves this site would not cover it.

Google, Discord and Telegram linking starts with your action. WBS stores the verified external account identifier and link dates; it does not request its password. Current handlers use OpenID or identify rather than access to private messages. Unlinking removes the WBS connection; permissions at the external service may need to be revoked separately.

Hosting and email infrastructure provide storage, technical processing and email delivery. Following a social link or writing to an external mailbox is also subject to that service's rules. The site does not guarantee that every external provider processes data in a single country.

9. Purposes and conditions

Data supports requested account and site functions, access checks, the public profile you configure, social actions you initiate, notifications, handling requests and preventing abuse. Processing that requires consent relies on separately expressed consent; merely reading this page is not blanket permission for all processing. Security emails and an optional news subscription serve different purposes.

10. Retention and deletion

Retention depends on the record's purpose: profiles and relationships support the account, sessions support sign-in, and security history supports access and incident checks. A code's ten-minute expiry does not automatically erase the request record. Session expiry is not a retention period for every device record.

Blocking an account or displaying a deleted-account label does not mean all personal data has been destroyed. Send correction, access-copy or deletion requests to support@wopblockstudio.ru. The controller considers continued necessity, applicable obligations and the ability to stop processing. Backups and technical logs are handled separately from the public profile; instant erasure of every copy is not promised.

11. Managing your information

You can edit public profile fields, cancel a follow or request, remove a friendship, change notifications, unlink external identities and revoke an available device session. Write to support@wopblockstudio.ru for data access, correction, stopping processing or withdrawing consent. Proportionate account-ownership checks may be needed; do not send passwords or one-time codes. Responses and actions follow applicable legal requirements.

12. Access, protection and changes

Public pages are available to visitors; security information and reports are intended for the account owner and authorised administration as appropriate to the feature. HTTPS, password hashing, session checks and form protection are used. No internet system provides an absolute security guarantee. Material changes in processing are reflected on this page; an update notice does not replace new consent where required.

Administrative audit records may contain an account identifier, time, acting administrator and a description of a role change, restriction or other operation. These records support decision review and abuse protection and are not displayed on public profiles.

13. Yandex Metrica

We use Yandex Metrica to count visits to public pages. The service may use cookies and process technical information about your browser, device and visit. Session recording is disabled. The counter is excluded from sign-in, the private account area and administration.

A separate short-term WopBlockStudio counter records a view after an interaction with a page. It stores the page path, time, and a random event identifier for up to 31 minutes.