Scope
This Privacy Policy explains how Aerod handles information when someone uses the website, reads content, follows affiliate links, changes privacy preferences, or uses privacy and security apps hosted on Aerod.
Aerod is designed for privacy-sensitive users. The operating principle is to collect less, explain what is needed, and deny optional storage until the browser records a choice.
Information the site may process
- Basic request information required to deliver and protect the website, such as IP address, user agent, requested URL, referrer, timestamp, and similar infrastructure log fields.
- App result information required for a tool to return a result, such as the public IP visible to Aerod or browser-provided signals used by a browser privacy check.
- Voluntary contact information when a user submits the contact form: reply email, topic, message, and any optional name, affected page URL, or attachments.
- Affiliate redirect information when a user follows a
/go/<slug>route. - Local preference information stored in the browser for optional Analytics and advertising choices.
App checks
Aerod apps run checks locally where practical. Some checks necessarily involve a network request. An IP check, for example, cannot show the public address visible to a website without receiving a request from the browser.
Browser, WebRTC, fingerprint, route, camera, and microphone results should be treated as current-session observations rather than permanent identity profiles.
Camera and microphone permissions
The Online Webcam Test asks for camera or microphone permission only after the user starts the relevant test. Live media is used in the browser for preview, input monitoring, device selection, and user-initiated local capture. Aerod does not require those streams to be uploaded.
Consent Mode, Analytics, and advertising
Aerod initializes Google Consent Mode v2 with analytics_storage, ad_storage, ad_user_data, and ad_personalization denied. Optional Google Analytics does not load until the browser records an Analytics grant.
The Google AdSense library can load in a paused state for domain verification, consent messaging, and advertising readiness. Aerod keeps ad requests paused until the local advertising preference is allowed and, where applicable, a Google-certified consent-management message provides the required consent signal.
Aerod enables Google TCF integration support. The certified message itself is configured through AdSense Privacy & messaging. Rejecting or revoking advertising consent pauses future requests governed by the page.
Google services can process browser, device, page, referrer, consent, and ad-request data under Google policies when the relevant service is active.
Privacy preferences
The Privacy Preferences page allows the user to permit or decline optional Analytics, permit or decline advertising storage, reject all optional services, clear the saved choice, reopen the local banner, and request an applicable Google privacy message.
Choices are stored in local storage on the current browser. Clearing browser storage can remove them.
Affiliate links and third-party websites
Aerod may use disclosed affiliate links. Third-party provider, documentation, standards, Analytics, advertising, and consent systems have their own privacy practices.
Data retention
The contact form sends submissions to Aerod's administrative inbox through Cloudflare Email Service. Cloudflare Turnstile processes browser and request signals to prevent spam; the server also uses connection information and short-lived rate-limit counters. These necessary protections are separate from optional Analytics and advertising preferences.
Messages and attachments are processed in memory during submission, not saved in a separate Aerod submission database or public file store. Aerod's contact-service logs record operational outcomes and reference IDs, not message bodies or attachments. Email providers and hosting infrastructure can retain delivery and security records. Delivered messages and attachments remain in the administrative inbox and may be retained as needed to handle the request, investigate security issues, and meet applicable obligations; they are not automatically deleted when the form closes.
Provide only information needed for the request. Do not upload passwords, private keys, malware samples, or unnecessary personal information. Attachment validation is not a guarantee that a file is safe. No automatic confirmation email is sent, and submissions are not added to a mailing list. See Cloudflare's Privacy Policy for its processing practices.
Aerod should retain only what is needed for security, operation, debugging, compliance, aggregate measurement, and documented commercial reporting. App results should not be stored as user profiles by default.
Contact
Send privacy questions or requests through the Aerod privacy contact form.