Privacy & cookies

Current analytics status

Google Analytics is not enabled. No Google Analytics tag, analytics cookie, advertising tracker, or pre-consent measurement ping is loaded by these websites.

The optional integration is prepared but will stay disabled until the operator’s privacy-contact details and the data-processing configuration are confirmed. This page describes the current setup; it is not a claim of legal certification.

Website operator

The supplied website-operator name is Agentic Realities, based in Finland. The full legal identity and public privacy-contact email still need confirmation before optional analytics can be activated.

Hosting and necessary requests

GitHub Pages delivers these websites. Requests necessarily reach the hosting infrastructure. GitHub states that visitors’ IP addresses are logged and stored for security purposes, whether or not they are signed into GitHub.

GitHub’s handling of hosting data, retention, international transfers, and privacy requests is described in its privacy statement. See also GitHub Pages data collection. The website operator does not receive a visitor-level analytics dashboard from these pages while optional analytics is disabled.

Analytics preferences

If analytics is later enabled, accepting will be optional. Rejecting will keep Google’s tag blocked, without cookieless analytics pings. You will be able to withdraw consent through “Analytics preferences” in the footer; the page then reloads without the tag and removes accessible analytics cookies.

A consent preference, when chosen, is stored in local browser storage for up to 180 days. It contains only the choice, notice version, and expiry time—not a visitor identifier. The main site and each subdomain keep separate preferences. If browser storage is unavailable, a choice lasts only for the current page. Browser Global Privacy Control and Do Not Track signals keep analytics off.

Before Google Analytics is activated

The notice must identify the controller and privacy contact, processing purpose and consent basis, Google as a recipient, applicable transfer arrangements, actual retention settings, and how to exercise data-protection rights. The configured integration disables advertising consent and Google signals, omits query strings and fragments from the manually sent page URL, and does not configure user IDs.

The operator must review Google’s processing terms and account settings, including enhanced measurement, data sharing, and retention. Accepting analytics does not permit advertising or remarketing. Consent alone is not a guarantee of GDPR compliance.

You may raise data-protection concerns with Finland’s Office of the Data Protection Ombudsman.

Links and project applications

Following a link sends a request to the destination website. Third-party services have their own privacy information. Any later use of a project application, account, upload feature, or private database is outside the scope of these public information pages and requires its own appropriate notice.