Skip to content

Legal

Privacy policy

Last updated 29 October 2026.

Template

This policy describes the data this software actually processes. Before operating the service commercially, an operator must add their legal entity, jurisdiction, data-protection contact and any processor agreements, and have it reviewed.

What is collected

Three categories, and nothing else:

  • Account data. If you create an account: email address, display name, and an optional profile (username, bio, website, GitHub handle). Authentication is handled by Firebase Authentication; passwords are never seen or stored by this application.
  • Content you create. Collections, saved resources, submissions, reports and, for editors, catalog edits. Administrative actions are written to an audit log that records who did what, when.
  • Product analytics. Event type, timestamp, page path, referrer, UTM parameters when present, a coarse device class (desktop/tablet/mobile), the id of the resource involved, and either a random visitor id stored in your browser or your account id when signed in.

What is never collected

  • IP addresses are not stored in the analytics record.
  • No cross-site tracking, fingerprinting or advertising identifiers.
  • No full query strings beyond the search term itself.
  • No passwords, tokens, API keys or payment card details.
  • Prompts and model outputs from the generation pipeline are not stored as user data.

Uploaded screenshots

An image you upload for repository discovery is stored in a private, per-user location, analysed by the configured AI provider to extract visible identifying text, and then deleted automatically after the retention window (24 hours by default). It is never made public and is not used to train anything. URLs found in the image are parsed as text and are never fetched.

Third parties

  • Google Firebase: authentication, database, file storage and hosting.
  • GitHub: public repository metadata is retrieved from their API. No personal data of yours is sent to GitHub.
  • An AI provider (Anthropic or OpenAI, when configured): receives repository text and uploaded screenshots for analysis.
  • A payment provider: only if you subscribe. Card details go directly to the provider; this application stores a customer id and a subscription status.

Retention

  • Raw analytics events: 180 days, then deleted; daily aggregates are kept.
  • Screenshot uploads: deleted after the configured retention window (24 hours).
  • Account data: kept until you delete your account.
  • Audit logs: kept for the life of the service, as a security record.

Your rights

You can export your collections at any time from your library (JSON or Markdown). To access, correct or delete your account data, use the report form on any page with the note “data request” and a moderator will action it. Deleting your account removes your profile, collections, saved items and submissions; audit entries recording administrative actions are retained.

Cookies

One essential cookie holds your signed-in session (HttpOnly, SameSite=Lax, five days). The theme preference and the anonymous visitor id live in localStorage, not in cookies, and clearing site data removes them.

Changes

Material changes will be noted with a new “last updated” date on this page. See also the terms.