Home / Privacy
Legal
Privacy policy
What we collect when you sign up for and use WhichSitesUse, why we collect it, who else handles it, and how to get a copy of it or have it deleted.
Effective November 19, 2026.
// 01 Who we are
Who we are
WhichSitesUse is run by Disco Shrimp Company, LLC, a Delaware limited liability company ("we", "us"). We decide what personal information the service collects and what it's used for. You can reach us at andrew@discoshrimp.lol or by post at Disco Shrimp Company, LLC, 245 N Highland Ave NE, Suite 230, Atlanta, GA 30307, USA.
This policy covers the website at whichsitesuse.com, the account pages, the MCP server and the REST API. Our terms of service cover how you may use the service.
// 02 The short version
The short version
To give you an account we need your email address. To stop people farming the free credits we also record the IP address and a hashed browser fingerprint from your sign-up, and to bill you and show you what you've spent we keep a record of each API call your keys make. Card details go to Stripe and never reach us.
We don't sell personal information, we don't run ads, and the marketing site has no analytics or tracking cookies. The website and technology data the service sells is about public websites, not about you.
// 03 What we collect
What we collect and why
Your account
Your email address, the email's domain, a normalized copy of the address (lower case, with +tags removed, and dots removed for Gmail) that we use to tell whether two sign-ups are the same inbox, when you verified it, your plan and its renewal date, and whether the account is active or suspended. We use these to run your account, sign you in and bill you.
Sign-up checks
When you sign up we record your IP address and a browser fingerprint. The fingerprint is a hash your browser computes from its user agent, language settings, screen size and color depth, time zone, number of processor cores, platform and a small canvas drawing. Your browser sends only the hash, and our server hashes it again with a secret key before storing it. We use the IP address, its network (the first 24 bits for IPv4, 48 for IPv6) and the fingerprint hash only to decide whether to give the free credits and to spot one person opening several accounts.
The sign-up form uses Cloudflare Turnstile to check that a person, not a bot, is filling it in. Turnstile receives your IP address and information about your browser from your device. When a sign-up is turned away (a disposable address, a failed bot check) or the free credits are held back, we record the type of event with the IP address, network, fingerprint hash and email domain. We use these records only to prevent fraud and abuse of the free credits.
API keys and sign-in
We store each API key only as a hash, with its first few characters so you can recognise it, its name, its monthly cap, and when it was created, last used and revoked. Sign-in links and session tokens are also stored only as hashes.
Apps you connect with OAuth
When an app such as Claude or ChatGPT registers with WhichSitesUse to let you sign in, we store the name it gives, the addresses it asks us to send you back to, how it authenticates, a hash of its client secret if it has one, and the IP address it registered from. When you approve it on the consent page, we record a short-lived, single-use authorization code (as a hash) with your account, the app, its return address, its security challenge and the monthly cap you chose. The approved connection is then stored like an API key, with the app's name, your cap, its usage and when it was last used, and its access and refresh tokens are stored only as hashes with their expiry and revocation times. We use these to let the app act for you within the limits you set, and to cut it off if you disconnect it or a token is misused.
What you do with the service
For every call made with one of your keys, over MCP or REST, we record the operation, the channel, the time, the credits it used, whether it worked and the error code if not, and the inputs you sent, such as the domain you looked up or the filters you searched with. We use this to charge credits, enforce caps, show you your usage, investigate abuse and fix problems.
Calls made without a key (the free technology search and counts) are rate limited by IP address. The service keeps that count only in the server's memory and doesn't write the address to the database. The sign-up and sign-in forms count emails per IP address the same way.
Payments
Payments are handled by Stripe. When you first check out, we create a Stripe customer with your email address and account ID. Stripe collects your card and billing details on its own pages, and we only receive and store your Stripe customer and subscription IDs and what you bought. A checkout link from an agent can be paid by someone other than the account owner, and in that case Stripe collects that person's payment details.
Messages and emails
If you ask for free credits after the work-email check turned you away, we keep the message you write so a person can review it. We send account emails through Loops: verification and sign-in links, and the answer to a free-credit request. Loops receives your email address and what goes into each email, such as the link or the number of credits.
The website
The marketing site at whichsitesuse.com has no analytics and sets no cookies. Its pages, like the account pages, load fonts from Google Fonts, so your browser sends Google its IP address when you visit. A domain you type into the free lookup on the homepage goes to our API to be looked up.
Logs
Our servers write operational logs, with API keys and tokens stripped out, to diagnose errors. Our hosting provider, Render, also keeps short-lived request logs under its own retention rules. We keep our own logs for up to 30 days.
// 04 Website data
The data we sell is about websites
The lookups and lists come from HTTP Archive's public crawl of public websites and from the Chrome UX Report. They say which technologies a site's public pages load, how popular the site is in broad buckets, and how fast it is for real visitors in aggregate. They contain no names, emails or contact details, and the Chrome UX Report figures are aggregated across many visitors, so they don't identify anyone.
If you own a website and think something we return about it identifies you personally, email andrew@discoshrimp.lol and we'll look at it.
// 05 How we use it
How we use it, and on what basis
We use your information to provide the service you signed up for: your account, sign-in, credits, billing and support. That's the contract between us. We use the sign-up checks, abuse records and usage records to keep the free credits for real new users and to protect the service, which is our legitimate interest in preventing fraud and abuse. We keep billing records because tax and accounting law requires it.
We email you about your account, such as sign-in links and replies to your requests. We don't send marketing email from this service today, and if we start we'll ask first where the law requires it.
We don't sell or share your personal information for advertising, and we don't use it to make decisions about you that have legal or similarly significant effects. The free-credit check is automated, and you can ask a person to review it from the free-credit request page. Where the GDPR applies, we rely on performing our contract with you to run your account, on our legitimate interest in preventing fraud and abuse for the sign-up checks, and on legal obligations for billing records.
// 06 Processors
Who else handles it
These companies process data for us to run the service. None of them may use your personal information for their own purposes under our agreements with them.
| Provider | What for | Personal information involved |
|---|---|---|
| Render | Hosting the website, the API and the database | Everything stored about your account and usage |
| Stripe | Payments, invoices and the billing portal | Email, account ID, payment details you give Stripe |
| Loops | Sending account emails: verification, sign-in and free-credit request answers | Email address and the contents of each email |
| Cloudflare | The Turnstile bot check on sign-up, and storage (R2) for the monthly website dataset | IP address and browser data for Turnstile; the dataset holds no account data |
| BigQuery and Cloud Storage to build the dataset from public data, and Google Fonts | No account data; your IP address when your browser loads fonts |
These providers are based in the United States, and so are we, so your information is processed there. Where information about EU or UK users is transferred to the United States, we rely on our providers' safeguards for those transfers, such as standard contractual clauses or the Data Privacy Framework.
// 07 Retention
How long we keep it
Some things expire on their own: a sign-up link after 24 hours, a sign-in link after 30 minutes, a signed-in session after 30 days and a checkout link from an agent after 7 days. For connected apps, an authorization code expires after 10 minutes, an access token after an hour and a refresh token after 90 days, and each refresh replaces the old token.
We keep your account, keys, connected apps and credit history for as long as the account is open, and delete them within 30 days after you ask us to close it. We keep usage records for 12 months, sign-up check and abuse records for 24 months, and billing records for 7 years to meet tax rules. Free-credit decisions are kept for as long as we need to stop the same person claiming them twice, which is up to 3 years after the account is closed.
// 08 Your rights
Your rights
Wherever you live, you can ask us for a copy of the personal information we hold about you, ask us to correct it, ask us to delete it and close your account, or object to how we use it. If you're in the EU, the UK or a similar jurisdiction, you can also ask us to limit how we use it, ask for it in a portable format, and complain to your data protection authority. If you're a California resident, you have the right to know what we collect and why, to delete it, to correct it, and not to be treated differently for using those rights. We don't sell or share personal information as California law defines those terms.
There's no self-serve account deletion yet. To make any of these requests, email andrew@discoshrimp.lol from the address on your account. We'll confirm the request comes from you by replying to that address, and we'll answer within 30 days. You can name an authorized agent to make a request for you, and we'll ask for proof that you've authorized them.
// 09 Cookies
Cookies
The marketing site sets none. The sign-up, sign-in, account and app consent pages set two, both needed for those pages to work, and none for analytics or ads.
| Cookie | What it does | Lasts |
|---|---|---|
| wsu_session | Keeps you signed in to your account page | 30 days, or until you sign out |
| wsu_anon | Protects the sign-up and sign-in forms from cross-site request forgery before you're signed in | 1 day |
Stripe's checkout and billing pages and Cloudflare's Turnstile check may set their own cookies under their own policies.
// 10 Security
Security
The service runs over HTTPS, and API keys, sign-in links, session tokens and connected apps' tokens are stored only as hashes, so a copy of our database wouldn't reveal them, and there are no passwords to leak. No system is perfectly secure, and if a breach affects your information we'll tell you as the law requires.
// 11 Children
Children
WhichSitesUse is a business tool and isn't meant for anyone under 18. We don't knowingly collect information from children, and if you think a child has signed up, email us and we'll delete the account.
// 12 Changes
Changes and contact
If we change this policy, we'll update the date at the top of this page, and for material changes we'll email account holders before the change takes effect. Questions or requests go to andrew@discoshrimp.lol, or by post to Disco Shrimp Company, LLC, 245 N Highland Ave NE, Suite 230, Atlanta, GA 30307, USA.