Privacy

This website is maintained by Armanas Povilionis-Muradian. It presents publications, research notes and supporting references. For questions about the website or your data, contact labnotes.muppet358@passinbox.com.

Readership statistics

The private administration panel shows aggregate requests for the archive, privacy page and published notes, plus opens of the stored source and PDF links. These statistics help identify useful material and improve this website. They count requests and actions, not people; repeat visits can increase a count. Individual visitors and browsing histories are not identified. Published notes also report an estimate of active time for their first visible interval.

The database stores a known page or reference identifier, UTC day, action type and count. Source opens may also be grouped by the stored link identifier. Ordinary request headers are reduced in memory to separate counts for a broad referral category, browser family, device category and hosting network entry region; UTC-hour totals show when requests arrive. The entry region is a network routing location, not the visitor's country or precise location. These breakdowns are stored separately, without joining them into a visitor profile.

A separate country count uses the connection IP address supplied by the hosting network. The server looks it up in a local copy of the DB-IP Country Lite database and immediately discards the address from analytics processing. Only the country code and aggregate page/day count are retained; no city, coordinates or IP address is saved or sent to a geolocation provider. This is an estimated network country, not a verified physical location: VPNs, proxies and database errors can affect it, and some requests have no country estimate. IP Geolocation by DB-IP, using data licensed under CC BY 4.0.

On a published note, a small browser script estimates active time while the page is visible and focused. It pauses after 30 seconds without interaction. The first time you leave the note or the page becomes hidden, it attempts one report containing only the note identifier and active seconds rounded to five-second increments, capped at 30 minutes. Interaction details are not transmitted or saved. The server immediately adds the report to daily totals and duration buckets; it does not retain the report or link it to a visitor, country or another note. There are no periodic heartbeat requests.

Time statistics cover reported initial intervals, not complete visits or confirmed reading. Returning to a hidden tab does not extend its report. Closing a browser, losing a connection, blocking scripts or leaving too quickly can prevent a report, so the sample may be biased. Request counts and numbers of timing reports cover different samples.

Analytics does not store individual event records, exact event times, visitor or session identifiers, IP addresses, raw browser user agents, referrer addresses, URL query strings or search text. It uses no analytics cookies, persistent browser storage or fingerprinting. The active-time counter exists only in page memory and uses the single report described above. It does not connect visits across pages. Requests carrying Do Not Track or Global Privacy Control are excluded, as are recognized bots, flagged prefetches and signed-in administrator visits; the timing script also respects these browser privacy signals. These filters are best effort; counts are not a census of human readers.

Daily counts are kept for up to 400 days and removed when counts are next written or the dashboard is opened. Older undated page-view totals are kept separately as legacy statistics. New breakdowns begin when collection is enabled and cannot be reconstructed for earlier visits. Cookie-free collection does not by itself remove transparency duties or establish an exemption from consent requirements in every jurisdiction.

Reading preferences and administration

Some browser storage supports features you use, separately from analytics:

• Session storage remembers your position and filters when returning to the archive, and whether you have chosen to show highlights. It normally clears when the browser tab or session closes.
• Local storage remembers your light, dark or system display preference until you change it or clear the site's browser data.
• For the administrator, local storage saves unfinished editing forms. Saving, cancelling or discarding a draft removes its saved form; browser data can also be cleared manually.
• Administrator sign-in uses an encrypted session cookie, research_session, with a maximum lifetime of 30 days. In production it is restricted to secure HTTPS requests and cannot be read by page scripts. Server-side checks allow sessions to be revoked, including after account recovery or credential changes. It is not an analytics identifier.

Shared highlights

When you submit a highlight, the selected passage, its position and colour are saved with a count and timestamps. Highlights can be shown to other readers. The website does not attach a reader account or visitor identifier to a public highlight. Administrator annotations are marked separately.

Hosting and security

The application and its database are hosted on Fly.io in Amsterdam, Netherlands. Delivering pages and protecting the service necessarily involves processing technical request information, including IP addresses. Request limits use temporary in-memory keys derived from IP addresses, or browser request headers when an IP is unavailable. Those keys are separate from analytics and expire after their rate limit window; expired entries are removed on subsequent requests or when the application restarts.

Hosting providers may also process operational and security logs. Their logging and retention are separate from the aggregate analytics described here and depend on the provider's policies and service configuration.

External references and your choices

Following an external source, publication, PDF or profile link takes you to the destination website, where that provider's privacy practices apply. You can clear this site's cookies and browser storage in your browser settings. Contact the address above to ask about data processing or request access, correction or deletion of personal data relating to you. The readership database has no visitor identifier with which to retrieve a personal browsing record.