privacy notice
updated
short version: you can read all of numptr without an account. we don't run analytics scripts, ad trackers or tracking cookies. we only collect personal data when you give it to us: your email if you sign up for the weekly, your details if you email us or pay for a sponsorship, and the basic technical data any website's host sees when you visit.
privacy.txt
numptr privacy --summary
cookies:none of our own # bar Cloudflare's bot check
ad trackers:none
analytics:none
email tracking:off # no open or click tracking in the weekly
data sales:never
# the long version is below. it's worth a skim.
who we are
numptr (numptr.com) is an independent directory that ranks AI tools for people who build with them. for the personal data described here, we're the "controller", which is the data protection word for the people who decide how and why it's used.
questions about your data, or want to use any of your rights: hello@numptr.com. sponsorship and billing: partners@numptr.com.
what we collect and why
here's everything, what it's for, and the legal reason we're allowed to use it under the UK GDPR and the EU GDPR.
| what | why | legal basis |
|---|---|---|
| visiting the site: your IP address, browser and device details, the page you asked for and when | to deliver pages, keep the site up and block attacks. our host, Cloudflare, handles this. we don't keep our own visitor logs and we don't build profiles of visitors. | legitimate interests (running a secure website) |
| the numptr weekly: your email address, when you signed up, and whether you're subscribed | to send you the newsletter you asked for. we've switched off open and click tracking, so we don't see whether you opened it or what you clicked. | consent. withdraw it any time with the unsubscribe link in every email. |
| emailing us: your email address, name if you give it, and whatever you write | to reply. if you're claiming a tool's listing, we also use your work email and role to check you're really behind the tool. | legitimate interests (answering you), or steps towards a contract if you're asking about a paid service |
| sponsoring numptr: your name, email, company, billing details and what you bought. card details go to Stripe, never to us. | to take payment, run your sponsored week, send your copy and results, and keep the records the law requires | contract, and legal obligation (tax and accounting records) |
| search data from Google: Google Search Console shows us totals of how numptr appears in Google search (searches, clicks, pages) | to see which pages people find useful. it's summary data from Google's own search, and it doesn't tell us who you are. | legitimate interests (improving the site) |
affiliate links. some links to tools are affiliate or referral links. when you click one you leave numptr, and the other site (or its affiliate partner) may set its own cookies so it can credit us if you sign up or buy. that happens on their site, under their privacy policy. we usually only get totals, like how many sign-ups or how much commission, not who you are. affiliate links never change a rank.
sponsor reports. if we tell a sponsor how many clicks their spot got, it's a number. we never tell them who clicked.
badges on other sites. the numptr badges that tools put on their own sites load an image from numptr.com, so Cloudflare sees that request like any other page visit. the badge doesn't set cookies or run code.
we don't use your data for automated decisions that affect you, and we don't sell it, rent it or use it for advertising.
cookies and storage
the main site doesn't set any cookies of its own. one thing is saved in your browser: the homepage remembers which picker view you chose ("not a clue" or "yeah, obviously") using your browser's local storage. it stays on your device, we never see it, and clearing your browser data removes it.
Cloudflare may set a strictly necessary security cookie if it needs to check that a visitor isn't a bot. it's there to protect the site, not to track you, so we don't need to ask first and there's no cookie banner.
who else handles it
we use a small number of companies to run numptr. they handle data for us under contract and only for the jobs listed here:
- Cloudflare: hosts the site, delivers pages and protects it from attacks. when the community opens, also its database and bot checks (Turnstile).
- Resend: stores the newsletter list and sends the weekly. when the community opens, also sign-in emails.
- Stripe: takes sponsorship payments. Stripe also uses payment data for its own fraud prevention and legal duties, under its own privacy policy.
- Google: Search Console (search totals, as above), and it hosts our partners@numptr.com inbox.
- GitHub: only if you choose "sign in with GitHub" once the community opens.
we'll also share data if the law requires it, for example a valid court order, or to protect people from serious harm.
where it's stored
some of these companies store or process data outside the UK and the EEA. the newsletter list sits with Resend in the US, and Cloudflare serves the site from data centres around the world, close to whoever is visiting. where data leaves the UK or EEA, we rely on the safeguards those providers offer, such as the UK and EU standard contractual clauses or the EU-US Data Privacy Framework and its UK extension.
how long we keep it
- newsletter: until you unsubscribe. after that we keep a note that you unsubscribed so we don't email you again by mistake. ask and we'll delete that too.
- emails to us: as long as we need them for the conversation and any follow-up, then we delete them.
- sponsorship and payment records: as long as tax and accounting rules require.
- visit data: kept by Cloudflare for a short time under its own retention rules. we don't keep a separate copy.
your rights
under the UK GDPR and the EU GDPR you can ask us to:
- show you the personal data we hold about you, and give you a copy
- correct anything that's wrong
- delete it
- limit how we use it, or object to us using it on the basis of legitimate interests
- hand it over in a format you can take somewhere else
- withdraw consent where that's what we rely on (for the weekly, the unsubscribe link does it in one click)
email hello@numptr.com. it's free, and we'll answer within one month. we may need to check it's really you before we hand anything over. if you're not happy with how we've handled your data, tell us first and we'll try to put it right. you can also complain to the UK Information Commissioner's Office (ico.org.uk) or the data protection authority where you live.
if you're in the US
we don't sell your personal information, we don't "share" it for cross-context behavioural advertising, and we don't do targeted advertising, as those terms are used in US state privacy laws such as California's. because we don't track you across sites, there's nothing to opt out of, and we treat browser opt-out signals such as Global Privacy Control as an opt-out anyway.
wherever you live, you can ask what we hold about you, ask us to correct it or delete it, and we won't treat you any differently for asking. email hello@numptr.com.
the community (not open yet)
we're building a numptr community where builders can show what they've made, what it's built with and what it costs. it isn't open yet. we'll update this notice before it opens, but here's how it's designed to work, so there are no surprises:
- accounts: you'd sign in with a one-time link sent to your email (via Resend), or with GitHub. with GitHub we'd get your GitHub id, username and avatar. sign-in links expire after 15 minutes.
- public by design: your handle, display name, bio, link, builds, the tools and costs you list, your likes and follows, and your chat messages are public. that's the point of the community, so only post what you're happy for anyone to see.
- cost averages: the monthly costs you list could feed anonymous "what people pay" figures on tool pages, only when at least three builds share costs for that tool. you'd be able to switch this off on any build.
- safety: we'd keep reports, moderation decisions and rate-limit counters to keep out spam and abuse. rate limits use a one-way scrambled (hashed) version of your IP address, never the raw address. Cloudflare Turnstile would check sign-ins and posts for bots.
- cookies: one strictly necessary cookie keeps you signed in for up to 30 days, plus a short-lived one during GitHub sign-in. no tracking or ad cookies.
- your controls: download everything we hold about you, edit it, or delete your account from your settings.
- age: you'd need to be 18 or over to join.
the legal basis would be our contract with you for running your account and showing what you post, and legitimate interests for safety, moderation and the anonymous cost figures. you can object to those at any time.
children
numptr is written for adults who build things. it isn't aimed at children, and we don't knowingly collect personal data from anyone under 13. if you think a child has given us their details, email hello@numptr.com and we'll delete them.
keeping it safe
the whole site runs over HTTPS, we collect as little as we can, and access to the services above is limited to the people who run numptr. no system is perfectly secure, but if something goes wrong that puts your data at risk, we'll tell you and the regulator when the law says we must.
changes
if we change how we use personal data, we'll update this page and the date at the top. if it's a big change, like opening the community, we'll say so on the site and in the weekly before it happens.
contact
privacy questions and requests: hello@numptr.com. sponsorship and billing: partners@numptr.com. see also the terms of use.