No analytics identifier
The aggregate table does not store a cookie ID, account ID, advertising ID, fingerprint, email address, or other visitor identifier.
Privacy boundary · aggregate counts only
Measure interest.
Do not profile people.
Build Proof Lab uses a deliberately narrow first-party counter to compare which documented projects, downloads, and disclosed affiliate providers people choose. It is not presented as unique visitors, sales, customers, or revenue.
Application record
Exactly what the counter stores.
- UTC calendar day.
- Allowlisted event category: project page opened, package downloaded, or affiliate destination opened.
- Allowlisted project or provider key.
- Allowlisted page surface, such as a project card or domain-search result.
- Aggregate count and the time that aggregate row was last updated.
Deliberate exclusions
No application-level visitor profile.
No request identity
The application does not write IP addresses, user agents, referrers, or full destination URLs to the aggregate table.
No domain-search history
The name entered into the domain tool is not sent to this counter. If a registrar link is opened, the registrar receives the requested destination under its own privacy terms.
No cross-site tracking
The counter uses no analytics cookie and does not combine activity across unrelated sites. Global Privacy Control or browser Do Not Track set to 1 prevents the browser-side signal.
Product prioritization.
Aggregate totals help decide which projects deserve customer interviews, compatibility work, support design, or retirement. Clicks alone never justify a testimonial, conversion claim, or paid launch.
Normal infrastructure still operates.
The hosting and security providers may process ordinary request metadata under their own operational and legal requirements. That infrastructure processing is separate from the application’s aggregate signal table.
Destination policies apply.
Downloads are served by this site. External demos, registrars, hosting providers, and affiliate destinations process visits under their own privacy, account, and commercial terms.
No visitor-level deletion record exists.
Daily aggregate rows may be retained for longitudinal product planning because they contain no application-level visitor identity. They cannot be used to find or delete one person’s click.
Your checklist stays in your browser.
Launch-checklist progress is stored on the device through browser storage. It is not sent to the aggregate signal table. Clearing browser storage removes it from that browser.
The opt-in is optional and purpose-limited.
If you request the two free guides, the email address you submit is processed by Systeme.io to provide the resources and occasional practical product updates. You can unsubscribe at any time. The library does not operate a public account, payment, or open contact form. A verified operator identity and monitored privacy contact must be published before any broader intentional collection of identifiable information.