This Privacy Policy explains what Hextner collects when you use VerifIP, DetectBT and this website, why, who processes it, how long it is kept, and how to have it deleted (in your account settings or by writing to contact@hextner.com).
1. Who we are
Hextner ("Hextner," "we," "us," or "our") provides adversarial traffic detection APIs — specifically VerifIP (server-side IP intelligence) and DetectBT (client-side browser fingerprinting). This Privacy Policy explains how we collect, use, store, and protect information when you use our website, APIs, the DetectBT browser script, documentation, and related services (collectively, the "Services").
For the purposes of data protection law, Hextner is the data controller of the personal data described in this policy.
2. Data we collect
2.1 Account information
When you create an account, we collect:
- Name, email address, and organization name
- Billing information (processed by our payment provider; we do not store full card numbers)
- API keys and authentication credentials
2.2 API request data
When your systems call our APIs, we process:
- VerifIP: the IP addresses, email addresses, phone numbers and URLs submitted for checking, along with request metadata (timestamp, API key identifier, response latency) and the result returned
- DetectBT: Browser fingerprint signals (canvas entropy, WebGL renderer, pointer physics, timing data, and other runtime characteristics), and the public half of the device key with a signature (section 2.3). DetectBT does not collect personally identifiable information such as names, emails, or form contents.
2.3 DetectBT: what the SDK stores in the browser
To tell a returning browser apart from a bot farm that keeps changing IP addresses and sessions, the DetectBT SDK stores two items in the visitor's browser. They are kept separately for each website that uses DetectBT and for each of our customers' keys:
- A device key. The SDK creates an ECDSA P-256 key pair in the browser and keeps it in IndexedDB (a database named
detectbt-device). The private key is created as non-extractable: the browser will use it to sign, but no script can read it out, whether the website's, a browser extension's or ours, and it never leaves the browser. With each evaluation the SDK sends us the public key and a signature over that evaluation. - A device certificate. A short record that we sign and the SDK keeps in localStorage (under
detectbt-dc:followed by the customer's public key). It holds an identifier derived from the public key, when we first saw that key, how many evaluations it has made, and a keyed tag of the network it last used, not the IP address itself. The SDK sends it back to us with the next evaluation.
The key and the certificate work only on the website that created them, so we cannot use them to recognise a browser across different websites or different customers. Nothing is stored until the website starts DetectBT, and a website that must ask for consent first can set DetectBT to wait for it. Clearing the website's data in the browser settings deletes both items. If the browser cannot store them, DetectBT works without them and does not count that against the visitor.
On our servers, to spot one key being used from many networks or in many sessions at once, we keep, for each verified key, the network ranges (the /24 or /64 of the IP address) it used in the last 10 minutes and a count of its evaluations in the last minute. These are held in memory only, are not written to disk, and are lost when that server restarts. We do not keep a database of device keys.
Why we may use it. Our legitimate interest, and our customers', in detecting bots, fraud and account abuse (Article 6(1)(f) GDPR).
2.4 DetectBT: detection-quality records
Before a new detection signal is allowed to affect any verdict, we measure how often it wrongly flags real people. For that we may keep a small sample of DetectBT evaluations, together with the outcomes our customers report to us.
- Evaluation samples. When this is switched on, we record a random sample of evaluations and the evaluations that were flagged. Each record holds the evaluation's ID and the customer's public key ID; the verdict, score and flags; the browser engine and its major version, the browser family, operating system type and device class (mobile or desktop), derived from the user agent; the network's ASN and country; a hash of the IP address's network range (the /24 or /48), keyed with a secret that changes every day so records from different days cannot be linked by network; the TLS and HTTP versions and a short code for the TLS cipher list, which is shared by every user of the same browser build; the challenge result; yes/no behaviour indicators and the name the website gave the protected action (such as login); a few counts; and the device key's status and an age range. Times are kept to the minute. We do not store the IP address, the user-agent string, fingerprint values, the page address or the device identifier.
- Outcome reports. Customers can tell us what an evaluation turned out to be (for example fraud, legitimate, chargeback or spam), with an optional note of up to 200 characters. We keep the report with the evaluation's ID, verdict and score. We ask customers not to put personal data in the note.
Both are stored in our database, hosted by Supabase. Evaluation samples are deleted after 30 days. Outcome reports are deleted after 30 days while evaluation sampling is switched on; a report received while it is off is kept until sampling is next switched on, and is deleted then if it is older than 30 days. Deleted records leave our encrypted backups within about a further 7 days. Why we may use it. Our legitimate interest in accurate detection that blocks bots without blocking real people (Article 6(1)(f) GDPR).
2.5 DetectBT: sites a key was used from
To help our customers set up the allowed sites for their DetectBT keys, we record, for each of a customer's publishable keys, the website hostnames that requests claimed to come from when that website was not on the key's allowed list (or any website, while the key has no list). Each record holds the key's ID, the ID of the customer account the key belongs to (used to cap how many records one account can collect per day), the hostname with its port if it has one (such as shop.example.com), and the day. The hostname is taken from the request's Origin header, which browsers set but other software can choose, so it is what the request claimed, not proof of where it came from. The key's owner sees the last 30 days of these in the console.
We record nothing about the visitor: no IP address, user agent, page address or time finer than the day. The records are stored in our database, hosted by Supabase, and deleted after 30 days; deleted records leave our encrypted backups within about a further 7 days. Why we may use it. Our legitimate interest in helping customers configure DetectBT so that it works on their own sites and nowhere else (Article 6(1)(f) GDPR).
2.6 Support & communications
If you contact us, we retain your name, email, and the content of the communication to provide support and improve our services.
3. How we use your data
We use the data we collect to:
- Deliver the Services — process API requests, return verdicts, and generate threat intelligence
- Improve accuracy — measure and refine our detection using pseudonymised evaluation samples and customer outcome reports (section 2.4)
- Maintain security — detect abuse of our own platform, enforce rate limits, and investigate incidents
- Billing & administration — process payments, send invoices, and manage your account
- Communicate — send service updates, security advisories, and (with your consent) product announcements
- Legal compliance — meet our obligations under applicable law
We do not sell your personal data. We do not use API request data for advertising or cross-customer profiling.
4. Data sharing & disclosure
We share data only in the following circumstances:
- Service providers: Infrastructure partners (cloud hosting, CDN), payment processors, and support tools. Our infrastructure partners include Cloudflare (hosting, CDN and our APIs) and Supabase (database hosting). Our other service providers include Razorpay (payments) and Telegram (internal operations alerts to our team, which can include your email address).
- Legal requirements: If required by law, regulation, subpoena, or court order
- Business transfers: In connection with a merger, acquisition, or sale of assets, with equivalent privacy protections
- With your consent: For any purpose you explicitly authorize
5. Data retention
Retention periods depend on the type of data:
- API request logs: API request logs are kept for 90 days; a daily job deletes older entries, which then leave our encrypted backups within 7 days. For a DetectBT evaluation the log holds the account and API key identifiers, the request type, the score, whether it was billed and, only when the verdict is bot, the IP address shortened to its network (the /24 or /48).
- DetectBT detection-quality records: 30 days, with the exception for outcome reports described in section 2.4.
- DetectBT sites a key was used from: 30 days (section 2.5).
- DetectBT device key and certificate: kept in the visitor's browser until the visitor clears that website's data; the per-key counts on our servers cover at most the last 10 minutes and are held in memory only (section 2.3).
- Account data: Retained while your account is active. When you delete your account, we delete your account data 30 days later (a subscription still being settled with our payment processor is settled first); copies leave our encrypted backups within about a further 7 days. If you ask us within 30 days of deletion, at contact@hextner.com, we can restore a deleted account; plans and API keys are not restored, and an account that signs in with a password will need a password reset. We keep the payment and invoice records that tax law requires us to keep (up to 8 years), with your name, email and contact details removed.
- Support communications: 2 years from the last interaction
You can request deletion of your data at any time by emailing contact@hextner.com or through your account settings.
6. Data security
We protect your data with:
- Encryption in transit (TLS) and at rest by our hosting providers
- Access to our systems restricted to authorized personnel
7. International transfers
Our service providers (listed in sections 4 and 12) may process data in countries other than yours.
8. Your rights
Depending on your jurisdiction, you may have the right to:
- Access — request a copy of the personal data we hold about you
- Rectification — correct inaccurate or incomplete data
- Erasure — request deletion of your data ("right to be forgotten")
- Portability — receive your data in a structured, machine-readable format
- Restriction — limit how we process your data
- Objection — object to processing based on legitimate interests
- Withdraw consent — where processing is based on consent
To exercise any of these rights, contact contact@hextner.com. We respond within 30 days.
9. Cookies & tracking
Our website does not set cookies of its own. Your browser's local storage keeps your sign-in session and a few small interface preferences (for example, that you dismissed the onboarding guide), and session storage keeps a few short-lived values while you sign up or check out. The payment window (Razorpay) and any video you choose to play (YouTube) follow their own cookie policies. We do not use advertising or analytics cookies, and we add no trackers of our own. If we introduce analytics in the future, this policy will be updated accordingly.
DetectBT's client-side SDK does not set cookies. It does store a device key in IndexedDB and a device certificate in localStorage, on the website that uses it, so that a returning browser can be recognised on that website (section 2.3). Clearing the website's data deletes both.
10. Children's privacy
Our Services are not directed to individuals under 16 years of age. We do not knowingly collect personal data from children. If we learn that we have collected data from a child, we will delete it promptly.
11. Changes to this policy
We may update this Privacy Policy from time to time. Material changes will be communicated via email to account holders and posted on this page with an updated "Last updated" date. Continued use of the Services after changes constitutes acceptance.
12. Business outreach
We sometimes email people at companies that we think could use our products. This section explains what we use for that and how to stop it.
Where the information comes from. Public information about companies: their own website, public directories such as the Y Combinator company list, and public posts on Hacker News. Your work email address is either published on your company's website or directory listing, or formed from your name and your company's domain and then checked with an email verification service.
Why we may use it. Our legitimate interest in telling businesses about products relevant to their work (Article 6(1)(f) GDPR). We do not email people in Germany, Austria, Denmark or Italy.
What we keep. Your name, role, work email address and company; the emails we send you and any reply. If you click a link in one of our emails, we record the click with the approximate city and country and the network provider derived from the request, so we know which messages are useful. We do not use tracking pixels.
Opting out. Reply "no" or "unsubscribe" and we stop immediately and for good. We keep only a one-way hash of your address so that we never contact you again. You can also write to contact@hextner.com for a copy of your data or to have it deleted.
How long we keep it. If you do not reply, we delete your contact details and our messages 9 months after our last email.
Service providers. Zoho Mail (sending and receiving email), Cloudflare (hosting), Groq (drafting and sorting messages; it does not train on our data), Reoon (email verification) and Telegram (notifications to our team).
13. Contact us
For privacy-related inquiries, including EU-specific matters:
- Email: contact@hextner.com