Privacy

No advertising scripts, no profile of you, and no cookies unless you start signing in to /insights/. This page lists the few things that do happen — including the search text this site records.

Ludbee is a static site. Apart from the two essential sign-in cookies for /insights/ described below, it sets no cookies, runs no advertising scripts, and does not build a profile of you. This page describes everything that happens to data when you visit, in the order it happens.

What is stored on your device

Three things. The first two are preferences, kept only if you change them: your choice of light, dark or midnight theme, saved in your browser's local storage under the key ludbee-theme, and the width you drag the browse sidebar to, under ludbee:rail-width. Neither leaves your browser or is sent to us or to anyone else.

The third is a random session id — a dozen characters, generated in your browser, stored under ludbee:session in session storage, which your browser discards when you close the tab. It is attached to the search records described below so that several searches in a row can be read as one train of thought. It is not derived from anything about you, it does not persist between visits, and it identifies nobody.

Clearing your browser's site data removes all three. No cookies are set unless you start signing in to /insights/ — see Signing in to /insights/. Nothing else on the site has a login or an account.

This site records what you type into its search box. We would rather say that plainly at the top than have you find it in a network tab.

When a search settles, the site sends to its own server: the text you typed, exactly as you typed it; which filters and sort order were in effect; how many results came back; and which records were on screen. If you open a company, it records which one and where it sat in the list. Each record carries the random session id above and the time it arrived.

What is not recorded: your name, your email, any account or cookie identifier (the records carry neither), your location, your IP address or your browser's user-agent string. The records go to this site's own server on this domain and to no one else — no third-party analytics service is involved, and nothing is sold or shared.

Why we do it. Searches that return nothing are the most useful thing anyone can tell us: they name what a directory of AI companies ought to cover and does not. Reading real searches is how the site learns what to add and how to answer better. Aggregate is not enough for that — the words matter, so the words are what is kept.

Records are held by Cloudflare Analytics Engine, our host, and expire automatically after three months. If you would rather not be included, blocking this site's scripts stops it, though search needs those scripts, so it stops too. A private window does not stop it.

What the server sees

This site is served by Cloudflare. Like any web host, Cloudflare's network receives the ordinary technical information every HTTP request carries — your IP address, the page requested, your browser's user-agent string and the time — and processes it to deliver the page and to protect the site from abuse. That processing is Cloudflare's, under its own terms as our hosting provider; we do not keep our own copy of it and do not have a database of visitors. The databases we keep are the sign-in one described under Signing in to /insights/, the shortlist submissions, and the search records.

Of what you do while browsing, the search records described above are the one thing we keep, and they carry none of that technical information — no IP address, no user-agent, no location. They are a list of what was searched for, not a list of who visited.

Analytics

This site counts page views with Cloudflare Web Analytics. It is cookieless: no identifier is stored in your browser, so it cannot recognise you on a return visit, and it does not track you across other sites.

What it tells us: which pages are visited and roughly how many times, which site referred a visit, the country it came from, the browser, operating system and type of device, and how fast pages loaded. It does not tell us who visited, does not fingerprint your browser or device, and does not build a profile that follows you anywhere else.

This data is Cloudflare's aggregate reporting, not a per-visitor record we hold ourselves — the same relationship this page already describes for Cloudflare's role as our host.

Newsletter

There is no newsletter signup in any page's footer today, and no newsletter has been sent. The shortlist report form described below does collect an email address, for a different reason — see that section. The one other place a newsletter comes up is the unticked box offered when you first sign in to /insights/; it records your choice and nothing is sent yet — see Signing in to /insights/.

If a newsletter signup is added, this page will name the provider that stores the list, say what is stored (an email address and the date it was given), and say how to unsubscribe — before the form goes live, not after.

Shortlist reports

The shortlist report form collects what you type into it — what you need an AI tool to do, your email address, and whichever of team size, budget, integrations, constraints and technical skill you choose to fill in; every field but the first two is optional.

Unlike the newsletter or the correction form, this one is stored by us directly, not handed to a third-party provider: the record goes to this site's own server on this domain and into Cloudflare Workers KV, a storage service on the same host that serves the site. Nobody but the person writing your report reads it.

What it is for: a person reads what you wrote, checks it against the directory, and emails back a short shortlist within 48 hours. Nothing here is automated, and nothing here changes any figure or ranking on the site — see Disclosure.

To have a submission corrected or deleted, use the address on the contact page and mention the email you submitted with.

Signing in to /insights/

/insights/ is the one part of this site you sign in to, and the only way in is Google sign-in. Nothing else on the site has a login.

What we store about a reader who signs in: the email address Google gives us (only once Google has verified it), the date you signed up, whether you chose the newsletter and when you made that choice, and a plan field that says free. We also store the identifier Google gives your Google account, so we recognise you next time even if the address changes. Your sessions are stored only as a one-way hash, so the stored value cannot be turned back into a working sign-in.

What we do not store: your name, your photo, your contacts, or anything else from your Google account. Google's sign-in is asked for your email and basic profile, so its consent screen will mention both; from Google's answer we keep the verified email and the identifier, and discard the rest. The email is never put in a web address, and it is not joined to the search records described above.

Cookies. Two essential cookies, used for nothing but signing you in and keeping you signed in. __Host-lb_oauth is set when you start signing in (Continue with Google) and lasts at most ten minutes; it ties Google's reply to your browser. __Host-lb_session is set when sign-in completes and keeps you signed in for 30 days. Both are sent back only to ludbee.com, and because they cover the whole site your browser sends them with requests to any page here, not only /insights/. Neither is used for analytics or advertising, and nothing else on the site sets a cookie.

The newsletter is opt-in. The first time you sign in you are offered a box, unticked, that says you would also like the newsletter; we store your answer and the time. No newsletter has been sent, and ticking the box does not promise one. You can change your newsletter choice at any time from the account menu on /insights/, or by writing to hello@ludbee.com.

Deleting your account. Delete my account in the account menu on /insights/ removes your email address, your sign-up date, your newsletter choice and the time you made it, your plan, your Google account identifier and every session, all at once. Sign out in the same menu ends only the session in that browser. Deleted records can remain in our hosting provider's automatic database backups for up to 30 days before they expire.

Who else is involved. We do not sell or share your email address. Google provides the sign-in, under its own terms. Cloudflare, the host described above, also hosts the database that holds this information.

The correction form

There is no correction form on this site today. Corrections and additions arrive by email, and nothing beyond what you choose to write in one is collected.

When a form is added it will be hosted by Tally, a third-party form provider, and this page will say so — what goes to Tally, what reaches us, and that email remains an alternative — in the same change that adds it.

Company and product records link out to the companies' own websites. Those sites are not ours and have their own privacy practices; this policy stops at the edge of this domain.

Children

This site is a business directory. It is not directed at children and does not knowingly collect information from children. Beyond the search records described above, the shortlist submissions and any email you send us, the only personal data it holds is what signed-in /insights/ readers provide, described under Signing in to /insights/.

Changes, and who to ask

If this policy changes, the change is published here. Because the site collects so little, most changes will be additions — an analytics script, a newsletter — and each one is described before it is switched on.

Questions about this policy, or a request to see or delete anything you have sent us: hello@ludbee.com.

This site is operated by Jaegeun Kim, in the State of Maryland, United States.