Privacy

Privacy Policy

How information may be processed during the current operation of this site and what choices visitors have.

Effective date: 2026-09-06

Food & Health Guide processes information only as needed to operate this site. The public site does not enable a contact form, comments, newsletter, or personalized advertising. Visitor statistics are aggregated on this server as described below.

Information that may currently be processed

  • IP address, browser type, requested URL, timestamps, and server logs used for security and troubleshooting
  • A Polylang language-preference cookie (pll_language, retained for up to one year) used to remember a visitor’s selected language
  • Essential WordPress cookies used for functionality and preferences when an administrator signs in
  • Information a visitor may explicitly submit in the future, with this policy updated when such a feature is added

How information is used

Information may be used as reasonably necessary to operate and secure the site, diagnose errors, prevent abuse, and meet legal obligations.

Service providers and international processing

Providers supporting hosting, security, backups, and technical operations may process information under applicable contracts and law. Servers or support systems may be located outside a visitor’s country.

Retention and security

Information is retained only as long as reasonably needed for the stated purpose, legal requirements, security, and dispute resolution. Reasonable safeguards are used, but no internet transmission or storage system is completely secure.

Your rights and contact

Depending on location, you may have rights to access, correct, delete, restrict, object to, or receive a copy of personal data. A rights-request channel will be published on the Contact page when the production domain and dedicated privacy mailbox are connected.

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.

Changes

If analytics, advertising, contact forms, comments, or newsletters are added, this policy and any required cookie choices will be updated first to reflect the actual processing.

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.

Scroll to Top