Privacy

Reading position

The reader keeps only the book's identifier and page number in your browser (localStorage); nothing is sent to the server. Clear them with the „Clear saved position" button in the reader.

How downloads are counted

„Unique downloads": with consent, the server stores a random identifier in a cookie (lekari_vid, 12 months). The database keeps only a keyed hash (HMAC-SHA256) of the identifier, the book and the first-download date; a unique index prevents one browser from being counted twice for a single book. Records are deleted automatically after 730 days.

Total downloads and reader opens are kept only as aggregated daily counts per book — no identifier, including for visitors without consent. Partial (byte-range) requests, searches, page renders and browser prefetches are not counted.

Limitations:

• People are not counted: different devices and browsers of the same person are counted separately.
• If the cookies are cleared, the browser may be counted again.
• Visitors who declined measurement are not included in the unique-downloads figure.
• A download request does not prove that the file was fully received or read.
• Opening the reader does not mean reading to the end; it is counted once per book within a single browser tab.
• Bot filtering (by User-Agent) is not perfect.
• Direct links to the PDF file bypass counting — only downloads through the „Download PDF" button are counted.

For abuse protection the IP address is used only as a keyed hash in counters that last up to 2 minutes and is not stored. Administrator activity can be excluded from measurement.

Time on the site and location

To know which biographies and books are being read, the browser sends every minute only the number of seconds a page was actively viewed (open tab and recent action or playing audio). No cookies, local storage or identifier are used. On the first ping the IP address is used only in memory to determine the approximate country and city (DB-IP Lite database); only aggregated daily counts are kept — the IP address is not stored.

Administrator sign-in

The admin area is accessible only to pre-approved email addresses through sign-in with Google (an Emergent service). There is no public sign-up. After sign-in a lekari_admin cookie is set (HttpOnly, 7 days); the database only stores a session hash, the administrator's email and name. Editorial changes are logged in a history.

Technical logs

The hosting server may process technical data (for example IP address and browser type) necessary to deliver pages and ensure security. The application only logs technical errors in its own logs, without visitor identifiers. Fonts are served from the site itself, without requests to external services.

Storage and retention

• Data for books, biographies and aggregated statistics — a MongoDB database on the Emergent hosting platform.
• PDF files and images — Emergent Object Storage.
• Database backups — Emergent Object Storage, the last 30 nightly backups.
• Deduplication records (hash of anonymous identifier × book) — 730 days.
• Hashed IP addresses for rate limiting — up to 2 minutes.
• Administrator sessions — 7 days; aggregated daily counts — no limit (they contain no personal data).
• Cookies: lekari_consent and lekari_vid — 12 months; reading position — until you clear it.