Privacy

The site currently provides public, repository-owned content. It has no accounts, comments, newsletter, forms, personalized profiles, or client-side analytics code. It uses private, server-side access-log analytics and does not set cookies for measurement or advertising.

The site does not publish or request AdamI memory, task data, runtime telemetry, administrative access, or other private system information.

The production site is delivered through Cloudflare infrastructure. As part of delivering and protecting the site, that infrastructure may process ordinary request information such as IP addresses, request paths, timestamps, browser details, and security signals under its own service operation and policies.

Protected raw server logs temporarily contain the Cloudflare-provided client IP, requested path, status, timestamp, country code, referrer, and full user agent. During processing, the full referrer is reduced to its host, the full user agent to a coarse category, and the raw IP is never written to the analytics database.

Private server-side analytics processes the requested path, response status, timestamp or date, coarse country, referrer, and user-agent category. An IP address is used only to derive a daily rotating pseudonymous visitor key; the key is not designed to identify a person across days.

Raw access logs are retained for 7 days, pseudonymous events for 90 days, and aggregate statistics may be retained longer. There is no public analytics dashboard, and analytics is not connected to the AdamI runtime.

The site uses no analytics cookies, fingerprinting, advertising, sale of personal data, or cross-site tracking.

/demo/ is an optional constrained public interaction layer, not the full AdamI runtime. Using that page sets a short-lived HttpOnly cookie on same-origin /api/demo/ so the temporary session can continue. The cookie is not used for advertising, cross-site tracking, or analytics identity, and the session identifier is not written into the page or browser storage.

Demo requests are handled by a separate public interaction service. They do not read or write production memory and do not provide unrestricted tools. The rest of the static site remains readable if the demo service is unavailable.