Privacy

You don’t need an account. To count visits and clicks without tracking you, we:

• Compute a visitor code from your IP address and browser details using a random key that changes every UTC day and is deleted after the day ends. Codes from different days can’t be linked to each other, and once a day’s key is gone nobody, including us, can work out whose code it was.
• Use your IP address and browser details only in memory to compute that code. We never store them.
• Count each kind of event once per visitor code in a 30-minute window, and keep only counts.
• Keep raw events for 90 days. After that, only daily totals remain.
• Mark likely bots and a company’s visits to its own app, and leave them out of every count.
• Don’t store the text of your searches or AI requests with any of this.
• Keep the public view count on app pages honest by letting each network (your IP address, or its block for IPv6) add only a few views per app per hour. That counter uses the same daily key as the visitor code, so it can’t be linked across days, and it’s deleted after 2 hours.

To stop abuse, some actions (such as sign-ups, reports, votes and leaderboard updates) are counted per network for a short time using a keyed hash of your IP address. These counters are deleted after at most 7 days.

• When you describe what you need to the advisor, we keep the conversation’s text for up to 24 hours so it can follow up on your answers, then delete it.
• The advisor reads your text on our own servers. If we switch on a hosted AI model for it (Anthropic or GMI Cloud), the text is also sent to that provider to read your requirements; it never receives information about who you are.
• If you use AppFinder from an AI assistant (our MCP connector), the assistant sends us your request and we answer it. We don’t store the request or link it to anyone. We do count, per app, how often an app was returned to an assistant (counted once per daily visitor code of the computer making the request, like a visit), and show that total to the app’s owner. If you ask the assistant to prepare a listing for your app, we keep the listing details it sends (and what your website says) as a draft behind a private link, not linked to anyone, until you submit the form or for 7 days at most.
• We keep the requirements the advisor understood (such as category, features, budget, team size, security needs and apps you want to replace), never your text, together with the apps we showed and, if you tell us, the one you picked. They’re linked to the daily visitor code, or to your account if you’re signed in, so you can see your own decisions.
• We use them to improve rankings, and to show the companies behind listed apps anonymous totals, such as how many buyers in their category asked for single sign-on. A total appears only when at least 3 buyers share it. Companies never see your text, an individual request, or who you are.
• We also publish anonymous totals per category, such as the share of project management buyers who asked for single sign-on, once at least 10 buyers have asked about that category in 90 days. The same 3-buyer rule applies to every line, and the totals are updated once a day.

• Questions and comments you post on app pages are public, under your display name (you can change it under Sign-in and security) and a Maker or Team badge when it applies. Deleting a post clears its text.
• When AI checks are switched on, the text of each new post is sent to a language model hosted by GMI Cloud, which checks it for spam, scams and abuse before it appears. The labelled AI host also writes its questions and weekly summaries from public listings and public posts with GMI Cloud. We don’t keep the prompts or the answers.
• If you report a post, we keep the report with your account, the reason and your note, so our moderators can act on it.
• Launch votes are stored with your account. To spot vote rings and duplicate accounts, each vote also keeps one-way codes of your network (your IP address and its wider block) and of your inbox (your email address without “+” tags or dots), made with a random key that is new every launch week. They can’t be matched with other weeks. We delete them when the week’s result is final (never more than 8 days after the vote), and then the week’s key, after which nobody can work out what they were. Votes from throwaway email addresses or from a cluster of new accounts may be held for a person to review before they count.
• If you’re on the team of a company that verified its app, we email you about new questions on its listings and send one report on a launch’s first week. Each email has an unsubscribe link.

Some profiles have a “Contact” button. When you use it, and only after you tick the box that agrees to it, we send your name, the email address of your account and your message (plus your company name and team size, if you add them) to the owners and admins of the company that verifiably owns that app, so they can reply to you by email. We email you a copy of what was shared, keep the message for a year, and don’t share it with anyone else. Companies agree to use it only to answer you.

• Your name, email address and whether it’s verified. Passwords are stored only as secure hashes.
• If you sign in with Google, GitHub, Microsoft, LinkedIn or X: the name, email address, whether the provider verified that address, and the profile picture’s web address that it shares with us (X: your display name or username and its confirmed email address; Microsoft: no picture), plus the provider’s ID for your account so we can recognise you next time. We never ask for permission to post, and we don’t read your posts or contacts (X lists read access on its consent screen because it requires it for profile sign-in). We don’t keep the provider’s access tokens, so we can’t read anything else from that account. You can disconnect it in your account’s sign-in settings.
• The companies you belong to and your role in each.
• What your company publishes on its listings, and a record of edits and claims.
• Payments: amounts, status, receipts and a customer reference from our payment processor. We never see or store full card numbers.

We email you about your account, such as address verification and payment notices, and about the questions and launch reports described above if you’re on a company’s team.

If you subscribe to New on AppFinder (the weekly launches email), we keep only that email address and when you confirmed. No account is needed, the email has no tracking pixels, and every issue has a one-click unsubscribe link. An address that is never confirmed is deleted 14 days after its last confirmation email. When you unsubscribe we delete the address and keep only a one-way keyed code of it, so nobody can sign it up again through our form; you can still subscribe again yourself from the link in a past issue or while signed in. Ask us if you want that code deleted too.

• A sign-in cookie, only when you’re signed in.
• A cookie that remembers how you last signed in (for example “Google”) for 30 days, so the sign-in page can point to it. It holds nothing else.
• A cookie that remembers which company you’re working on in the dashboard.
• Browser storage that remembers that you closed the announcement bar, paused live leaderboard updates, or just asked for another verification email.
• Your shortlist, if you save apps to one: kept in this browser only, until you remove them. Its link lists the apps on it, so anyone you share the link with sees them. Each time you save an app we count it anonymously for that app (with the daily visitor code, like a pick), never the list.

No advertising cookies and no third-party trackers. Some app logos load from the app’s own site or a site-icon service, which, like any image request, can see your IP address.

• Dodo Payments, which processes payments, calculates tax and issues invoices.
• Anthropic, for the AI requests described above, only when that model is switched on.
• GMI Cloud, which hosts the AI models we use, only when they’re switched on: to check new community posts, to write the AI host’s posts and draft blog articles from public data, and, if we use it for the advisor, to read advisor text.
• Our email delivery provider, to send account emails.
• Google, GitHub, Microsoft, LinkedIn or X, only if you choose to sign in with them: they confirm who you are and send us the details listed above.
• A company you contact from its profile: only the details you agreed to send it.

We don’t sell personal data or share it for advertising.

You can ask to see, correct or delete your account data by emailing privacy@appfinder.tech from the address on your account. Some payment records must be kept for tax and accounting even after an account is deleted. When we delete an account, your posts’ text is removed but replies other people wrote stay in the discussion, under a “Deleted member” placeholder.