Support and source review
Contact & corrections
Multi-seat and organisation licensingSelf-service checkout is one seat for one verified address. Everything beyond that is quoted individually. Include the organisation name, the number of named users, and the intended use.support@provenancedatahub.com
Who operates this service
| Operating entity | Provenance Data Research LLC |
|---|---|
| Form and jurisdiction | A limited liability company formed in Wyoming, United States |
| Seller of record | the applicable Paddle entity identified at checkout and on the receipt is the merchant of record for purchases and appears on your receipt. Billing questions may be raised with either party. |
Where to write
There is no message form on this site: enabling one would mean collecting personal data through a route with its own retention and spam-handling requirements, and email already does the job. Please write from the address on your account where the request concerns a purchase.
| Purpose | Address | What to expect |
|---|---|---|
| Billing, refunds, and access problems | support@provenancedatahub.com | First substantive reply within 2 business days. |
| Data corrections and facility disputes | support@provenancedatahub.com | Acknowledged on receipt; corrections ship in a later release, never as an in-place edit. |
| Privacy requests and data rights | privacy@provenancedatahub.com | Handled under the privacy notice. |
| Source rights, licensing, and removal | legal@provenancedatahub.com | Reviewed against the source-rights record for the cited page. |
| Security reports | support@provenancedatahub.com | Acknowledged within two business days; please allow time to remediate before disclosure. |
Correction request
Include the facility ID, facility name, the affected field, the value shown now, the value you believe is correct, a public source URL supporting it, the date of that source, and a short explanation. A correction backed by a public page the operator itself publishes is the fastest to process.
Accepted corrections ship in a later release. A release that has already been sold is never edited in place, so a buyer can always reproduce the file they paid for — see the release integrity section of the data dictionary.
Please do not send confidential facility information, anything under an NDA, or payment card details.
Source-rights or removal request
If you own or administer a page cited by this database and believe a field, link, or description should be corrected, restricted, or removed, provide the facility ID, the material at issue, your authority to make the request, the relevant source or policy URL, and a contact address. Requests are reviewed against the record of what was accessed and when.
Paid access
Paid facility search and the complete CSV are not on sale yet. The public pages, the ten sample records, the methodology and the coverage figures are complete and free to use in the meantime, and what each paid product will include is set out on the pricing page.
To be told once when paid access opens, write to support@provenancedatahub.com with “launch notice” in the subject. Your address is used for that one message and nothing else — there is no mailing list, and no other use of it.
Commercial enquiry
Multi-seat access, organisation licensing, purchase orders, specific invoice requirements, scheduled delivery, and client-use rights are arranged through a reviewed quote. Self-service checkout grants one seat for one verified email address and does not imply any of them. Write to support@provenancedatahub.com with the organisation name, the number of named users, and the intended use.
Security reports
Report suspected vulnerabilities to support@provenancedatahub.com. Please include enough detail to reproduce the issue. Do not test against production data, other users’ accounts, or the payment provider, and do not access or retain data that is not yours. Reports made in good faith under these limits are welcome and will not be pursued.
Refund requests
Paid web access carries a 24-hour discretionary refund window, assessed automatically against the published rules; the complete CSV is not refundable once it has been delivered, though a failed or defective delivery is always replaced or refunded. Both routes, and the evidence to include, are set out in the cancellation and refund policy.