Privacy

Browsing

Browsing needs no account. We count page views and App Store clicks so developers can see how their page is doing. To count a visitor once per day without tracking them, we use a daily-rotating salt: the same person on two different days, or on two different apps, looks like two different people to us.

We set one cookie of our own for this, which expires at midnight UTC the day it is set. It holds a random identifier, never your name or email. We do not use advertising cookies. Your theme choice is remembered in your browser’s local storage and never sent to us.

Product analytics

We use PostHog to understand how the site is used and to catch errors: which pages are visited, which buttons are pressed, and what went wrong when a page fails. PostHog stores a random identifier in a cookie and in your browser’s storage so it can tell one visit from the next. Its requests go through our own domain, and it never receives the contents of forms.

When you are signed in, we tell PostHog your account’s identifier, email address, display name and role, so a problem you report can be traced. We do not use PostHog for advertising, and it does not share this data with advertisers.

What we store about visitors

• Which page was viewed, and whether its App Store or website link was clicked.
• The broad kind of place that sent you: a search engine, a social network, another site, another page here, or none. Not the full address.
• The country your connection comes from, as a two-letter code supplied by our network provider.
• What people search for here, without who searched.
• Anonymous page-speed measurements from about one visit in five.

We never store your IP address with these events. Raw events are deleted after 90 days. After that we keep only daily totals: counts per page, and the day’s most common search terms, none of which says anything about an individual visitor.

Accounts

We store your email address and the profile you choose to publish. If you submit apps, we also store the listings and media you upload. Passwords are hashed and never stored in readable form. You can sign in with a password or with Google. Google shares your email address, name and profile picture with us. If you sign in with Google using an address that already has an account here, the two are joined into one.

When you create an account, we record that you agreed to the Terms and this policy, when, and which version. If either changes in a way that matters, we ask again.

Signing in sets session cookies that keep you signed in. They are only readable by our servers and are removed when you sign out.

Upvotes and comments are tied to your account, which is how we make sure each account votes once. When you upvote, we also store a one-way code derived from your network address, so we can spot many votes coming from one place. The key that makes the code is deleted after two days, after which the code can no longer be matched to any address.

Claims

If you claim a page, we store your note, the evidence we checked (such as a code found on your website), and any work address you ask us to send a code to. We keep it as the record of what we decided and why.

Contact messages and removal requests

If you write to us through the contact form, we store your name, email address, the topic and your message, and link it to your account if you were signed in. We use it only to answer you, and keep it so a follow-up has its history. Ask and we delete it.

If you ask us to remove a listing, we store your name, email address, your relationship to the app and your message. We keep it as the record of what we decided and why.

Email

We send email through our provider, Email Bump, which processes your address only to deliver it. We record whether each message was sent, delivered or bounced, to spot delivery problems, and keep that record for 180 days. We do not track whether you open emails or click their links. Review decisions and account email are always sent; notification emails can be turned off in Settings or with the link in each one. If an address bounces permanently or marks our email as spam, we stop sending to it altogether.

Services that run the site

• Netlify hosts the website and serves every page.
• Cloudflare sits in front of the site to protect it from abuse, and supplies the country code. Its human check runs on the sign-in, sign-up, contact and removal forms; most people never see it.
• Convex runs our database and backend. Everything above is stored there.
• PostHog provides the product analytics described above.
• Email Bump delivers our email.
• Google, only if you choose to sign in with it.
• Anthropic’s Claude helps our editors draft “Listed by editors” pages. It only ever sees an app’s public App Store details, never anything about our visitors or account holders.

How long we keep things

• Raw visit events: 90 days. After that only daily totals remain.
• Email delivery records: 180 days.
• Moderation and account-security records: two years in our live records, so a decision can be explained if it is questioned. After that they move to a secure archive, which we keep.
• A deleted app: 30 days, in case it was a mistake. Then it is gone.

Your rights

From Settings you can export your account, profile, apps, launches, comments, votes and analytics as a single file. For anything else we hold about you, such as claims, contact messages or removal requests, write to us.

You can also delete your account there. Deletion takes effect after a 30-day grace period, during which you can change your mind. After that we remove your email address, name, profile details, picture and sign-in methods, and your apps come off the site. Your comments stay in their threads, shown as “Deleted account”, and your upvotes stay in the results they helped decide. Your profile address is kept so nobody else can take it over. Archived Launch Week results keep the app’s name and rank.

To ask anything about your data, use the contact form or write to our contact form.