How the service handles access
Harborlight Watch checks publicly reachable restaurant web pages and links. It does not require a restaurant POS password, online-ordering back-office password, or payment-card details.
Billing
Subscription checkout and billing are handled by Stripe when Stripe is configured. This WordPress application does not intentionally store raw payment-card numbers.
Customer accounts
Restaurant locations, scan history, incidents, support-request notes, and exports are scoped to the signed-in customer account. Customer users are kept inside the branded application rather than the WordPress administration area.
Incident support
When an eligible customer requests Harborlight guidance, the system packages the incident code, monitored evidence, affected public destination, likely owner, and optional customer note for the configured Harborlight support mailbox. It does not send POS or third-party back-office credentials because Harborlight does not request them for the public monitoring layer.
Monitoring safeguards
The scanner rejects private and reserved network destinations, rate-limits public scans, verifies signed Stripe webhooks, and protects the monitoring worker with a secret header.
Scope
No monitoring service can guarantee that every third-party checkout or guest journey is available at every moment. See the Monitoring Scope page for the exact current layer.