Durudam Living
Privacy information
The features currently available on the blog and the information associated with them.
A reading-focused blog
Visitor registration, comments, contact forms, and newsletters are not currently available. Advertising-display scripts are not enabled. Visitor statistics are aggregated on this server as described below.
Access logs
The web server records information such as IP address, request time, requested URL, response status, browser details, and a referring URL when supplied, to serve the site and investigate problems. The current configuration rotates logs daily and retains up to 14 previous non-empty rotations. Empty logs are not rotated, so this is not a promise of deletion after exactly 14 days.
Language choice and administrator login
The multilingual feature may store a pll_language cookie to remember a language preference. You can clear or block cookies in your browser, though you may need to select your language again. Administrator sign-in uses WordPress authentication and preference cookies.
Contact details and future features
Article, calculator and accessibility errors can be reported through the shared anonymous Durudam report form on the main site. It accepts an optional HTTPS article URL and a message of up to 2,000 characters. Reports are stored in a private server inbox accessible only to administrators. There are no name or email fields, attachments or individual replies. Do not include personal or sensitive information. This form is for content reports, not a dedicated privacy-rights request channel. See the privacy notice for the shared form for processing details. Other operator contact routes remain in preparation. Before adding contact, analytics or advertising features, we will review the actual data processing and contact route and update this notice.
Configuration checked: September 8, 2026. Additional retention practices for server backups and operational records, and operator contact details, remain to be completed.
Sign-in security records
Reading the blog does not require an account. To reduce repeated attempts against administrator accounts, the Durudam network records failed-sign-in counts, IP addresses, the submitted username or email identifier, event times, and access routes on its server. The security plugin does not store the submitted password in its sign-in logs.
Sign-in limits are shared across sites in this network. Detailed lockout records and daily security records are configured for periodic removal after 14 days. Scheduled-job delays and separate server backups can affect the actual deletion time. Rate-limit counters and web-server access logs follow their own settings.
Attempt limiting currently runs locally on this server; the plugin’s external cloud analysis and notification emails are not connected. An external human-verification service has not been activated while account permissions are being confirmed. Its provider and processing details will be added here when it is connected.
Visitor statistics and operational checks
Durudam uses Koko Analytics on its own server to aggregate daily pageviews, estimated daily visitors, viewed page paths, and referring website domains. For this Koko aggregation, analytics data is not sent to an external analytics service, and analytics cookies or local storage are not used.
To reduce duplicate counts within a day, the collector derives a one-way hash from an IP address, browser information, and a daily rotating random value. The analytics store keeps this temporary hash rather than the original IP address or browser information and does not link a visitor across days. Temporary hashes are scheduled for daily removal, and aggregated statistics older than three months are periodically removed. Pending records are normally aggregated within about one to two minutes. Delayed scheduled jobs or separate server backups can affect actual removal times. Ordinary web-server access logs are separate and follow their own retention configuration.
Search terms, URL query strings, and detailed referrer paths are excluded from analytics records. Signed-in operators and known bots are excluded. Collection is skipped when the browser sends a DNT or GPC opt-out signal. Script blockers, devices sharing a network, and changes in connection or device can make visitor estimates differ from actual people.
Only authorized operators can access statistics and operational reports. Operational checks record homepage response codes and response times, certificate expiry, and server capacity; check history is retained for 30 days. External continuous monitoring and notification emails are not connected.
Cloudflare RUM performance measurement
Separately from our own Koko aggregation, Cloudflare RUM performance measurement code sends information such as page loading and rendering performance and the current and referring page URLs to Cloudflare.
Cloudflare states that this code does not use cookies or browser storage. The current dashboard is set to exclude EU visitor data. The descriptions of Koko retention, operator exclusion and DNT/GPC handling do not imply that the same conditions apply to RUM.
Official processing information: Data collection · RUM processing and privacy. Checked: 2026-10-30.