Glossary
Signup signal
Evidence about a visit and its submitted request, returned separately from the email result and the final signup action.
A Signup Protection response keeps the email result, visit findings and recommended action separate. A finding has a code, class and default_raises flag. In a combined check, read the outer action: a signal may require confirmation even when email alone allows the signup.
Signals cannot recommend rejection on their own or relax an email rejection. VPN, Tor, proxy and hosting findings are informational by default. Their presence does not establish abuse; their absence does not establish a human visitor.
signals.notes contains separate observations about the connection and browser. A note is not a finding that raises the action. A browser check reported as not evaluated limits that evidence, even if the overall signal operation was evaluated. It does not mean that the check passed.
Email reason_codes remain inside email. Outer signal_codes identify the findings that raised the action, while signals.findings contains the fuller evidence. Your application applies the action, sends confirmation messages and controls access. See how to read a signup check and what TLS fingerprints can establish.