Privacy Policy

1. Controller

2. Website delivery and security

ProviderBench is delivered through Cloudflare Workers and stores public catalog snapshots in Cloudflare R2. When you request a page, Cloudflare processes the technical information required to deliver and protect it, such as your IP address, requested URL, request time, browser and device headers, and security signals. We use this processing to provide a reliable and secure website and to diagnose failures. The legal basis is our legitimate interest in operating and protecting the service under Article 6(1)(f) GDPR.

Cloudflare, Inc. and its affiliates act as processors under the applicable contractual safeguards. Requests may be handled by Cloudflare infrastructure outside the European Economic Area. See Cloudflare’s privacy policy for information about its processing and transfer safeguards. Operational data is retained only for as long as required for delivery, security, troubleshooting, and applicable legal obligations.

3. Pirsch Analytics

We use Pirsch Analytics, provided by Emvi Software GmbH, Nickelstraße 1b, 33378 Rheda-Wiedenbrück, Germany, to understand aggregate use of ProviderBench and improve navigation, search, filters, and comparisons. Pirsch is cookie-free. It generates a non-reversible visitor identifier from the IP address, user agent, date, and a website-specific salt. The IP address is not stored, the identifier changes after 24 hours, and it cannot be used to recognize a visitor across different websites.

Depending on the request, Pirsch may process the visited path, referrer, language, visit time, browser, operating system, device type, screen size, and approximate country or city. ProviderBench disables query-string collection, so model searches and filter values in page URLs are not sent with page views. ProviderBench also sends a small set of fixed interaction events, such as whether a provider or model result was opened, which ranking metric was selected, and how many models were included in a comparison. We never send raw search text, email addresses, account identifiers, or other free-form personal information as event metadata.

The legal basis is our legitimate interest in privacy-preserving, aggregate measurement and product improvement under Article 6(1)(f) GDPR. Pirsch acts as our processor. More information is available in Pirsch’s privacy documentation.

4. Public catalog data and images

Provider, model, price, and performance metadata is fetched server-side from OpenRouter and stored as public catalog snapshots; it is not linked to individual visitors. Provider logos, model icons, and country flags are retrieved through a restricted first-party image proxy and cached for 24 hours, so the original image hosts do not receive your IP address merely because an image appears on a ProviderBench page. If you actively follow an external link, the destination receives the normal technical request data and applies its own privacy policy.

5. Email contact

If you email us, we process your address, message, and any information you choose to provide to answer the inquiry and handle follow-up questions. The legal basis is Article 6(1)(b) GDPR for pre-contractual or contractual communication and otherwise our legitimate interest in responding under Article 6(1)(f) GDPR. We retain correspondence only as long as needed for the inquiry and any statutory record-keeping duties.

6. Your rights

Subject to the legal requirements, you may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. You may contact marius@eyloo.com. You also have the right to complain to a data-protection authority. The authority responsible for our registered office is the Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz.

7. Changes to this policy

We update this policy when the service, processors, or legal requirements change. The date at the top identifies the current version.