Privacy
This page explains the data used by the map, accounts and feedback features.
Accounts and reading
Registration stores your username, display name and a protected password hash, not your plaintext password. Server records may also include your profile, reading statuses, ratings and activity information used for achievements. Profile and library sharing are separate opt-in settings; profiles are private by default.
Cookies and browser storage
Necessary cookies support sign-in and guest identity. Your browser stores language, map preferences and local reading statuses, including changes awaiting synchronisation. Removing server data does not automatically clear copies already stored in your browser.
Site statistics
Our first-party counter measures map startup stages, interactions, book and Webway openings, saved reading marks, donation-link clicks and approximate active browsers. Distinct browsers across 7 and 30 days and calendar weeks and months use another random first-party cookie with a sliding lifetime of up to 31 days, renewed on an eligible analytics event. A separate random daily cookie expires at UTC midnight; its daily hash is not linked to an account. Daily aggregates and short-lived event receipts include a hash of the period identifier; the data is not linked to accounts or IP addresses. Daily statistics, including distinct-browser data, are cleaned up after 90 days, and receipts after two days; these are periods before scheduled cleanup, not hard guarantees. Deleting the cookie may result in a new browser ID. We store device and referral categories, including the search engine, but not full page URLs, search queries, IP addresses or screen recordings. Random event IDs prevent double counting during limited retries; delivery summaries help identify failures. Reports are restricted to an authorised administrator. No analytics cookies are issued and no events are collected when Do Not Track or Global Privacy Control is enabled. Cross-day distinct counts are available only from the start of the new tracking; partial and unavailable periods are marked separately. Account totals and reading data are counted separately. Cloudflare may collect its own technical delivery analytics.
Comments, reports and avatars
Other visitors can see comments and profile information you choose to publish. Avatars are processed and stored as images. Feedback stores its text, page or book context, language, links and contact details you voluntarily supply. Do not submit passwords, payment details or identity documents. Deleting a comment removes its text but can retain a record to preserve replies.
Loading diagnostics
Unless Do Not Track or Global Privacy Control is enabled, the site automatically sends limited technical reports to its own server: a random page-load code, loading stages, browser family and major version, device category, sanitised request categories, HTTP statuses, sizes, timings and error categories. The server correlates these with its response delivery using random request codes. These reports do not record IP addresses, full page URLs, search queries, request or response bodies, cookies, error messages or account data. Only the administrator can access them. Reports are kept for up to 7 days; older records may be removed sooner when storage limits are reached. One unsent copy may temporarily remain in the current tab’s session storage for a retry after reloading, for up to 30 minutes.
Hosting and protection
The site and database run on the project server in the Netherlands; incoming traffic passes through a proxy server in Russia. Cloudflare provides DNS and Turnstile form protection; verification sends a challenge token and the request’s network address. Account data and uploaded images are stored in the project database and object storage. External services, including Telegram, have their own data policies.
Data requests
Use the private Feedback form in the site menu, preferably while signed in, to request access, correction or deletion of account data. A general fixed retention period has not yet been established; automatic deletion after a particular period is not promised. Clear device-local copies separately through your browser’s site-data settings.