Legal

Privacy Policy

Last updated November 5, 2026

This policy explains what personal information licenscheck collects when you use licenscheck.com and the licenscheck API, and what we do with it. We don't sell personal information, and we don't use advertising trackers.

Visitors to the website and free API

• No accounts, no cookies. The website sets no cookies.
• IP addresses and visits. Our hosting and security provider, Cloudflare, processes your IP address and request details (browser type, approximate location, and the pages and API requests you make) to deliver the site and block abuse, and gives us analytics of them. We review a daily summary of those visits, kept in our private team chat, to understand how the site is used and to spot bots and abuse. The API also uses your IP address to enforce rate limits and the daily free searches. Short-term rate-limit counts live only in memory; the daily search count is stored for up to 7 days under a keyed one-way hash of your IP address, never the address itself.
• Searches. We keep each search for 90 days: the words or license number searched, the state chosen, how many licenses it found, and the API key it was made with (or, without a key, the same one-way hash of your IP address). We read it to find searches that came back empty and fix them. It's never shared or sold.
• Saved keys. If you save an API key in your browser, it stays in your browser's storage and is sent only to the licenscheck API.

API customers

• What you enter in the "Talk to us" form: your name, work email, company, and what you'd check. We use it to set you up and follow up.
• The name and contact email you give us when we issue your key.
• For a free key: the email you sign up with (and your name and company, if you give them), which we use to send you the key, to keep it to one free key per person, and to follow up about licenscheck. Each signup is posted to our private team chat.
• Your key, stored only as a one-way hash.
• How many successful requests each key makes to each endpoint, and each AI agent tool (MCP), per day, which we use for billing and capacity planning. We don't store what an agent sends us beyond what the request itself needs: the contractors it checks are counted and, for a batch, saved as described below.
• If you use monitoring: which licenses each key watches, the events we write about them, and the web addresses you ask us to send those events to, with a record of each delivery. We use them only to run monitoring for you, and keep them while your key is active.
• If you verify a spreadsheet: the values in each row you upload (never the file itself), how each row matched and its verdict. We use them only to show and send you the results, and delete them 90 days after the upload, or after a day if you never run it.
• If you issue a proof report: the report and its PDF, kept so that anyone you give it to can check it's genuine. Its public page shows only what the report prints.
• If you pay us, Stripe, our payment processor, handles your card details; we never see or store them.

Email

When you email [email protected], we keep the correspondence to answer you and to keep a record of what was agreed.

People in the license records

The license data we show is public record published by state licensing boards, and can include licensees' names, business addresses, phone numbers and principals. We show it as the board reports it. If something about you is wrong, correct it with the board, and our copy will follow on its next refresh. If you think our copy or our matching is wrong, email us and we'll review it.

Who processes data for us

• Cloudflare: website hosting, network security, visit analytics, and email forwarding.
• OVHcloud: the server that runs the API and database, in Virginia, USA.
• Stripe: payments and subscriptions; it receives your card, billing details and how many verifications your key used.
• Google Fonts: the website's typefaces, which your browser downloads from Google, so Google receives your IP address and browser details.
• Google Cloud: encrypted database backups and the archive of the boards' raw files, in the USA.
• Google (Gmail): our support inbox.
• Resend: sends the email with your free API key.
• Sentry: error reports from the API, with the failing request's address but not its headers, body or your IP address, in the USA.
• Discord: our private team chat, where the daily visit summary, key requests, free-key signups and operational alerts are posted.

Retention

We keep information as long as we need it for the purposes in this policy, including billing, tax and accounting, resolving disputes, and enforcing our agreements.

Your rights

You can ask what personal information we hold about you, and ask us to correct or delete it, by emailing [email protected]. Depending on where you live, the law may give you these and other rights; we'll respond as the law requires. We don't sell personal information.

Security

We use reasonable measures to protect the information we hold, such as storing keys only as hashes and encrypting backups. No system is perfectly secure, and we can't guarantee that information will never be accessed, disclosed or lost.

Children

The Service isn't directed to children under 13, and we don't knowingly collect their information.

Changes

We may update this policy at any time; the date at the top shows the latest version.