Privacy Policy
What personal data Heedeo collects on heedeo.com and app.heedeo.com, what it processes for its customers, who it shares data with, how long it keeps it, and your rights.
Effective November 6, 2026 · Also as markdown: /privacy.md
Heedeo helps websites and apps spot fraud and abuse at signup, login and other actions. Heedeo is provided by Heedeo, Inc. ("Heedeo", "we", "us"). This policy explains what personal data we collect, why, who we share it with, how long we keep it and what rights you have.
It covers:
- heedeo.com, our website, and the call requests people send through it;
- app.heedeo.com, where our customers sign in, manage their workspaces and read our documentation;
- email and calls with us.
Section 4 explains what happens to data about the people who use our customers' websites and apps. For that data, our customer decides what is collected and why, and we process it on their behalf.
1. Who we are
Heedeo, Inc. provides Heedeo. It is the controller of the personal data this policy describes, except the data in section 4.
Contact us about privacy at barun@heedeo.com (Barun Pandey, CEO) or arjan@heedeo.com (Arjan Chaudhary, CTO).
2. Visiting heedeo.com
Analytics. We count page views and link clicks with PostHog. The site sets no cookies. It keeps an anonymous ID in your browser's local storage, and any utm_ campaign tags in session storage for the length of your visit. Each event carries the page's address, the page that linked to it and those campaign tags. PostHog receives your IP address with each event, as any web server does. If your browser sends Do Not Track or Global Privacy Control, the site sends nothing to PostHog and stores nothing. We use the counts to see which pages and links people use. There are no advertising trackers.
Call requests. When you ask for a call or for access, through the form on the site, POST /api/book or the older POST /api/waitlist, we keep:
- your email address;
- your site, and your answer to "What are agents doing on your site?", if you give them;
- whether you asked to be a design partner, if you did;
- whether a person or an AI agent sent the request, and the agent's name if it gave one or we recognized it;
- whether the request carried Web Bot Auth signature headers (only whether they were there);
- the request's status (pending or confirmed), and when it was made, confirmed and last sent by an agent.
A request an agent sends for you stays pending until you confirm it, by sending it yourself or when we check with you. We use call requests only to contact you about access to Heedeo.
Booking a call. Calls are booked on Cal.com, which receives the name, email address and notes you enter there.
The public endpoints. /api/visitor, /api/decide and /api/policy compute an answer and return it. They don't store what you send. To check signatures, /api/visitor keeps agent operators' public key directories and recently seen signatures in memory for a short time.
Hosting. Cloudflare hosts heedeo.com and stores call requests in its D1 database. Like any web host, it processes every request to the site, including your IP address.
3. Using Heedeo as a customer
When you or your team use app.heedeo.com:
Your account. Your email address, and your name if you give it. If you sign in with Google, Google shares your name, email address and profile picture with us. Sign-in runs on Clerk, which keeps these details and your sessions, including each session's browser, IP address and approximate location, to keep accounts secure.
Your workspaces. Workspace names and settings, each workspace's contact email, your API keys (we store secret keys only as hashes), the domains you connect, your team's labels and notes, and daily counts of identifications, events and flags. We use them to run the service and show you your results.
Cookies on app.heedeo.com. Clerk's cookies keep you signed in. Our workspace cookie remembers which workspace you last opened, for up to 400 days. Both are needed for the site to work. app.heedeo.com has no analytics or advertising cookies.
Logs. Our servers write one line for each request, without the query string, API keys, email addresses, or IP addresses beyond their network prefix.
Payments. We don't take payments yet. Before we do, we'll name our payment provider here.
Why we use this data, and our legal basis under the GDPR, for people in the European Economic Area, the UK and Switzerland:
| Purpose | Legal basis |
|---|---|
| Providing Heedeo under our Terms of Service: your account, sign-in, workspaces and support | Performance of a contract (Article 6(1)(b)) |
| Keeping accounts and the service secure, and preventing abuse of Heedeo itself | Legitimate interests (Article 6(1)(f)) |
| Telling you about changes to the service, our terms or your account | Performance of a contract, or legitimate interests |
| Improving the service, from counts that identify no one | Legitimate interests |
| Answering call requests and emails, and counting page views on heedeo.com | Legitimate interests |
| Keeping records the law requires, such as tax records once we bill | Legal obligation (Article 6(1)(c)) |
Where we rely on legitimate interests, you can object (section 8).
4. People who use our customers' sites and apps
Our customers add Heedeo to their own websites and apps to protect signups, logins and other actions. For the data this collects about their users, the customer is the controller and we are their processor. We use the data only to provide Heedeo to that customer, on their instructions and under our agreement with them. The customer's privacy policy applies to it. If you want to know what a service holds about you, or want it deleted, ask that service. We help our customers answer these requests.
For each customer, Heedeo processes:
- Browser and device characteristics that Heedeo's script reads on the customer's page, such as screen, graphics hardware, language, time zone, platform and signs of automation. Depending on the customer's settings, also fonts, canvas rendering and audio processing.
- A visitor cookie: a first-party cookie on the customer's own domain that recognizes the browser on later visits, with copies in the browser's storage. Browsers keep it for up to 400 days.
- Network data: the IP address, used during the request and then kept as its network prefix and a salted hash of the full address, and what our providers IPinfo and Spur report about the network, such as its operator, whether it is a VPN, proxy, Tor exit or hosting provider, how many devices share it, and its country, region and city.
- Request details: the browser's user agent, languages and client hints.
- Identifiers the customer sends, such as an email address, account ID, phone number or payment card fingerprint. We keep them as hashes, salted differently for each customer, not as the raw values. For an email address we also keep its domain, and a reason may name a role address's first part, such as "admin".
- Facts the customer sends, such as whether an email or phone number was verified, how old an account is and the results of card checks.
- Results: risk scores and the reasons for them, links between browsers that look related, flags, and the customer's own labels and notes.
Hashed values are still personal data, and we treat them that way.
The customer uses the results to decide what happens next, for example whether a signup goes through or needs another check. Heedeo does not make that decision. If you think a service treated you unfairly, contact that service.
We don't use this data for advertising, we don't sell it, and we don't combine one customer's data with another's. We compute counts from it that identify no one, such as how many identifications each customer made in a day, to run and improve Heedeo.
How long it is kept depends on the customer's settings. Our documentation lists every record and how long it is kept: https://docs.heedeo.com/privacy#what-heedeo-keeps-and-for-how-long.
5. Who we share data with
We share personal data only with the providers that help us run Heedeo, each under a contract that limits what it may do with the data:
| Provider | What for | Personal data |
|---|---|---|
| Railway Corporation (United States) | Hosting the Heedeo service and its database | Everything the service holds |
| Cloudflare, Inc. (United States) | Hosting heedeo.com and its database; the network in front of app.heedeo.com and our API; serving our script from customers' own hostnames | Requests in transit, including IP addresses; call requests |
| Clerk, Inc. (United States) | Sign-in to app.heedeo.com | Our customers' team members: names, email addresses and sessions |
| Google LLC (United States) | Sign in with Google, if you choose it; our email (Google Workspace) | Your Google name, email address and picture; email you send us |
| PostHog, Inc. (United States) | Analytics on heedeo.com | Page views and clicks, with an anonymous ID and your IP address |
| Cal.com, Inc. (United States) | Booking calls | The name, email address and notes you enter |
| IPinfo Inc (United States) | Information about the network an IP address belongs to | The IP addresses of our customers' users (section 4) |
| Spur Intelligence Corporation (United States) | Information about the network an IP address belongs to | The IP addresses of our customers' users (section 4) |
| Superlative Enterprises Pty Ltd, which runs Have I Been Pwned (Australia) | Whether an email address appeared in known data breaches, only for customers who turn it on | The email addresses of our customers' users (section 4) |
To check an email address's mail servers and how old its domain is, the service also asks public DNS and the public domain registries about the domain only, never the full address.
We may also disclose personal data when the law requires it, to protect someone's safety or our rights, or as part of a merger, acquisition or sale of our business. In that last case, we'll tell you before your data becomes subject to a different privacy policy.
We don't sell personal data, and we don't share it for cross-context behavioral advertising.
6. International transfers
Heedeo, Inc. is a United States company. We and our providers process personal data in the United States and other countries. When personal data from the European Economic Area, the UK or Switzerland goes to a provider in a country without an adequacy decision, we rely on the provider's certification under the EU-US Data Privacy Framework (with its UK and Swiss extensions), or on the European Commission's Standard Contractual Clauses, with the UK Addendum and the Swiss amendments where they apply.
7. How long we keep data
- Your account and workspaces: while your account is open. When it closes, we delete them within 30 days, except what the law requires us to keep.
- Call requests: while we're in touch with you about Heedeo. Ask us and we'll delete yours.
- Email: for as long as we need it for the conversation and our records.
- Analytics events: for as long as they help us understand how the site is used.
- Data about our customers' users (section 4): as the customer's settings and our agreement with the customer allow.
8. Your rights
You can ask us for a copy of your personal data, and ask us to correct or delete it. Email barun@heedeo.com or arjan@heedeo.com. We reply within one month, and we may ask you to confirm your identity first.
In the European Economic Area, the UK and Switzerland, you also have the right to restrict or object to our processing, including where we rely on legitimate interests, to receive your data in a portable format, and to withdraw any consent you gave. You can complain to the data protection authority where you live or work, or where you think the problem happened. We'd welcome the chance to help first.
In US states with privacy laws, such as California, Colorado, Connecticut and Virginia, you can ask to know, access, correct and delete your personal data, and to opt out of its sale or its sharing for targeted advertising. We don't sell it or share it that way. You may use an authorized agent. If we turn down a request, you can appeal by replying to our answer. We won't treat you differently for using these rights.
We offer these rights to everyone, wherever you live.
If you use one of our customers' services, see section 4 and ask that service first. If you ask us, we'll tell you how to reach the service, or pass your request on to it if we can tell which service it concerns.
9. Security
We protect personal data with measures that fit what it is:
- encryption in transit (HTTPS) everywhere;
- identifiers hashed on arrival, and API secret keys stored only as hashes;
- a production database with no public address, reached only by Heedeo's founders;
- each customer's data kept apart from every other customer's;
- multi-factor sign-in on every infrastructure account.
No system is perfectly secure. If a breach affects your personal data, we'll tell you, and the authorities, as the law requires.
To report a security issue, email arjan@heedeo.com.
10. Children
Heedeo is a service for businesses. It isn't meant for children, and we don't knowingly collect personal data from anyone under 16 for our own purposes. Our customers decide who may use their own services.
11. Changes to this policy
We'll post any change to this policy on this page, with a new effective date. If a change is significant, we'll also email account holders before it takes effect.
12. Contact
Heedeo, Inc., a Delaware corporation. Email barun@heedeo.com or arjan@heedeo.com.
Our Terms of Service: https://heedeo.com/tos.