Privacy Policy

1. Summary

Most calculations and file processing run in your browser. Tools that query locations, addresses or URLs send the necessary inputs to external services. Feedback, HTTP request relay and tier-list server sharing send the selected inputs or files to a server. See the tool interface and the details below.

2. Data the tools process

Your browser may retain preferences, recent tools and some tool inputs or work in local storage. Clear site data after using a shared device. Code running on the same site can access this storage; it is not a secure vault.

Loading fonts, libraries, models, maps or external Markdown images may send your IP and request information to their providers. Even locally processed files are handled on a page that may run third-party code.

3. Location data

Some tools, such as “find a nearby pharmacy, emergency room, or restroom”, request your browser's location permission. Coordinates are used only if you allow it, and are passed to a public-data API proxy (for example a national open-data portal or map geocoding) to look up nearby facilities. We do not store your location or build a profile from it. If you decline, you can type an address instead.

4. When data is sent to a server

(a) The feedback form. When you submit the bug report / feedback form, the following is sent to us: your message, an optional reply email, the related tool name, the language, the referring page URL, your browser User-Agent, and your country code. This is delivered to the operator's notification channel (Discord). By default your IP address is used only transiently for spam and abuse rate-limiting and is not stored with the message.

(a-1) Diagnostic details (optional, opt-in). Only if you tick the “Include diagnostic details” box, the following is sent along with your report to help reproduce the bug: your IP address and approximate region (city/country level), your browser type and version, operating system, screen and window size, pixel ratio, language, time zone, network status, storage availability, and any JavaScript error messages from the page. You can untick the box at any time, and the form shows you the exact payload before it is sent. This information is likewise only delivered to the Discord channel and is not otherwise stored or profiled.

(b) Lookups a tool makes on its own. Tools that need fresh values — exchange rates, server time, public data — call external public APIs (directly or through a thin proxy). Those calls carry only what the tool needs to work (a currency code, the site address you want checked, the region to look up) and nothing else you typed into the tool. Such external services may keep standard web access logs (IP, User-Agent, and similar).

(c) A relay you choose yourself — the HTTP Request Tester. The HTTP Request Tester is the one tool whose input can pass through our servers. By default it sends your request straight from your browser to the target server, and in that case nothing passes through us. But if the target does not allow cross-origin browser requests (CORS), the browser refuses to let the page read the response. Only if you then press the “send through our server” button do the request URL, headers, and body travel through our relay (a Cloudflare Worker) to the target. That includes any Authorization, Cookie, or API-key values you entered. The relay does not store, log, or cache the request or the response; it forwards them and drops them. The only thing kept is a per-IP request counter used to limit abuse. It strips headers that could forge a caller IP, and it refuses to relay to localhost or private addresses. The first time you press that button, a dialog explains exactly what will be sent, and every response in the tool is labelled with the route it came through. If you would rather not use the relay, simply do not press the button.

(d) Storage you choose — Tier List Maker share codes. Tier lists made in the Tier List Maker stay in your browser, and share links carry their data after the # in the address, which browsers never send to a server. Only when there are too many images for a link, and only if you pick a retention period (1 hour, 1 day, 1 year) in the “Store it on the server?” dialog, is the tier list (including its compressed images) stored in our bucket (Cloudflare R2) and given a share code. It is deleted automatically once nobody has opened it for the period you picked — every time someone opens the code, the clock is reset. Anyone who knows the code can open it, so do not upload sensitive images. All that is kept besides the data is a per-IP upload counter to prevent abuse. Choosing “No” uploads nothing.

5. Cookies, advertising, and analytics

Google Analytics is not loaded by default. It loads only after you allow analytics in Privacy settings in the footer. You can withdraw permission there; rejecting analytics does not disable tools.

AdSense is used after approval and activation. Ad requests wait for the certified CMP to signal consent or that consent rules do not apply. Without a signal, no ad is requested. Ad consent and analytics consent are separate. See Google’s policy for its processing.

6. Hosting and logs

The site is served from static hosting (Cloudflare Pages) and thin proxies (Cloudflare Workers). This infrastructure may keep standard access logs (IP address, request time, User-Agent, and similar) transiently for security and reliable operation. We do not use these logs to identify individuals or build profiles.

7. Children's privacy

This site is not directed at any particular age group and does not knowingly collect personal information from children.

8. Your choices

• Delete this site's stored data (localStorage, cookies) in your browser settings.
• Opt out of personalized ads and analytics collection using the links in section 5.
• Deny or revoke the location permission in your browser.
• Use an ad blocker — the tools still work.

9. Changes

This policy may be updated as needed. When it changes, the “Last updated” date on this page changes too.

10. Contact

For questions about how data is handled, write to us on the feedback page.