Customer-Site Monitoring Policy

Authority and notice

A customer may install SiteAirbag only on a website it controls or is authorized to manage, and must have authority to observe the configured actions and operate each rescue route. The customer is responsible for required visitor, client, worker or sector-specific notices, legal bases and choices. Origin verification is a security control; it is not proof of every legal permission.

Observed signals

The runtime listens for interactions with configured buttons, links, forms, navigation and supported providers. It measures normalized timing and outcome/failure evidence, and wraps browser fetch/XHR only to observe method, sanitized path without query/fragment, origin relationship, status and duration. It passes requests through and does not read request or response bodies or authorization headers. Separately, it may report only a bounded CSP violation attributable to SiteAirbag, reduced to a directive, disposition and normalized origin or fixed keyword; it does not send the site policy, page URL or blocked URL path.

• No keystroke logging, session replay, screenshots or page-HTML capture.
• No original form values, request bodies, full query strings or advertising identifiers in ordinary runtime evidence.
• Setup can read a bounded locator description, such as accessible name, classes or sanitized link target, when an authorized user deliberately selects an action.

Fail-open and conservative rescue

SiteAirbag is designed not to block, submit, cancel, purchase, book, upload, create, delete or replay the original visitor action. A rescue appears only after configured conservative evidence and provides an alternative the visitor chooses. A retry returns control to the original page; it does not replay a request. Browser, network, policy or customer-site changes can prevent observation or rescue. A policy that blocks the script leaves no running code to report why; a policy that blocks the SiteAirbag connection also blocks diagnostic delivery, and SiteAirbag does not use another channel to evade it.

Deliberate rescue forms

If enabled, a visitor can separately submit name, email, phone, a short message and allowlisted business-safe details. The form is not a copy of the original website form. Customers must not solicit credentials, card/bank data, government IDs, health data, authentication codes, private keys or other secrets. Screening reduces risk but cannot guarantee a visitor never enters unexpected sensitive text.

Customer controls

Workspace owners choose protected actions, rescue methods and visitor-facing privacy links; can test without creating real customer-side effects; and can disable or remove a site. Runtime authority can be revoked by resetting the installation. Reports of unauthorized monitoring or abusive configurations should go to security@siteairbag.com.