Privacy and safe use
Checks stay bound to the site owner’s control.
Before FormUptime inspects or submits a public form, control of its exact HTTPS origin must be shown with a verification file or DNS record. Redirects are not accepted. The proof is rechecked before discovery and immediately before submission.
What is retained
Verification records contain a cryptographic digest, origin, timestamps, method, and status. The raw proof token is not stored. A private report may contain the target host, outcome, detected field count, and a screenshot. Evidence follows the applicable rolling retention period.
What is blocked
FormUptime does not bypass CAPTCHA, OTP, access controls, consent flows, or transaction safeguards. Password, file, verification, and payment forms are excluded. Cross-origin form actions and private-network destinations are blocked.
Control and removal
The owner can remove the verification file or DNS record, revoke the verification session, or ask the operator to stop a monitor. A failed, revoked, or expired proof blocks further synthetic submissions. Service capabilities may change, and a monitor also depends on technical availability and continuing authorization.