Benchproof / Miller Hoey Ventures LLC
Privacy
Last updated: September 29, 2026. This page describes information the application stores; it does not set a retention or deletion policy.
Information Benchproof handles
Benchproof stores account information used for sign-in; company profile fields and evidence submitted by an account holder; saved assessment and report snapshots; and purchase records such as product, price, currency, checkout reference, payment state, and entitlement balance. The app also stores contact-form name, email address, and message, plus signup attribution fields when present.
The assessment purchase is one-time and payment is collected on Stripe-hosted checkout managed by Polsia. The app records a checkout reference and payment verification result; its Benchproof purchase record has no card-number field. Profile, evidence, purchase, and saved assessment reads use the signed-in account id in the current application routes.
Product analytics
Benchproof sends a page-view beacon to Polsia with the site slug and a random browser visitor id stored in local storage. It also records allowlisted funnel events for pricing views, purchase clicks, signup, checkout start, and verified payment. Public funnel rows contain the event name and visitor id; authenticated rows contain the event name and internal account id. Assessment completion is recorded separately with its assessment id, account id, time, and acquisition source.
Signup attribution can store an allowlisted source, UTM fields, external referrer hostname, and capture time. The funnel event record has no free-form payload field.
Storage, sharing, and retention
The application uses these records to provide account access, save and reopen assessments, verify purchases, accept contact messages, and record the product events described above. Official NASA sources may be linked in a report. Customer profiles, evidence, purchases, and saved assessment reports are not presented as a public directory.
Miller Hoey Ventures LLC has not supplied retention periods by data type, a deletion request process (including scope, identity checks, exceptions, or timing), a subprocessor list, cross-border processing details, or a legal basis for processing. This page does not state those policies. A monitored privacy-request contact has not been verified.