Aerod handles topics that can be sensitive: public IP visibility, IP lookup, browser exposure, fingerprinting surfaces, DNS behavior, WebRTC behavior, VPN/proxy route consistency, affiliate redirects, and security guidance.
The default posture is data minimization.
Static content pages
Most pages are static. Reading a guide, hub, doc, policy, provider page, or comparison page should not require invasive tracking. Normal hosting infrastructure may still process request metadata needed to serve the page.
IP Lookup
An IP lookup tool requires requests to lookup data providers. A “What’s My IP” check also requires a request because the app has to see the public IP address presented by the current connection.
IP lookup results can include public IP, IP version, ISP or organization, ASN, approximate country, region, city, timezone, privacy signal, and map coordinates when a provider returns that data. These values should be treated as current-session or lookup-result context, not a permanent identity profile by default.
IP geolocation is approximate. It may identify a network route, ISP, VPN, proxy, carrier, business network, or cloud point rather than exact device location.
Browser checks
Browser-focused apps should run locally where practical. Browser Fingerprint Check is treated as a local diagnostic surface: if a value can be computed and explained in the browser, it should not be sent to a server without a specific reason.
Examples of browser-side signals can include rendering behavior, Canvas/WebGL availability, audio behavior, font and text metrics, timezone, language, viewport, storage support, and permission state. These signals can be sensitive because they may contribute to a fingerprint pattern.
Browser Fingerprint Check
Browser Fingerprint Check is a local browser diagnostic for fingerprintable characteristics and consistency signals. Results should be treated as a current-session view of available browser surfaces, not as a permanent identity profile. Exported reports should remain user-controlled unless Aerod intentionally adds a documented comparison or storage feature later.
Browser, WebRTC, DNS, and route checks
Browser Leak Test, Browser Fingerprint Check, WebRTC Leak Test, and Proxy/VPN Detection are session-specific app checks. Results should be presented as current browser or route signals and should not be treated as permanent user attributes.
DNS behavior may require controlled external infrastructure. Until that infrastructure exists, DNS guidance should be presented as interpretation and setup guidance rather than a complete DNS leak test.
If DNS, WebRTC, browser, timezone, or language behavior contradicts an expected VPN or proxy route, Aerod should label the issue as a configuration review path unless the result directly demonstrates a meaningful exposure.
Affiliate redirects
Affiliate redirects use /go/<slug> routes. The redirect function needs the slug to select the destination. If click counts are added later, they should be anonymous or aggregate unless this policy is intentionally updated.
Pages that include affiliate links should use appropriate disclosure and link attributes. App pages should link to the Proxies and VPN hubs when interpretation is useful instead of turning the main tool surface into an affiliate wall.
Analytics and advertising
Aerod is prepared for Google Analytics through an optional PUBLIC_GA_MEASUREMENT_ID build setting. When that value is configured, the site loads Google’s gtag.js measurement script and sends page measurement data to the configured GA4 property.
Aerod also loads the Google AdSense site script with the approved publisher client so the domain can be reviewed for ads. The site should use restrained ad placements and avoid popups, interstitial takeovers, or layouts that make app and article content harder to use.
Analytics and advertising scripts are third-party scripts. They may process browser, device, page, referrer, and interaction signals under Google’s systems and policies. Aerod should keep this disclosed and revisit this policy if analytics events, ad formats, or consent behavior change.
Logs
Infrastructure logs may exist for deployment, debugging, abuse prevention, and security. Logs should be retained only as long as needed for those purposes.
Migration data
Migrated content may include source URLs, original publish dates, screenshots, tables, provider details, affiliate disclosures, author names, tags, and metadata. Missing source content should be flagged instead of replaced with generic filler.
Migrated articles should use the original publish dates as Aerod publish dates according to the migration workflow. Internal migration notes should not be rendered publicly.
Migration notes should not expose private credentials, unpublished affiliate account details, or internal secrets.
Review standard
Any new app, analytics tool, redirect change, or content migration process should be checked against this data handling model before publishing.