THE FINE PRINT / PRIVACY

Measure the page.
Respect the person.

You can scan a public website without accepting audience analytics.

What a scan records

A clean browser opens the submitted public URL. We store the URL, domain, public title and description, aggregate resource telemetry, redacted resource paths and selected response headers. We do not forward your cookies, login session or form values. Never submit a private URL or a URL containing passwords or access tokens. Receipts are accessible to anyone who has their link.

AI-readiness checks also store bounded public metadata, text counts, attribution/structured-data signals, matched robots rules and the resulting checklist. The full page body and full robots.txt are not retained. A separate protected request reads the site’s public robots.txt. Address-bar shortcuts use the same scan protections and do not opt you into public discovery.

Public discovery is a separate choice

The optional listing checkbox makes a new homepage receipt eligible for Just printed and Trending. It is off by default. Only root homepage URLs without query strings or fragments are listed; redirects to deeper pages are excluded too. Existing cached receipts do not change publication permission. Anyone with a receipt link can still open the receipt whether or not it appears in discovery. No visitor identifiers or contact details appear in public feeds.

First-party audience analytics are opt-in

When you choose “Allow analytics”, this installation records page views, visible-tab activity, scan-submit/cache-hit actions, share/download clicks and viewable ad impressions/clicks. It stores random browser and session identifiers as server-side keyed hashes, coarse device/browser categories, referrer hostnames and sanitised campaign tags. Raw IP addresses, email addresses, full referrer URLs and page query strings are not stored in the analytics events.

Identifiers and retention

The browser identifier expires after 30 days. A session restarts after 30 minutes of inactivity or a new tab session. Analytics events are retained for up to 90 days. Events are stored in PostgreSQL. Owner reports are capped at 100,000 events and warn when that limit is reached. The production deployment must run the documented retention task. A separate signed, HTTP-only anti-abuse cookie may be used when you submit a scan or interact with server endpoints. It expires after one day and is not a cross-site advertising identifier.

Your choice

Use “Analytics preferences” at the bottom of the page to withdraw consent. This removes the local tracking identifiers and stops new analytics events; previously aggregated measurements remain until retention removes them. Browser Do Not Track and Global Privacy Control preferences are respected. Blocking analytics does not block the scanner. An owner can disable all event collection with ANALYTICS_ENABLED=false.

Sponsorship and public reporting

Sponsor placements are labelled Sponsored. The public Stats page contains aggregate traffic and inventory numbers only. Owner reports and exports require a password. Sharing or downloading a receipt does not reveal how many people see it on another platform, and we do not invent that reach. We do not infer age, profession, country, purchases or sponsor conversion revenue from a scan.

Optional receipt history

When you enable recent receipts, the last 12 receipt links are saved in this browser. No account is needed. Use Clear history to remove them, or turn history off to stop saving new receipts. Clearing device history does not delete public receipt links.

Sponsor contact details and notifications

Sponsor contact details are stored with the booking for payment support and campaign management. When email delivery is enabled, Resend processes campaign confirmations, reminders and reports. Availability alerts require email confirmation, send one availability message, and can be stopped from the private email link. Alerts expire after 180 days. Support and privacy questions can be sent to yoosufsayyid@hotmail.com.

Payments

Checkout is disabled until the operator configures Dodo. When enabled, Dodo hosts checkout; payment credentials and owner authentication secrets are not supplied to the scanner.

Back to the receipt printer →