Privacy-conscious measurement
We count anonymous aggregate pricing views, research-kit views, printable evidence sample openings, share actions and quote-interest clicks by a fixed event category in daily totals. These counters never include selected country/state/report rows, search queries, page URLs, source fingerprints, names, email addresses, IP addresses, cookies or device identifiers. Counts may include automated traffic and are directional events, not unique visitors or verified individual conversion rates. When you submit an inquiry with consent, we store a limited source category (such as report sample or pricing request) with the inquiry for attribution. Inquiry records follow our 90-day deletion schedule. Anonymous daily event totals are deleted after 180 days.
Information we collect
When you submit a custom data request, we store the email address, intended use, category, requested fields or requirements, preferred delivery format, optional budget-interest range, optional desired timeframe, submission time, and a random one-time request identifier used to prevent accidental duplicate submissions. Budget responses are non-binding research signals; no payment is collected. Please do not submit passwords, financial account details or sensitive personal records.
Why we use it
To review requests, understand what people need, and possibly contact you about availability or clarification. After a request is accepted by our system, a transactional email provider may deliver a limited notification to the listed DataSupply operating contact. The notification includes the inquiry reference, email address, stated need and request preferences so authorized staff can review and reply; it is not marketing. Email delivery and abuse-prevention metadata are processed under the provider's service terms. Requests are not publicly displayed. The public dataset browser does not require an account or payment. When a paid report is enabled and ordered, checkout is hosted by Stripe on behalf of the disclosed merchant; DataSupply does not receive or store full card numbers. The server stores an order reference, dataset ID, price, payment status, report body, report SHA-256, Stripe session and payment-intent identifiers, and a salted client-IP hash for anti-abuse. These are separate from optional sourcing inquiries. When a paid report is eventually enabled, its immutable analysis artifact will also be stored privately in Cloudflare R2. Public R2 access is disabled, and the report download endpoint checks the stored order status before releasing the file.
Retention and access
Custom sourcing requests are kept in restricted Cloudflare D1 and scheduled for deletion after 90 days. Paid order records, if any, use a separate restricted D1 table. They are not covered by the inquiry deletion schedule and will be subject to an independently defined commerce retention/deletion policy before checkout activation. Access is limited to authorized operators. Operational hosting and security logs may be handled separately by Cloudflare.
Payment processing and order recovery
When enabled, a secure checkout takes place on Stripe, operated under the merchant name SmallBusinessFix.com. Stripe processes payment details under its own privacy terms. DataSupply uses a signed Stripe webhook—not a browser redirect alone—to confirm payment and release the purchased analysis report. A buyer’s Stripe session reference acts as an order-access token, so do not share the order URL. Contact the DataSupply support address on the pricing page if fulfillment or refund review is required. Paid recurring delivery is not currently offered through checkout.
Search privacy
When you search for datasets, your search words may be sent to the U.S. General Services Administration's Data.gov catalog service for third-party metadata discovery and temporarily cached to limit repeated lookups. Do not put personal, confidential, or payment information into dataset search terms. Source links may take you to third-party publishers governed by their own privacy practices.
Data sources
Public packs include a SHA-256 fingerprint of the normalized rows and fields, and downloaded files expose their own byte-level SHA-256. These are repeatability and integrity references—not publisher authentication, security certification, or proof of factual accuracy.
Public government records displayed here come from the identified agencies. You should read their original documentation and limitations before acting on the information. The data is not independently certified by DataSupply.
Contact
For privacy inquiries or a request to remove your submission, use the listed operating contact and include the submission reference if you have it.
Public site notice, November 2026. Commercial terms, retention schedule, merchant support/statement details and payment processor review must be finalized before enabling live charges.