Data processing and cookies
1. Document status
This information notice describes version 2.0 of the site and its editor. It does not provide the owner’s name, address or contact details because those details were not supplied for publication. It is therefore not presented as an exhaustive privacy policy for an identified data controller. It does not limit data subjects’ rights or release the owner from obligations under Russian Federal Law No. 152-FZ.
2. Reading the site
No registration is required to read articles. The site receives technical HTTP request data needed to respond, including a network address, requested path and headers supplied by the browser. Availability and detail depend on the proxy and server configuration. The site’s own code embeds no advertising pixels, third-party analytics or external fonts. Following an external link transfers further interaction to that resource.
3. Local storage and language
Browser localStorage retains the selected language (ufa-lang), theme (ufa-theme) and saved article identifiers (ufa-saved). These remain until removed by the user or browser. The ufa_lang cookie stores a language code for up to one year and helps select a language version. Saved articles are not transmitted into a separate reader account.
4. Editorial access
Only an authorised editor can sign in. The password is stored as a cryptographic derived value with an individual salt, not as plaintext. The ufa_session cookie contains a random session identifier valid for up to 12 hours; its server record stores a hash, a request-protection token and an expiry time. Sign-out and password changes terminate the relevant sessions. Expired records are removed during login maintenance and application startup.
5. Login protection and logs
A network address, failed-attempt count and restriction period may be processed temporarily to limit repeated failed logins. Expired records are cleared at startup; a given address’s record is also replaced on subsequent attempts and deleted on successful login. Application and proxy logs may contain technical request information. Actual log retention depends on the server owner’s configuration; this notice does not invent a retention period.
6. Articles and images
Editors submit texts, translations and images, which become available to readers after publication. Editors must have lawful grounds for processing and publishing personal information and images. Photographs are stored in original quality and may retain source metadata, including capture location. If that information must not be disclosed, editors must remove it before uploading. Removing an image from an article does not automatically remove its file or old direct URL; physical deletion requires a separate owner action.
7. Storage controls
Users can remove site data and cookies in browser settings. This resets language, theme, saved articles and the login session, but does not itself delete published material, server logs or backups. Blocking local storage may prevent settings from being retained. Removing public material and handling data-subject requests require lawful action by the owner.
8. Owner obligations
A complete privacy policy requires identification of the controller, processing purposes and grounds, recipients, actual retention periods, rights procedures and other required information. Depending on actual processing, notification, localisation, international transfers and consent requirements must also be assessed. This notice does not certify that those duties have been fulfilled.