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.
- A request without an API key is metered by an HMAC-SHA256 of your IP address. The HMAC is keyed with a server secret. It is a pseudonym, not anonymous data.
- For an IPv6 address, the HMAC covers only the /64 prefix. So all addresses in one /64 share one budget.
- A request with an active API key is metered by the SHA-256 of the key. Its IP address is not hashed and not stored in the database. Section 2.7 says what the web server logs.
- The row holds the hash, whether the hash belongs to an API key, the number of credits used and the hour the row is for. We delete the row at most 75 minutes after that hour starts. A cleanup job deletes old rows every 15 minutes. If the server is down or the cleanup fails, a row can stay longer.
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.
- A vendor key row holds the id of your key's row, the vendor name, the key you saved and when you saved it. The key is stored sealed, encrypted with AES-256-GCM, and no answer shows it again.
- You change or delete a vendor key through a link that works for 15 minutes. The Service keeps one manage link row for each link it shows you. The row holds the SHA-256 of the link, the id of your key's row, a fingerprint of your key and the end of the link. It never holds the link itself. A save through the link deletes its row once every change of the save passed.
2.3 Monitoring (watchlist). A Pro key can keep a monitoring list. Without a Pro key, the Service stores nothing of this kind.
- An item holds the id of your key's row, the endpoint it watches and the values you gave for it. Those values are a CVE id, a vendor and product pair with an optional version, some CVE search filters, a package ecosystem and name with an optional version, a domain name, or an IP address.
- A package item makes no scan and holds no value that a scan read. A change event of a package holds the advisory and the package, and it names no key. Once an event matches an item, the item holds a reference to the event.
- A domain item also holds its registered domain and the time of its next scan. It holds the values its scans read, such as the name servers, the mail servers and the certificate's end date. Those values hold no certificate and no IP address.
- A domain name that any list watches has one shared row, and that row names no key. A change event of the name holds the change, when it was confirmed, and the value before and after it. A new certificate issuer needs no confirming scan, so its event holds when the scan read it.
- An IP item holds the IP address you gave. An IP address can be personal data, such as the address of a home connection. The item also holds when it was last compared, and two values of that comparison. One value is the DROP listings that hold the address. The other is the hosting class of the address. The item also holds a new hosting class that a comparison saw and has not confirmed yet, with when that class was first seen. A change event of an address holds the address, the change, when it was recorded, and the value before and after it. A DROP event also holds the date and the copyright text of the list.
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.
- The web server's access log holds the raw IP address, the request path without its query, the user agent and the referer of each request.
- The web server logs nothing about a
/password_check/request, because its path holds a password's SHA-1. An/email_address_check/path holds an e-mail address, and the access log keeps it as it keeps any other path. - The host's security tooling keeps the raw IP address of a request it flags or blocks.
- The website at contrastcyber.com uses the same web server and the same access log. Its own program also writes one line for each request: the method, the path, the status and the duration. That line holds no IP address.
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:
/password_check/takes the SHA-1 hash of a password, not the password. It sends Have I Been Pwned only the first 5 hex digits of that hash. It keeps no answer./image_inspectholds your image in memory while it answers. It writes the image, its hash and the answer to no disk, log, cache or database. It sends the image to one other process: the exif service on the same host.
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 ledger row of a payment holds an HMAC-SHA256 of the payment message, an HMAC-SHA256 of the paying token account, a status and the time of the last reserve. Both HMACs are keyed with a server secret. While the payment is pending, the row also holds the transaction signature. The row holds no wallet address, no amount and no endpoint. The status is reserved, settled, pending or released.
- The payment limits count under an HMAC-SHA256 of your IP address for 60 seconds, of the paying token account for 1 hour, and of the payment for 60 seconds. A count names no endpoint and no amount.
- The usage log line of a paid request names the tier x402. It holds no payer and no 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
- The application sets no cookie.
- The theme button keeps your choice, light or dark, in the local storage of your browser under the name
theme. The browser never sends it to us. - Our pages load no script, font or image from another host. Their Content-Security-Policy allows only this site.
- We use no third-party analytics and no advertising tracker.
- The free tier needs no signup. Our database holds no name and no e-mail address of a user. It holds no payment data of a user either, apart from the hashes that section 2.10 describes and the Pro orders of section 8.
- The application derives no location from the IP address a request comes from.
- We do not sell or rent your data. We share it only with the recipients that sections 2.9, 8 and 9 name, and the companies that host our server and our e-mail.
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
- Rate limiting: the hash of your IP address or of your API key meters your credits.
- API keys: the key row tells whether a key is active and not expired.
- Monitoring: the items of a list tell the Service which change events to give that list.
- Upstream limits: the counts of section 2.5 keep our requests to each upstream source within its limits. They are keyed by the source, not by you.
- Pay per call: the ledger of section 2.10 tells whether a payment was used already, holds one wallet to one payment at a time, and limits payment attempts.
- Operations: the usage log shows how the Service is used and where it fails.
7. Data Retention
- Rate-limit rows: at most 75 minutes from the start of their hour.
- Kept answers: an answer of
/ssl_check/,/headers_check/or/whois_lookup/stays one hour. An answer of/wayback_lookup/or/cert_search/stays one day. A/subdomain_enum/answer with Certificate Transparency names stays one day. Without them it stays 10 minutes, or the wait it names. The state that/cve_lookup/keeps stays at most one day. The first purge after that time deletes the row. - Monitoring items and feed position: until you remove them, clear the list or the key is deleted. A key that expired more than 30 days ago loses its list at the next purge. A key that we revoke expires at that moment, so it loses its list 30 days later. The scans of a name run only for the items of an active key.
- Vendor keys: until you delete them or the key is deleted. The first purge after your API key has been expired for 30 days deletes them.
- Vendor key manage links: the first purge after the link has ended deletes its row.
- Change events: the first purge after an event is 90 days old deletes it.
- Counts of our own requests: the first purge after a window has been over for 35 days deletes a count. A per-minute registry count is deleted by the first purge after its minute ends.
- Payment ledger rows: the first purge after a row is 1 hour old deletes it. A payment-limit count is deleted by the first purge after its window of 60 seconds or 1 hour ends.
- Payment events: a payment processor sends us an event when an order is paid, cancelled, resumed, expired or refunded. The first purge after an event is 365 days old deletes it, if it names an order we hold or no order at all. The latest cancel or resume of an order is kept while we hold the order. An event of an order we do not hold yet is kept until that order comes.
- Usage log: about 90 days. A new file starts each day, and the last 90 are kept. While the access log keeps a request, the time of a usage log line can match it to that request's IP address.
- Web server access log: up to about 48 hours.
- API key rows: while the key exists. An expired key no longer works, but its row stays until we delete it. To have your key row deleted, write to us. Deleting a key also deletes its monitoring list and its vendor keys. The order row of a Pro key stays. It keeps the processor's order and subscription numbers and the claim code, and it is marked revoked. So a payment event sent to us again cannot create a new key.
8. Payment Processors
We use two payment processors for Pro subscriptions:
- Lemon Squeezy handles card payments. It receives the payment data you give it directly. See Lemon Squeezy's Privacy Policy.
- NOWPayments handles cryptocurrency payments. It receives the invoice and payment data. See the NOWPayments Privacy Policy.
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:
- Legal basis: we process data on the basis of legitimate interest (Article 6(1)(f) GDPR). That interest is to operate and secure a public API, to prevent abuse and to understand overall usage. For Pro subscribers, we process key and monitoring data to perform the contract (Article 6(1)(b)).
- Data minimization: we collect only what we need. The database stores your IP address as a keyed hash, for rate limiting and for the payment limits of section 2.10. An IP address you add to a monitoring list is stored as a plain address, not as a hash.
- Your rights: you have the right to access, rectification, erasure, restriction of processing, data portability and objection.
- Right to erasure: on the free tier, call
/privacy_my_datato see the hash your rate-limit row is kept under. The rate-limit row is deleted within 75 minutes of the start of its hour. On the Pro plan, write to us to delete your key row and its monitoring list. We process requests within 30 days. - Complaints: you have the right to lodge a complaint with the data protection authority of your country.
- Data Protection Officer: given our small scale and minimal data processing, we have not appointed a DPO. Contact us directly about any privacy concern.
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.