Privacy

Optional advertising on the tool page

Advertising is off until you accept in the cookie dialog, or this website has your saved, unexpired advertising acceptance. Rejecting leaves the free tool available. Cookie-Einstellungen reopens the two choices; Werbeeinwilligung widerrufen saves a rejection and reloads the page to stop future provider scripts and requests. Withdrawal cannot erase information or cookies already held by third parties.

After acceptance the approved Adsterra 300×250 tag runs directly in the tool page. Adsterra and its advertising partners may place/read cookies and browser-storage identifiers and process IP address, page address, browser/device details, advertising interactions and identifiers for advertising delivery and measurement, including internationally. The audited bootstrap creates a seven-day visitor identifier; downstream advertisers may have their own retention periods. See Adsterra privacy information and Adsterra cookie information for purposes, recipients, retention and international processing. Consent is the basis for optional device storage/access under §25 TDDDG and advertising processing under Art.6(1)(a) GDPR.

A necessary first-party cookie, signal_advertising_v1, stores only the advertising decision, notice revision and decision time for up to 180 days, separately on this host. It has no visitor identifier and is not sent to our statistics collector. The cookie prevents repeated prompts and respects refusal; necessary choice storage relies on §25(2) TDDDG and Art.6(1)(f) GDPR. If the browser blocks this cookie, your choice applies only to the loaded page.

The tool's own calculation/file/media code does not hand its inputs or results to the advertising tag. Advertising scripts nevertheless execute in the same document after acceptance; this is not an isolated-origin privacy boundary. Declining advertising avoids those third-party scripts. Optional aggregate statistics retain their separate, default-off choice described below. Advertising consent does not enable statistics.

Optional aggregate statistics on the tool

Statistics are off by default. Checking the choice and pressing Enable statistics is explicit consent under Art. 6(1)(a) GDPR. The tool works without consent. Withdraw at any time in the statistics section, or uncheck the choice. Consent stays in page memory only; it is not saved to cookies, localStorage or sessionStorage. A new load or restored navigation requires a new choice. Withdrawal stops future events and cancels pending requests; it cannot delete events already received.

After consent, one visible-page event and the accepted completed-operation events listed below can be sent to https://signal-income-observatory.pages.dev/api/collect. No earlier operation is replayed.

This page currently sends no successful-function event: its published core has no accepted completion hook. Opt-in pageviews only; no button presses are inferred as success.

The payload has only schema version, fixed tool ID tool-001-ai-is-down, fixed function ID, contract version, outcome, QA flag and a fresh random UUID for that operation. No text, date, numeric input, calculation, file, filename, metadata, audio, microphone or device data, URL, query, fragment, referrer, visitor/account identifier or input detail is included. Requests omit cookies and referrer. The temporary operation token is used only for bounded duplicate detection in collector memory for ten minutes; it is not stored in the database or used as a visitor identity. Only aggregate UTC-day tool/metric counts, separately marked QA, are saved in the operator's private EU D1 database. The application has no IP, browser-agent or personal-input database columns.

Cloudflare necessarily handles connection IP and ordinary browser request headers to deliver HTTPS requests. Its transport/security processing and possible retention follow the Cloudflare hosting notice and Cloudflare privacy policy. The application writes no event/request logs; Pages deployment log streaming is not enabled. This is not a promise that all provider metadata is absent. Daily aggregate counts currently have no automatic expiry. Operator contact is in the imprint; these aggregate rows cannot be linked back to a particular visitor.

There are at most 50 attempts per loaded page, without retries, with a three-second timeout. Consent choices, blockers, outages, global caps, forged/automated events and duplicate-detection limits make counts incomplete. These events do not measure unique visitors, independently audited demand, ad clicks/impressions, search visibility, revenue or CPU margin. An absent row remains unknown. Owner QA uses an exact local #portfolio-qa marker which sends only qa:true; the marker itself is never sent. QA is stored separately from demand. Statistics consent does not change the separate main-page advertising choice.