Privacy Policy
Last updated
This policy explains what wtsp.dev ("we", "us") collects and why. It covers visitors to this website, customers of the API and CLI, and the people whose phone numbers are looked up. Contact: hello@wtsp.dev.
If your number was looked up
The service answers lookups of phone numbers. For a number on WhatsApp, an answer can include what WhatsApp shows publicly for it:
- whether the number is on WhatsApp, and whether it is a personal or business account;
- the about text and profile photo, unless your WhatsApp privacy settings hide them from strangers;
- the country WhatsApp reports, and how many devices are linked to the account;
- for business accounts, the business profile: name, description, categories, email, websites, address, opening hours and linked Facebook page.
We only see what WhatsApp shows to someone who doesn't have your number saved. Personal accounts publish no name, and we don't add one. We keep the latest answer for each number so repeat lookups can be answered quickly; it's refreshed when it's more than 7 days old. Profile photos are stored so the links in answers keep working.
To opt out: email hello@wtsp.dev with your number. We may ask you to confirm the number is yours, for example by sending a WhatsApp message from it. We'll then delete the profile and photo we hold for it and stop answering WhatsApp lookups of it. The number itself stays on our block list, because that list is how we keep refusing lookups.
If you visit the website
- Analytics: we use Google Analytics to count visits and see which pages people read. It sets cookies and receives your IP address and browser details.
- Free lookups: the playground's free lookups use Cloudflare Turnstile, a captcha that checks you're not a bot. To count your free lookups, we store a one-way fingerprint of your IP address (never the address itself) and delete it after that day.
- Hosting: the site runs on Vercel, which keeps short-lived request logs, including IP addresses, to run and protect the service.
If you buy lookups
- API keys: we store a fingerprint of each key (never the key itself), its first few characters, its credit balance, when it was created and when it was last used.
- Purchases: for each credit purchase we store the amount, the blockchain network, the transaction hash and the paying wallet address. Blockchain payments are public by nature: anyone can see them on the network they were made on.
- Lookups: the numbers you send are used to answer your requests. We keep the answers as described above.
- Payments: per-request payments in USDC on Base are processed by Coinbase's payment service.
We don't ask for your name or email to use the service. If you email us, we keep the conversation to answer you.
Why we use this data
- To run the service and answer the lookups you pay for.
- To prevent abuse, such as getting around the free lookup limit.
- To understand how the website is used, and improve it.
- To keep records of payments.
We don't sell information about our visitors or customers.
Who else handles it
The companies that run parts of the service for us: Vercel (hosting), Supabase (database), Cloudflare (captcha), Google (analytics) and Coinbase (payments). They handle data only to provide their service to us. They may store it outside your country.
How long we keep it
- Free lookup fingerprints: deleted after the day they were used.
- API keys and purchase records: as long as the key exists, and as long as payment records must be kept.
- Lookup answers and photos: the latest answer for each number, and its photo, until the number's owner opts out.
- Block list entries: for as long as the service runs.
Your rights
Depending on where you live, you can ask for a copy of the data we hold about you, ask us to correct or delete it, or object to how we use it. Email hello@wtsp.dev. You can also complain to your local data-protection authority.
Children
The service is for businesses and developers. It is not meant for anyone under 18.
Changes
We'll update this page when what we collect changes. The date at the top shows the last change.