benchr
What benchr itself collects
The site has no reader accounts, comment system, contact or newsletter submission form, or first-party analytics script. benchr's own code does not build advertising profiles of readers. Normal hosting logs and requests to the third-party services listed below can still contain an IP address, user agent, requested URL, and standard request headers. No Google AdSense ad request is made as of the effective date.
What's stored in your browser
Product preferences and guest work stay in your browser's localStorage and do not leave your device. These items include the light/dark theme and whether you selected it (benchr-theme, benchr-theme-source), the reading font (benchr-font), share-image options, Platform Watchlist, Collections, and Workspaces (benchr-platform-guest-v1), the compare tray (benchr-compare-anywhere-v1), and the short Recently Viewed list (benchr-recent-v1).
A small benchr-theme cookie may mirror the theme so the selected mode appears before the page is painted. Clearing site storage removes these local items. The site does not set AdSense advertising cookies while AdSense remains inactive; the planned activation process is described under Advertising.
Share links and Labs URL fragments
Shared Platform, comparison, and calculator links carry the state needed to rebuild selected filters or a scenario in the URL. A Labs share link is different: after you explicitly confirm and create it, cases, pasted outputs, scores, notes, and setup are encoded in the URL fragment after #lab=.
Browsers do not send that fragment in a normal HTTP request to benchr, but anyone who receives the complete URL can decode and read its contents. Do not place secrets, personal data, or confidential material in a Labs share link.
Third-party services the pages load
Some page resources come from third-party servers, which receive your IP address and standard request headers when your browser fetches them:
- Google Fonts (fonts.googleapis.com / fonts.gstatic.com) — serves the site's typefaces. See Google's privacy policy.
- CDN scripts (cdn.jsdelivr.net, cdnjs.cloudflare.com) — many article and tool pages load an animation library; image-export libraries load only when you click the relevant download button.
- Google Firebase (Firestore) (firestore.googleapis.com) — the homepage fetches its small “Latest from X” card strip from a read-only Firestore collection. The request carries your IP address and standard headers; benchr does not add an account or reader identifier to it.
- Affiliate destinations — if you choose a marked link to AI/ML API, Lovable, or RunPod, your browser opens that third-party site. The destination receives the normal web request, and the URL can contain an affiliate identifier. Its own privacy policy then applies.
Optional inference API
Current status: disabled. The codebase contains an optional /api/v1/inference proxy, but the production route returns an unavailable response unless five server-side controls are enabled: the feature flag, a privacy-policy acknowledgement, a provider key, a model allowlist, and a private bearer token.
If activated in the future, the prompt, optional system instruction, selected model, and generation settings supplied to that endpoint would be sent to OpenRouter for processing under OpenRouter's privacy policy. benchr does not currently offer a page that submits reader text to this route, and the access token must never be exposed in public browser code. This policy and its effective date must be reviewed before activation.
Affiliate links
Some pages include clearly disclosed affiliate links. Clicking one can allow the destination to attribute a later signup or purchase to benchr, and benchr may receive a commission without increasing your price. benchr does not attach an email address or benchr account identifier because the site does not collect either. The destination may process your IP address, request headers, referrer, cookies, and any information you later provide there under its own policy. See the affiliate disclosure for the current programs and editorial safeguards.
Advertising
Current status: benchr does not currently load the Google AdSense ad script, render AdSense ad units, or send AdSense ad requests. Publisher-account metadata, ads.txt, advertising-domain allowlists, and dormant readiness code do not by themselves display an ad or set an advertising cookie.
benchr may begin using Google AdSense only after Google approves the site. If AdSense is activated:
- A Google-certified consent management platform (CMP) will be enabled for visitors in the EEA, the UK, and Switzerland before consent-required advertising storage or processing begins, with a way to review or withdraw the choice.
- Google and participating vendors may receive the IP address, user agent, page URL, consent signals, and advertising identifiers, and may use cookies or similar storage according to the visitor's choice and applicable law.
- Controls for personalised ads are available through Google Ads Settings. How Google uses information from sites that use its services is described at Google's partner-sites notice.
- This policy and its effective date will be updated to reflect the live configuration.
Hosting and server logs
benchr is served by its hosting provider, which may keep standard server logs (IP address, user agent, requested URL, timestamp, and response status) for security and operations. benchr does not use those logs to build reader advertising profiles.
Security
Reasonable security measures are used to protect the site and its infrastructure, but no method of transmission over the internet can be guaranteed to be completely secure. Security reports are welcome at the address published in our security.txt.
Your rights
benchr does not maintain reader accounts or personal profiles. Most information described in this policy either remains on your device or is processed by the third-party services listed above, each of which has its own controls. If you'd like to exercise a privacy right available under the laws of your region, or believe something here is inaccurate, email security@benchr.org. If AdSense is activated, the certified CMP will also provide the applicable consent controls described under Advertising.
Policy URL
The canonical location of this policy is https://benchr.org/privacy. If you're reading a copy anywhere else, check that address for the current version.
Changes to this policy
If the site activates advertising or adds a service that changes what is collected — analytics, a newsletter, or anything else — this page will be updated and the effective date above will change. The page history is tracked like every other benchr page.