Choose useful editorial questions
Aggregate interest helps me see which questions may deserve an article without turning any reader into a dossier.
Privacy and intent measurement
Aggregate demand sensing, with a public boundary.
My commitment: I run an aggregate demand-sensing system, not a surveillance archive.
Automation status: Not independently verified. The public site can measure consented actions. I have not independently verified the automated transfer into aggregate research in production, so I do not describe that automation as active.
Why this exists
Useful measurement without a reader dossier.
Improve recommendations
Anonymous totals show whether readers understand and use a recommendation, so I can repair weak decision paths.
Plan capacity without reading inquiries
Aggregate inquiry totals help me plan capacity and offers without exposing what a prospect wrote.
Make the boundary inspectable
The public policy and explicit exclusions let readers, partners, and procurement teams inspect the boundary before they grant consent.
What I count
Three consented actions, counted without identity.
- Recommendation shown
- Recommendation opened
- Commercial form sent
The site counts nothing until you choose Allow analytics. It counts a recommendation once per page and browser session. It counts clicks and form submissions only after you act.
Technical field reference
| Technical field | Purpose |
|---|---|
schema_version | Non-personal event or journey context |
event_id | Non-personal event or journey context |
occurred_at | Non-personal event or journey context |
event_type | Non-personal event or journey context |
path | Non-personal event or journey context |
page_type | Non-personal event or journey context |
topic | Non-personal event or journey context |
recommendation | Non-personal event or journey context |
destination | Non-personal event or journey context |
entry_path | Non-personal event or journey context |
last_content_path | Non-personal event or journey context |
journey_depth | Non-personal event or journey context |
utm_source | Allowlisted first-touch campaign context |
utm_medium | Allowlisted first-touch campaign context |
utm_campaign | Allowlisted first-touch campaign context |
utm_content | Allowlisted first-touch campaign context |
What I never collect for intent measurement
- names
- emails
- companies
- messages
- form values
- wallet data
- IP addresses
- user-agent strings
- arbitrary query parameters
- persistent identifiers
- cross-session profiles
- retargeting audiences
- reader scores
- account scores
Firm boundaries
Aggregate interest never becomes editorial authority.
Storage and aggregation
The form service may temporarily receive individual measurement submissions. I do not treat them as analytics records or retain them in Git. Any research process may save monthly totals and aggregate briefs only, never individual submissions or event IDs. I have not independently verified the automated transfer in production.
Editorial verification
I treat aggregate interest as inspiration only. I still commission every article as a human editor, verify it with independent sources, and apply the published editorial standard.
Commercial independence
I never let measured interest change a ranking, finding, correction priority, or commercial boundary. A partnership buys reach, never a rating.
Disable and recover
Choose Decline in the analytics banner, or clear the saved analytics choice in your browser and reload. The site sends no intent measurement unless you explicitly choose Allow analytics.
Site operators can disable intent measurement and redeploy. After any boundary failure, they must stop collection, delete affected temporary records, disclose the incident, and publish a correction.
Privacy FAQ
Questions to answer before you grant consent.
Does the concierge profile readers?
I use a random ID to prevent duplicate counting of one submission. I do not reuse it to identify a reader, fingerprint a browser, join sessions, build a profile, or score a person or account.
What happens to raw intent submissions?
The form service may temporarily receive individual measurement submissions. I do not treat them as analytics records or retain them in Git. Any research process may save monthly totals and aggregate briefs only, never individual submissions or event IDs. I have not independently verified the automated transfer in production.
Can aggregate intent commission an article automatically?
I treat aggregate interest as inspiration only. I still commission every article as a human editor, verify it with independent sources, and apply the published editorial standard.
Can intent change a ranking, finding, correction, or commercial decision?
I never let measured interest change a ranking, finding, correction priority, or commercial boundary. A partnership buys reach, never a rating.
How can a reader or operator disable it?
Choose Decline in the analytics banner, or clear the saved analytics choice in your browser and reload. The site sends no intent measurement unless you explicitly choose Allow analytics. Site operators can disable intent measurement and redeploy. After any boundary failure, they must stop collection, delete affected temporary records, disclose the incident, and publish a correction.
Policy version 1 · Last verified 2026-08-12. Review the policy data (JSON), the independence rules, and the verification record. Report a boundary failure through corrections or contact.