Security at SiteGauge

Every page SiteGauge fetches, for a monitor or a free tool, goes through a server-side request guard. Private, loopback, link-local and cloud-metadata addresses are refused, the address is checked again at connect time so a DNS answer cannot switch to an internal host, and every redirect hop is re-checked before it is followed.

• All traffic to the website, dashboard and API is served over TLS.
• Secrets we have to reuse (login sessions for monitoring gated pages, signing secrets and bot tokens for alert channels, and your own third-party API keys) are encrypted at rest with AES-256-GCM.
• SiteGauge API keys are stored as one-way hashes, so a key cannot be read back, only replaced.

On Business and Enterprise, a change can be exported as an evidence bundle: the captured files, a manifest of their SHA-256 hashes and a signature over that manifest. Bundles signed with Ed25519 include the public key, so anyone can check them on the verification page without trusting us. A trusted timestamp is attached when the timestamp authority is reachable.

• Owner, admin, member and viewer roles, with viewers limited to read-only access.
• An audit log of account actions.
• Sign-in is handled by our authentication provider, Clerk.
• SSO / SAML is available on request for annual enterprise agreements. It is not self-serve.

Change history and snapshots are kept for your plan's retention window and pruned automatically after it. When you delete a workspace, its data, including stored snapshots and screenshots, is permanently erased after a 30-day grace period. The providers that process data for us are listed in our privacy policy.

SiteGauge does not currently hold a SOC 2 report or an ISO 27001 certification. We are happy to answer a security questionnaire and describe the controls above in more detail; get in touch.

If you believe you have found a security issue, email support@sitegauge.com with the details and steps to reproduce. Please give us a reasonable chance to fix it before sharing it publicly.