Privacy

What never leaves your browser

File tools process the documents and images you open on your device, and calculators work with your numbers locally. Those files and calculation inputs are not uploaded. Each tool describes its processing limits.

A few tools remember a draft so that a closed tab does not lose your work: the notepad, the invoice, a list of names. That draft is kept in your browser’s own storage under a key beginning gb:, on this device only. It is never read by the site, and you can remove it at any time by clearing this site’s data in your browser.

The same storage holds the few things the site itself remembers for you: your bench (the tools you pinned or used lately), your Daily progress and streak, and how many answers you gave each day in a practice tool. They are counts and names of tools, never what you typed, and they are not sent anywhere.

Your activity calendar combines meaningful tool use and Daily play. It keeps dates, tool names and puzzle types in this browser for up to 400 days, independently of individual tool resets. It works when analytics is disabled. Clearing this site's browser data clears that history; another browser or device has its own history.

A practice set shared as a link, such as a spelling list, carries the set after the # in the address. Browsers do not send that part of an address to a server, and our analytics drop it as well, so the set lives only in the link.

The site also installs a small offline worker that caches the pages and scripts so the local tools can open without a connection once loaded. Network lookups still need a connection. The worker caches site files, not submitted input or private lookup responses.

Requested lookups and feedback

When you request an IP or ASN lookup, the address or network number is sent in a POST body to our server. Choosing your own address uses request metadata supplied by our host. The server reads a dated DB-IP Lite snapshot stored with the application; it does not send your lookup to DB-IP or another data provider. Application code does not log lookup inputs or keep a history of them. Results are returned with no-store caching instructions. Hosting request logs still apply as described below.

SSL Checker sends the public hostname you enter to our server. The server resolves it through DNS and makes one bounded TLS connection on port 443 to inspect the certificate. The DNS resolver and target receive that network request. Results may remain in a bounded in-memory cache for five minutes; application code does not keep a lookup history. The browser receives no-store responses, and hostnames are excluded from analytics.

Redirect Checker sends the supplied URL to our server, which requests that public URL and follows its permitted redirects. Those target servers receive the requests. Motorcycle VIN Decoder sends the supplied VIN and optional year through our server to the NHTSA vPIC service. Each tool names its source and explains its limits before use. Currency Converter requests one shared reference-rate feed; the amount and currency pair are calculated locally and are not sent to the rate provider.

Feedback is sent only when you submit the feedback form. Its message and the tool it concerns are stored so we can investigate. Avoid including private information.

What is collected

To learn whether optional Daily invitations and activity displays help people return, this browser may be assigned to a stable experiment group. When analytics is allowed, we send the group, its starting date, and limited events such as an invitation being seen, a puzzle being played, or a meaningful return visit. These events contain no visitor identifier, tool inputs, puzzle answers, or copy of your activity calendar. The experiment measures browsers, rather than identifying people across devices.

Two measurements, both cookieless, both from Vercel, the company that hosts the site:

• Vercel Analytics records that a page was viewed: the page address, the site you came from, your country, and the browser and device type. It does not set a cookie and does not keep an identifier that follows you between days. We also measure tool views, interactions, verified outcomes where supported, exports, safe error categories, shares, discovery links, search result counts and install actions. These carry approved tool names, event categories and known acquisition sources or campaign labels. Tool inputs, results, filenames, raw search text, error messages and URL query strings or fragments are excluded from these analytics events.
• Challenge links carry only a random challenge seed, the run length and the claimed score you chose to share. The seed lets a recipient receive the same challenge; it is not an account identifier and no typed text, answers or device information is put in the link.
• Vercel Speed Insights records how quickly pages load and respond in real browsers, so slow pages can be found and fixed.

Neither one can see what you put into a tool: they observe the page, not its contents. As with any web host, Vercel’s servers keep short-lived request logs to serve the pages and to defend against abuse.

Google Analytics

Google Analytics helps us understand visits, useful tool actions and which pages need improvement. It uses analytics cookies to distinguish browsers and sessions. Google receives page addresses, traffic sources, browser and device information, approximate location and approved tool-action categories. Network requests also expose your IP address to Google. These measurements are processed on Google’s servers.

For visitors our host locates in the United States, analytics can run unless you decline or exclude this browser. Everywhere else, including when location is unknown, Google loads only after you allow it. We keep advertising storage, advertising personalization and Google Signals off. This setting does not give consent to any future advertising network.

Our events exclude tool inputs and results, files, filenames, search text, full error messages and URL query strings or fragments. We do not send the local activity calendar, experiment history or retention cohorts to Google. Analytics cookies and your choice last for up to six months; you can withdraw permission below. See Google’s privacy policy.

Returning visits and your choice

A small local analytics record remembers your first visit date, up to 40 recent active dates, broad acquisition source, and the most recent successful use date for up to 100 tools. It contains no identifier, files or tool values. It lets this browser report that it returned, including weekly cohorts and return windows of one day, 7–13 days and 30–36 days. We receive aggregate categories, not the local activity history. Clearing browser storage resets this record, and a different device is counted separately. A session record preserves acquisition attribution for up to 30 minutes of inactivity.

What does not exist here

• No accounts, sign-ups or passwords.
• No mailing list and no newsletter.
• No mailing of tool results or uploaded files. The contact page provides an email address.
• No advertising, today.

Advertising, if it comes

General-purpose tools on this site may carry advertising in future. That is a possibility, not a plan with a date. If it happens, an advertising network’s script would run on those pages and could set its own cookies or identifiers under its own privacy policy. This page would say so before it happened, name the network, and say which pages carry it. Tools with paid professional extras would carry no advertising at all. Any future advertising integration would also require a review of what its scripts can access.

Questions

Ask through the contact page. This page was last changed on 8 October 2026.