Data policy

BlockPanther is a general market, so whether a purchase is legal depends on the data. The contract records who claimed what, but it can't make an unlawful purchase lawful. This page covers what we carry, what we refuse, and how anyone can ask us to take a dataset down.

#What we refuse

We refuse contracts in these categories when they're posted, whatever lawful basis they give.

• Special-category personal data, such as health, biometric or genetic data, religion, political opinions, sexual orientation and union membership
• Criminal records
• Credentials, such as passwords, API keys and session tokens
• Government ID numbers, such as social security, passport and licence numbers
• Payment card and bank account numbers
• Data about children
• The precise location of individuals

We also scan every delivery for payment card numbers and US social security numbers, and refuse it if we find any.

#Personal data

If a contract's rows describe identifiable people, it has to state a lawful basis (consent, contract, legal_obligation, vital_interests, public_task or legitimate_interests), where the data came from in plain words, and which jurisdictions it covers. With every delivery the seller signs an attestation naming the job, contract, data, license and lawful basis, and stating that it has the right to sell the data.

Buyers of personal data are usually controllers under GDPR, CCPA and US state privacy laws, and may need a lawful basis of their own to use it.

#Scraped data

Plenty of sites forbid scraping and resale in their terms, and some have gone to court over it. A seller who takes data from one of those sites breaks its attestation. Check the source before you buy or sell scraped data.

#Takedowns

Anyone can ask us to stop carrying a dataset, and they don't need a wallet, since most data subjects and rights holders won't have one. Use the report form, or POST /v1/takedowns with {job_id, reason, contact}.

A person reads every report. If we uphold one, we delete the dataset's encrypted copy, its preview and its keys, close the job, and end the series if it's recurring. If the seller hasn't been paid yet, we stop the payment and refund the buyer.

We can't claw back a payment that already went through, but the buyer loses access to the key and the data.

#What we keep, and for how long

• While checking, we decrypt the delivery inside a sandbox with no network, and we don't keep the plaintext.
• After payment, we keep the ciphertext for 30 days by default so the buyer can download it, then delete it. The contract's retention_days sets the period.
• After a refund, we delete the ciphertext and its key straight away.
• Verdicts are public and never quote the data.

Because we decrypt deliveries to check them, you're trusting us not to keep a copy. We're moving the checker into a confidential-computing enclave that anyone can verify, which will remove the need for that trust.