Privacy Policy
Cookie-Free • No Advertising Trackers • Idea To Fact LLC
1. The Privacy-First Commitment
AirGap Axis values digital sovereignty and operational transparency. We design our website to respect your privacy, avoiding invasive tracking mechanisms, user profiling, and third-party advertising networks.
2. Privacy-Focused Aggregate Web Analytics (Cloudflare)
To understand high-level visitor activity and ensure registry availability, AirGap Axis uses Cloudflare Web Analytics (static.cloudflareinsights.com).
Cloudflare Web Analytics is specifically engineered to be privacy-first and cookie-free:
- No Tracking Cookies: It does not set or read client cookies or local storage identifiers on your device.
- No Cross-Site Profiling: It does not track individuals across websites or construct behavioral profiles.
- Aggregate Metrics Only: It collects non-identifiable, high-level traffic numbers such as aggregate pageviews, top referrers, device/browser categories, and country-level geography.
- No Personal Data Sale: We do not sell, rent, or monetize any analytics data.
3. What We Do NOT Collect
- No Advertising Trackers: We do not use Google AdSense, Meta Pixel, LinkedIn Insight Tags, or marketing pixels.
- No Behavioral Surveillance: We do not run session replay tools, keystroke loggers, or heatmaps.
- No Third-Party Marketing CDNs: All core application scripts, styling, and icons are served directly from our root domain.
- No Public User Accounts: Visitors browse the registry without creating profiles, passwords, or entering personal data.
4. Edge Infrastructure & Security Logging
Our website is hosted on Cloudflare Pages. Cloudflare edge servers process standard HTTP request metadata (IP address, user agent, requested path) in transient memory to route packets, mitigate DDoS attacks, and enforce security policies. These access logs are not used for visitor tracking.
5. Owner CMS Authentication
When authorized maintainers unlock Owner Admin Mode, their GitHub Personal Access Token (PAT) is stored exclusively in their local browser's sessionStorage. The token is transmitted solely to GitHub's official REST API (api.github.com) to commit updates to catalog.json. It is never logged or sent to any intermediate server.
6. Contact & Inquiries
For privacy inquiries or data practice questions: [email protected]