Privacy Policy

Last updated: 2026-11-14

1. Introduction

ContrastCyber ("we", "us") operates ContrastAPI at api.contrastcyber.com. This Privacy Policy covers the data we handle when you call the API, over REST or over MCP. It also covers the web pages at api.contrastcyber.com, the website at contrastcyber.com and its CVE pages.

2. Data We Collect

2.1 Rate limiting. Each request is charged to a credit budget, and the database keeps one row for each budget.

2.2 API keys. An API key row holds the SHA-256 of the key. It also holds when the key was created, whether it is active and when it expires. It never holds the key itself.

A Pro key can also keep vendor keys, one Shodan key and one AbuseIPDB key. Without a Pro key, the Service stores nothing of this kind.

2.3 Monitoring (watchlist). A Pro key can keep a monitoring list. Without a Pro key, the Service stores nothing of this kind.

The Service scans each watched domain name about once a day. It compares each watched IP address with its local lists about every 15 minutes, after one of the lists has a newer sync, and sends no request to the address. You read the change events yourself, with watchlist_events.

2.4 Kept answers. These endpoints keep their answer for a while: /ssl_check/, /headers_check/, /whois_lookup/, /wayback_lookup/, /cert_search/, /subdomain_enum/ and /cve_lookup/. /cve_lookup/ keeps only the state that CVE.org names for an id our data does not hold. That state is stored under the CVE id. Every other kept answer is stored under its host name or registrable domain, in lower case. Any caller who asks the same question in that time gets it. The row holds no API key, no credit budget and no IP address of the caller. The application keeps no other answer, and every API answer carries Cache-Control: no-store.

2.5 Counts of our own requests. The Service counts the requests it sends to each upstream source, such as Cert Spotter or an RDAP server. A count names the source or its host, and a time window. So an RDAP count tells which registry was asked in a minute, but not which domain or by whom. A count holds nothing else about a request or a caller. Two kinds are the exception. A count of the headers scans names the registered domain of a watched name. The payment limits of section 2.10 count under an HMAC of a client address, of a paying account or of a payment.

2.6 Usage log. The server writes one line to its usage log for each connection. A line holds the time to the second, the port of the server, whether the request came over REST, MCP or the web, and the name of the endpoint, web file or MCP method it asked for, if any. It holds the tier, the HTTP status, how the request ended and how long it took. It holds the size of the answer, the credits the request was charged and the item count of a bulk request. It holds no IP address, no API key, no query, no body and no argument value. A request may name an endpoint that does not exist. The line then writes that name only when it is a short lower-case word.

2.7 Web server and network.

2.8 Values you send. The application stores no path, query, body or looked-up value of a request in its database, except the items above. These endpoints take extra care:

2.9 Requests we send for you. Some endpoints ask another host about the value you send. Only that value, or a part of it, leaves the server. The one addition is your own vendor key, as described below. For example, /whois_lookup/ sends the registered domain to the RDAP server of its registry. /cert_search/ sends the host name to Cert Spotter. /password_check/ sends the first 5 hex digits of the hash. /cve_lookup/ sends the CVE id, and nothing else, to the CVE Services of CVE.org at cveawg.mitre.org when our data does not hold the id. These requests carry our User-Agent. They carry neither your IP address nor your API key. A Pro key that saved a vendor key adds requests of its own. /ip_lookup/ sends your own vendor key and the looked-up address to Shodan at api.shodan.io and to AbuseIPDB at api.abuseipdb.com, for each vendor whose key you saved. When you save a key, the server checks it. It sends the Shodan key to Shodan, and the AbuseIPDB key with the address 127.0.0.1 to AbuseIPDB. A status request sends each saved key to its vendor the same way. The bot page lists each of these requests.

2.10 Pay per call (x402). A request without an API key may pay for one call with USDC on Solana. The payment itself is public on Solana. Anyone can read the transfer there, with its amount and its wallets. The Service keeps the following about a payment.

The facilitator that verifies a payment and sends it to Solana runs on the same host as the API server. It uses a Solana RPC provider for both steps, so that provider receives the signed transaction. When you retry a pending payment, the server asks the provider whether the transaction is confirmed. That request holds the transaction signature, which is public on Solana. The provider also sees the address of our server. See section 9.

3. What We Do Not Collect

4. Check It Yourself

The Service has an endpoint that shows the hash it meters you by:

curl https://api.contrastcyber.com/privacy_my_data

The answer shows your tier, your credit budget and the hash your request was metered by. With a Pro key, it also shows whether a Shodan key and an AbuseIPDB key are stored, and the link that opens the page where you change them. It links to this policy, which says what is stored and for how long. The MCP tool privacy_my_data gives the same answer.

5. Do Not Track & Global Privacy Control

The Service does not act on the Do Not Track (DNT) or Global Privacy Control (Sec-GPC) header. It keeps no analytics profile that these signals could switch off. The rate-limit row of section 2.1 is needed to meter every request.

6. How We Use Data

7. Data Retention

8. Payment Processors

We use two payment processors for Pro subscriptions:

For Pro subscriptions, the API server's database holds no card data and no wallet data. It holds a row for each order: the processor's order and subscription numbers, the claim code, the row of the key it gave, the order's status and its times. It also holds the payment events of section 7. When we delete a key row, its order row stays, marked revoked, with no key. It keeps the processor's order and subscription numbers and the claim code. So a replayed payment event cannot create a new key. We share no usage data, IP address, query or answer with either processor.

A payment per call (section 2.10) goes through no payment processor. It is a transfer on Solana. The facilitator on our own host verifies it and sends it to Solana. A Solana RPC provider receives the signed transaction when we verify and send it. It receives the transaction signature of a pending payment when we check it.

9. International Data Transfers

Our server is located in Germany (EU). If you use the Service from outside the EU, this EU server handles your requests. Payment processors run their own infrastructure in their own jurisdictions. The upstream sources of section 2.9 receive only the name a request asks about. Shodan and AbuseIPDB also receive your own vendor key. The Solana RPC provider of section 2.10 receives the signed transaction and its signature.

10. GDPR (EU/EEA Users)

If you are in the European Union or the European Economic Area:

11. KVKK (Turkish Users)

If you are in Turkey, we respect your rights under the Personal Data Protection Law (KVKK, Law No. 6698). You have the right to learn whether your personal data is processed, and to request information about that processing. You have the right to learn its purpose and whether the data is used for that purpose. You have the right to know the third parties that receive the data. You have the right to request correction or deletion, and to ask that third parties be told of it. You have the right to object to a result against you that comes only from automated analysis. You have the right to claim compensation for damage from unlawful processing. Our server is in Germany, so your data is processed outside Turkey, and section 9 names the other recipients. Write to us at the address below to use these rights. You can also apply to the Personal Data Protection Board.

12. Security

Requests to api.contrastcyber.com travel over HTTPS. The host runs security tooling that blocks abusive traffic. Section 2.7 says what that tooling keeps.

13. Children's Privacy

Our Service is not directed at children under 16. We do not knowingly collect data from children. If you believe a child has used our Service, contact us and we will delete any associated data.

14. Changes

We may update this Privacy Policy. We post each change on this page with a new date. We announce material changes on this website.

15. Contact

For privacy questions, or to use your rights, write to contact@contrastcyber.com.