What the rescue service does not accept
It has no account, form, credential field, payment flow, cookie, analytics script, user-supplied redirect, or remote-content fetch. Query strings are rejected and request values are not reflected.
Plain HTTP cannot be trusted
A captive or hostile network can read or replace an unencrypted response. The HTTP page is not trusted application configuration and never asks you to enter personal information. Continue to the secure website for product, privacy, legal, and support information.
What we cannot prove
A successful browser request does not prove that it used Wi-Fi rather than cellular data. WiFi 4 Breakfast cannot prove that a venue, access point, portal, or connection is safe. Current browser guidance is assistance, not a security certificate.
Reporting a vulnerability
Email support@onekapisch.com with the affected URL, observed behavior, and steps to reproduce. Do not include credentials, portal contents, private keys, full IP addresses, precise locations, or personal venue information.
Please do not test against venue networks you do not own or have permission to assess. We do not currently operate a paid bug bounty or publish legal safe-harbour terms.
Current operating limits
The rescue topology is still a private field experiment. External synthetic monitoring, provider-log confirmation, a backup incident owner, and real captive-network evidence remain public-release requirements. See known limitations for the current product boundary.