Skip to content

Privacy policy

What we collect, why we collect it, who processes it for us and the choices you have.

Last updated 2026-10-27

This policy explains how Kleerance, LLC ("Kleerance", "we", "us"), a company based in New York, United States, handles personal information when you visit kleerance.com or use the Kleerance screening service. Kleerance is a business-to-business service for screening companies and people against government restricted-party and sanctions lists.

1. Information we collect

  • Account information. Your email address, name and organization name, and a sign-in identifier. If you sign in with Google, Google shares your name and email address with us. Passwords are handled by our authentication provider and stored only in hashed form.
  • Screening inputs and results. The names and other details you screen while signed in, the lists searched, the results returned, the time of each search and any review decisions you record. These are saved to your account so you have a record of each check.
  • Anonymous searches. Searches on the public homepage without an account are not saved to any account. We keep a signed counter in a cookie so we can apply the free daily limit.
  • Billing information. Payments are handled by Stripe. Card details go directly to Stripe and never reach our servers; we receive your plan, subscription status and Stripe customer reference.
  • Messages and requests. When you use the contact form we store your name, email address, optional company name, message and the IP address it came from (to stop abuse). When you request a guide or sign up for the newsletter we store your email address, optional first name, where on the site you signed up, any campaign tags in the page address, and the IP address of the request.
  • Record watches. When you ask to watch a record on a public record page, we store your email address, which record, whether you also asked for the newsletter, and when you asked, confirmed and stopped. We don't store a name or your IP address with it.
  • Technical data. Our hosting and security providers process IP addresses, browser type and the pages and API endpoints requested, to deliver the site and protect it from abuse. If the app hits an error in your browser we record the error message and the page it happened on.

2. How we use information

  • To provide the service: run screenings, keep your screening record, send monitoring alerts and produce reports.
  • To run your account, process payments and answer support requests.
  • To protect the service against abuse, fraud and unauthorized access, including rate limits and bot checks.
  • To understand, in aggregate, how the website is used and improve it.
  • To send the newsletter, if you asked for it. Every newsletter email has an unsubscribe link.
  • To email you when a record you asked to watch changes or is removed, after you confirm, at most once a day per record. Every one of these emails has a link to stop.
  • To comply with law and respond to lawful requests.

We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not use your screening inputs to train AI models.

3. Service providers (subprocessors)

These companies process information on our behalf to run the service:

  • Cloudflare — Hosting, network, security and bot checks (Turnstile). Processes: all website and app traffic, IP addresses, technical data.
  • Supabase — Database and sign-in. Processes: account information, screening inputs and results, messages.
  • Stripe — Payments and subscription billing. Processes: billing details, payment card data (held by Stripe).
  • Resend — Account, alert, record-watch and contact-form email. Processes: email addresses and email content.
  • Google — Website analytics (Google Analytics, via Google Tag Manager); Google sign-in if you choose it. Processes: pages visited, device and browser data, cookie identifiers; your Google account name and email for Google sign-in.
  • OpenAI — Plain-language match explanations, only when you ask for one in the app. Processes: the name you screened and the matched list record.
  • Sendy (self-hosted) — Newsletter mailing list. Processes: email address, optional first name, signup source.

We also disclose information when the law requires it, or to protect our rights, our users or the public. If Kleerance is sold or merged, information may transfer to the new owner under this policy.

4. Cookies, local storage and analytics

Section last updated 2026-10-21.

Your choice. If you're in the United Kingdom, the European Union, the wider European Economic Area or Switzerland (based on the country of your connection), Google Analytics stays off until you choose "Accept analytics". If we can't tell where you are, we treat you the same way. Everywhere else, Google Analytics is on by default; if your browser sends a Global Privacy Control signal, we treat that as "off" until you choose otherwise. Wherever you are, you can change your choice at any time from , also linked at the bottom of every page. We don't use advertising or remarketing cookies.

Strictly necessary

These are needed for the site to work, so they don't ask for consent.

  • kleerance_consent (cookie, 12 months) remembers your cookie choice, so we don't ask on every page.
  • klr_home_anon (cookie, 24 hours) and klr_wallet_anon (cookie, 30 days) are signed counters for the free search limits on the homepage screener and the free wallet check. They hold only a count and an expiry time.
  • Sign-in session (your browser's local storage, not a cookie). When you sign in, our authentication provider (Supabase) stores your session token in local storage. It is removed when you sign out.
  • Screens in progress (your browser's session storage, not a cookie). In the app, the last search in a tab is kept in that tab's session storage so it survives a page reload, and a name you screened on the homepage before signing up is carried to the app the same way (for up to an hour). It is cleared when you close the tab or sign out.
  • Bot checks. Some forms (contact, newsletter, guide downloads, record watches) use Cloudflare Turnstile, which runs in a frame from challenges.cloudflare.com and evaluates signals from your browser to tell people from bots. See Cloudflare's Turnstile privacy addendum for what it processes.

Analytics (only with your consent where consent is required)

  • Google Analytics, loaded through Google Tag Manager. It sets first-party cookies to count visits and see which pages are used: _ga and _ga_*, which by Google's defaults last up to 2 years. Where consent is required, Google Tag Manager isn't loaded at all until you accept. If you later turn analytics off, we delete these cookies from your browser where the browser allows it.

The names and details you screen are never sent to Google Analytics or any advertising tool. Screened names don't appear in page addresses, so they aren't captured by page-view analytics.

Our own page-view counts (no cookies)

We also count page views on our own servers without cookies or local storage. For each view we record the page path, the referring site, a country derived from your connection, and an anonymous identifier that changes every day and can't be traced back to you. We don't store your IP address for this.

Other services

  • Stripe. Stripe's checkout and billing pages, which you reach only when you pay, set their own cookies for fraud prevention.
  • Google sign-in. If you choose to sign in with Google, Google's own pages use Google's cookies.

5. How long we keep information

  • Account information and screening records: for as long as your account is open, so the record of each check stays available to you. When you ask us to delete your account, we delete it and its screening records, except information we must keep for legal, tax or accounting reasons.
  • Contact-form messages: for as long as needed to handle the request and any follow-up.
  • Guide download links: links expire after 7 days; the request record (email, IP address) is kept with our newsletter consent records.
  • Newsletter: until you unsubscribe, after which we keep only what's needed to honor the unsubscribe.
  • Record watches: a request you don't confirm is deleted after 7 days. A confirmed watch is kept until you stop it; after that we keep the row for 90 days, as a record that you stopped, then delete it.
  • Hosting logs and analytics: for the periods set by our providers.

If you screen people or companies for regulatory reasons, you may have your own record-keeping obligations. Export screening records you need before closing your account.

6. Security

Traffic is encrypted in transit (HTTPS). Account data is separated per account in the database, and administrative access is limited. No system is perfectly secure; see Security & data for details. If you think your account has been compromised, contact us.

7. Where information is processed

Kleerance is operated from the United States. Our providers may process information in the United States and other countries, where data-protection laws may differ from those where you live.

Screening record verification. Each PDF screening record you issue carries a record ID and QR code. Anyone who has that ID can open the record's verification page at kleerance.com/verify. Depending on the setting on your Records page, that page shows either the organization name on your account, the name or address screened, the result and the list dates, or only that the record is genuine, when it was issued and its hash. It never shows email addresses or the names of your users.

8. Your choices and rights

You can change some account details in the app, unsubscribe from the newsletter using the link in any newsletter email, stop a record watch using the link in any record-watch email, and turn analytics cookies on or off in Cookie settings (or block them in your browser). Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal information, and to object to or restrict some uses. To make a request, use the contact form and choose "Privacy or data request", writing from the email address on your account if you have one. We may need to confirm your identity before acting on a request. We won't treat you differently for making one.

If you are screened by one of our customers (for example, as a supplier or consignee), that customer decides what to screen and is responsible for that data. Please contact them first; we'll help them respond.

9. Not a consumer reporting agency

Kleerance is not a consumer reporting agency, and its results are not consumer reports under the U.S. Fair Credit Reporting Act (FCRA). The service must not be used to decide a person's eligibility for credit, insurance, employment, housing or any other purpose covered by the FCRA. See the Terms of Service.

10. Children

The service is for business use and is not directed at children under 16. We don't knowingly collect their information.

11. Changes to this policy

We'll post any change here and update the "Last updated" date. If a change is material, we'll also tell account holders by email or in the app before it takes effect.

12. Contact

Questions about this policy or a privacy request: use the contact form.