CabinTally / Site notes
Privacy, in plain English
What this PHP frontend processes: anonymous event hashes, local content caching, and merchant redirects.
What this frontend processes
To serve a page, the web server receives the request path, IP address and browser user-agent. This PHP app does not maintain visitor profiles, a mailing list, accounts or a local visitor database. It does not set cookies, use browser storage, load external fonts or embed third-party tracking scripts.
Page views and outbound clicks
When the publishing connection and page-view recording are enabled, a successful public HTML page can send its path and, for a review, its article slug to the publishing API. Recognized bots are skipped. Previews, errors and HEAD requests do not generate page-view events.
Merchant links send a product ID to the API to record an outbound click and obtain the current stored destination. This happens even when optional page-view recording is disabled. These events are page views and clicks, not verified purchases.
A daily anonymous hash
When a private visitor salt of at least 24 characters is configured, the app combines the UTC date, IP address and user-agent locally using HMAC-SHA256. Only the resulting anonymous daily visitor hash is sent with events. No raw IP address or user-agent is sent in the event payload. With no suitable salt, the optional hash is omitted. The API receives this server’s network connection and a fixed application user-agent.
The hash rotates each UTC day. This app has no endpoint for looking up individual visitors and stores no local event history. Local file caching stores public publishing content, not visitor event payloads.
Server logs and upstream storage
The hosting server may keep access logs containing request information. The publishing service stores events under its own retention settings. This frontend does not set a retention period for either system, and it does not provide a visitor-level deletion interface.
When you visit a merchant
A verified merchant link redirects your browser to a stored external URL, which may include affiliate tracking parameters. The merchant then receives your visit and applies its own privacy policy and storage practices. CabinTally sends a no-referrer policy on the redirect and uses noreferrer on merchant links.
Scope of this notice
This notice describes the behavior implemented in this frontend. No legal entity, office address or contact details are asserted here. Hosting and publishing-service settings should be reviewed by the operator before launch.