Skip to content
Likelier

Privacy policy

Last updated: 2026-05-09

What we collect

Page analytics

Likelier uses Plausible Analytics , a privacy-focused analytics tool. Plausible collects:

Plausible does not use cookies, does not collect personal data, and does not track visitors across sites or sessions. No IP addresses are stored. All data is aggregated — there is no way to identify individual visitors.

Search analytics

When you use the search feature, we record an anonymous search event in our database. The event contains:

No IP addresses, cookies, or session identifiers are stored with search events. The hash is one-way — we cannot reconstruct your query from it. Anonymised search analytics are retained indefinitely to help us understand which topics are most searched and where results are missing.

Third-party data processors

Google (Gemini API)

When you use semantic search, your query text is sent to Google’s Gemini API to generate a mathematical search vector. Likelier does not store the query text; only the resulting vector is used (in your browser) to rank results. Google’s processing is subject to the Google Privacy Policy .

Cloudflare

The site is hosted on Cloudflare Pages. Cloudflare processes connection metadata (including IP addresses) as part of its network infrastructure. See the Cloudflare Privacy Policy .

What we do not collect

Data controller

Likelier is operated by Krzysztof Gluszczyk. For privacy questions, open a GitHub issue .

Legal basis (GDPR)

The legal basis for processing aggregated analytics data (page views and anonymised search events) is legitimate interest (Article 6(1)(f) GDPR) — understanding aggregate usage patterns to improve the site. No consent is required because no personal data is processed and no cookies are set. The Gemini API call is necessary to provide the semantic search feature you explicitly invoked.

Your rights

Because we do not collect personal data, there is no personal data to access, correct, or delete. If you believe this is incorrect, contact us via the GitHub link above.