Privacy
Read the public website privacy summary.
This page describes the release-facing privacy posture for the official
ait-native website. It applies to the public site surface, not to future
customer agreements, self-hosted deployments, or a future authenticated
hosted product.
- Official website only
- No login required
- Updated November 6, 2026
Scope
This privacy summary covers the static-first public website and the release-facing materials served through it. It does not describe separate data handling for self-hosted deployments or future authenticated hosted offerings.
What this website may receive
- Routine request metadata processed by the hosting layer, CDN, or reverse proxy, such as IP address, request path, user agent, and request time.
- Any information you intentionally send through a public feedback or repository channel in response to this site.
- No account, login, or in-browser workflow state is required just to read the current public pages.
Cookies and analytics
The observatory publishes anonymous aggregates from existing server access logs;
it adds no analytics cookies, browser-storage identifiers, sessions or beacons.
Qualified page requests and estimated daily browsers are not people, installs
or product adoption. Referring domains and valid utm_source,
utm_medium and utm_campaign labels are separate,
overlapping dimensions of those requests. Missing referrers are direct/unknown.
The collector retains at most 90 days of daily aggregate counts. It stores only normalized hostnames and bounded campaign labels with their counts, never raw referring URLs, full request targets, IP addresses, User-Agent strings or transient browser identities. Public rankings show at most ten entries with at least two browser-days; suppressed names and labels are not published. Browser-days sum daily estimates, not seven-day unique people. Do not place personal information in campaign labels. Hosting access logs retain their existing hosting-layer lifecycle, separately from these aggregates. No third-party analytics provider or tracking endpoint is added.
How information may be used
- Serve the requested public pages reliably.
- Monitor uptime, delivery health, and abuse or security signals at the website edge.
- Respond to a message you intentionally send through a published public channel.
- Improve public wording, routing, and release-facing clarity without turning the site into a hidden product telemetry surface.
What not to send
This public website is not the right place to submit confidential customer data, private source code, secrets, credentials, or regulated personal data. Use a dedicated private contract or security path when those channels are formally published.
Status note
This is release-facing website guidance, not legal advice. More detailed privacy, security, or data-processing terms may be added later if the product expands into authenticated or hosted public surfaces.