wirepage.net says it is private. That needs a more precise explanation than “we care about your privacy.” Some pages work entirely on your device. Others cannot produce useful results without sending a request through site infrastructure to an outside data provider. Every visit also depends on the ordinary network systems that deliver the site.
The useful promise is not that nobody can observe anything. It is that wirepage.net collects as little as practical, does not build a visitor profile, and makes unavoidable data flows understandable.
What the site deliberately does not have
There are no wirepage.net accounts, advertising systems, analytics scripts, tracking pixels, session-replay tools, affiliate identifiers, mailing lists, social widgets, or behavioral recommendation systems.
The site does not need to know who used the calculator, which game someone played, or whether they returned the next day. Removing these systems also removes the identifiers, consent machinery, third-party scripts, and incentives that tend to grow around them.
What happens during an ordinary visit
The site is delivered through Cloudflare. To send a page to you and protect the service from abuse, internet infrastructure processes technical information such as an IP address, requested URL, request time, browser information, and security signals. Cloudflare applies its own privacy practices to that processing.
wirepage.net does not add visitor analytics or export visitor-level traffic logs. That does not mean an HTTP request leaves no trace anywhere in the delivery chain. It means the project is not turning those requests into an audience database.
What stays in your browser
Most tools operate locally. Calculator entries, unit conversions, timers, text transformations, and generated passwords are handled by code already delivered to the browser. They are not sent to a wirepage.net function.
Some games store progress, preferences, or a local record so play can resume. The selected color theme is stored locally. Weather can store a chosen location and forecast only when the visitor asks it to remember them. The service worker keeps eligible pages after a visit so they can reopen on a poor or absent connection.
Browser storage is not permanent or secret storage. Someone with access to the browser profile may be able to inspect it, and the browser may clear it. Private-browsing modes commonly discard it at the end of the session. wirepage.net cannot retrieve that local data from your device.
Search
A search query is submitted in a request body to a wirepage.net function. The function sends the query to the Brave Search API and returns a small, sanitized results page. wirepage.net does not intentionally log, retain, or cache the query, and result pages are marked not to be indexed.
Brave still receives the query from wirepage.net’s infrastructure and processes it under its API privacy notice. When you open a result, your browser connects directly to that destination. wirepage.net removes common tracking parameters from returned URLs and sends a no-referrer policy, but the destination naturally receives the new request and applies its own practices.
Weather
A typed weather location goes to a wirepage.net function and then to Open-Meteo for geocoding and forecast data. If you use the browser’s current-location feature, coordinates are used instead. The forecast can remain in the open page or, with explicit permission, be saved in that browser.
Open-Meteo describes its own API logging and retention in its terms. The important distinction is that wirepage.net does not need a weather history tied to a person; the provider still has to process enough request data to return the forecast.
Directions
Starting point, destination, travel mode, and selected coordinates go to a wirepage.net function and then to Geoapify. The route remains in the open tab unless you explicitly print or download it. API responses are marked not to be stored by shared caches.
Geoapify processes request details under its privacy policy. OpenStreetMap data contributes to place and route information. A short-lived rate limiter may process the connecting IP address to prevent one source from exhausting the service.
News and outside links
The News page downloads a finite feed assembled in advance. Choosing a category happens locally and does not send a personal preference to the server. The page does not need to request each publisher while you scan headlines.
When you choose “Read full source,” the publisher receives a direct visit. The same is true for links in Explore and Articles. wirepage.net can avoid adding referral and affiliate data; it cannot control what a destination does after you arrive.
Security is part of privacy
Pages use restrictive browser policies: outside runtime assets are blocked, referrers are suppressed, framing is prohibited, and unnecessary device permissions are disabled. These controls reduce avenues for accidental leakage and make an unexpected dependency easier to notice.
They do not make software infallible. The project uses validation and automated tests to narrow risk, but no site should promise perfect security.
The standard to judge
Ask four questions of any privacy claim:
- What information is required for the feature?
- Which parties receive it?
- How long is it retained, and where?
- What business incentive exists to collect more?
For wirepage.net, the intended answers are: only what completes the task; only the infrastructure and provider the task requires; no intentional server-side history maintained by wirepage.net; and no advertising or engagement business model pushing the collection outward.
The formal, provider-specific details remain in the Privacy page. This article explains the design philosophy behind them.