Privacy

No human audience tracking

The website application does not measure individual human visits, set visitor identifiers or maintain visitor profiles. Separate AI request counters operate on ordinary server requests as described below.

No tracking storage

The application does not set analytics or advertising cookies, tracking pixels, browser fingerprints, advertising identifiers, or analytics values in local storage or session storage.

No submitted visitor form data

The public reference website does not provide visitor account registration, comments, newsletters or contact forms. A separate internal statistics report is restricted to the authorised site administrator using platform sign-in; it is not a public visitor account service.

AI request statistics

A separate server-side counter recognises documented AI crawler user-agent tokens. Where official provider IP lists are available, the request source IP is checked transiently against recent provider network ranges. Network-verified requests and requests that merely claim a crawler identity are reported separately. A user-agent name alone does not verify an AI provider.

Only known public pages and public data resources are included. API, sign-in and administrative routes are excluded. Query parameters, fragments, raw source IP addresses, full user-agent strings, referrers, exact request timestamps, visitor hashes and session identifiers are not stored in the statistics database.

The stored fields are the calendar date in Europe/Budapest, provider, crawler label, documented purpose, verification category, public resource path, GET or HEAD method, response status class and request count. This counter does not execute browser measurement code, set cookies or fingerprint visitors.

Purpose and legal basis

The operator's purpose is to assess automated access to its published reference material and the technical operation of the website. Where transient processing of request information concerns personal data, the legal basis is the legitimate interest in that limited purpose under GDPR Article 6(1)(f), assessed against necessity, reasonable expectations and individual rights. Automated origin does not by itself remove data protection obligations. The final daily aggregates are designed not to identify or single out a natural person.

The separate hosting and security processing described below is not represented as absent merely because the application counters retain no source identifiers.

Retention and limits

AI request aggregates are kept for no more than 365 days. Automatic maintenance normally removes them after 364 calendar dates, with an additional check scheduled every six hours. There is no individual request log in the statistics database.

Counts are HTTP requests, not unique people or AI users. A request does not establish citation, model training, indexing or use in an AI answer. Some automated access cannot be identified, and the crawler's documented purpose does not establish how a particular retrieved page was later used.

Provider identification references: OpenAI crawlers, Anthropic crawlers, and Perplexity crawlers.

Ordinary page requests

A browser still has to request pages and files in order to display the website. Those requests necessarily pass technical connection information, such as an IP address and user-agent string, to the hosting infrastructure while the request is handled.

Hosting and security logs

The hosting platform may process or retain standard delivery, reliability, abuse-prevention or security logs under its own infrastructure practices. Energy Drink Facts does not describe those platform records as its own application analytics and does not claim that infrastructure logging is absent.

External links

Pages link to studies, authorities, manufacturers and other external sources. Following an external link sends a separate request to that destination, whose own privacy and logging practices apply.

Future changes

If application-level analytics, accounts, forms, advertising technology or other data collection are introduced, this page should be updated before that processing begins and should explain what changes.

Contact and operator disclosure

The website provides no public privacy contact address and names no data controller. Readers should treat this as a transparency limitation. The About page records the available publisher information.