Privacy notice

Ordinary catalogue browsing does not require an account. We do not use advertising trackers or cross-site profiling. Product icons are requested from Google's favicon service, so Google can receive the requesting network address and viewed product domain.

If you request software missing from the catalogue, we retain the software query and an aggregate request count for editorial follow-up. This private queue contains no account or network identifier and expires 90 days after the last request. Avoid including personal information in a software request.

Cloudflare Turnstile is loaded only on protected contribution forms when configured. Its processing is governed by Cloudflare's terms.

PostHog web analytics, session replay, and error monitoring are optional and disabled by default. When the operator configures them, the browser sends page views, allowlisted product events, masked session replays, and diagnostic error reports directly to PostHog's US Cloud. Pageview URLs carry origin plus path only, with query values stripped. Do Not Track is respected, form inputs are masked, and raw search text, email addresses, bearer tokens, and account identifiers are never PostHog fields. Click autocapture, feature flags, and surveys are disabled. When unconfigured the browser makes zero PostHog requests. PostHog's processing is governed by PostHog's terms and data-processing agreement.

Ahrefs site analytics loads on every page from analytics.ahrefs.com and reports page views there. Its processing is governed by Ahrefs' terms.

Supabase Auth provides account identity. The API stores the immutable Auth subject, private saves/lists/preferences, Project-change notifications, contributions, moderation history, and scoped memberships. It does not copy account email into the profile table. An opted-in report contact is encrypted, copied to a bounded delivery queue only when the report is resolved or dismissed, and destroyed after delivery, terminal failure, account deletion, or expiry. Submitted public-interest history is retained with actor references anonymized after account deletion; private drafts and inbox rows are deleted.

First-party decision and commercial events use keyed session pseudonyms, strict property allowlists, and expiry dates; raw IP addresses, device fingerprints, bearer tokens, and email addresses are not analytics fields.

API 5xx failures may additionally send a diagnostic report to PostHog's US Cloud when the operator configures it. The report carries only the error name, message, truncated stack, route template, method, status, and request ID. Request bodies, query strings, headers, tokens, emails, IP addresses, and stored rows are never sent as separate fields, though the truncated error message itself comes from thrown errors and is not scrubbed. When unconfigured the API keeps error reporting log-only.

When you explicitly ask the decision assistant to interpret a request or generate a comparison summary, the API may send the bounded request plus reviewed catalogue facts to the configured OpenAI project. It also sends a keyed pseudonymous safety identifier. OpenAI receives no account email, API bearer token, database credential, source URL fetch permission, or model tool access. Requests set provider storage off; our database stores structured intent, bounded results, model/run metadata, and keyed hashes—not the raw natural-language request, prompt, or provider response envelope.

Recommendation/model metadata, drafts, and feedback carry configured expiry dates and are removed by the retention process. Account-linked recommendation sessions are included in export/deletion. Editors may request source-grounded drafts, but a human must decide each field and complete the ordinary publication review. The operator must execute an appropriate data-processing agreement and retention setting with the provider before enabling production use.

Account settings provide granular Project alert choices plus export and deletion workflows. For access, correction, deletion, or legal-hold questions, contact legal@opensourcealternatives.fyi.

You can opt out of PostHog analytics and session replay with Do Not Track, with PostHog's opt-out cookie, or with a content blocker that stops direct requests to PostHog's US endpoints. Opting out does not change catalogue content or first-party decision analytics, which remain pseudonymous and server-enforced.