Inside the nook
Privacy, in plain language
How AirDryNook handles API requests, anonymous page views, outbound clicks, and browser storage.
What the frontend does.
This site renders pages on the server. It contacts a publishing API from PHP to fetch public content and to resolve merchant links. API credentials stay on the server and are not sent to your browser.
Page views and outbound clicks.
When page-view recording is enabled, a publishing connection is configured, and a visitor salt is set, successful page renders may send the page path and article slug to the API. Obvious automated visitors and draft previews are skipped.
A daily-changing HMAC visitor hash is computed on the server from the connection IP address, user-agent string, date, and a private salt. This application sends the hash, not the raw IP address or user-agent string, to the API. Without a sufficiently long salt, page-view recording stays off. Outbound clicks send the product ID and include that hash only when a salt is configured.
These hashes support approximate activity counts; they do not prove a person’s identity or a purchase. This frontend does not provide an analytics retention policy or controls for the separate publishing service.
Browser storage and server logs.
The application does not set cookies, use local storage, load third-party scripts, or offer account registration. The hosting server may maintain access or error logs separately; this frontend does not set the hosting provider’s log retention rules.
Content cache and merchant sites.
The server caches public publishing responses for a limited time. The cache contains public content, not visitor hashes. Merchant and source links lead to other sites with their own privacy practices. Outbound merchant redirects use a no-referrer policy.
Contact availability.
There is no public privacy contact inbox or contact form configured on this site yet. Do not submit sensitive information through page URLs.