Security

Last updated: November 15, 2026

Encryption

All traffic to the Service uses TLS. Passwords and API tokens are stored hashed, never in plain text. Alert-channel settings (such as Slack and Discord webhook URLs, PagerDuty keys and Telegram bot tokens), webhook signing keys, health-check secrets and AI provider keys are encrypted at rest.

Backups

The production database is dumped nightly to private object storage, encrypted with age to a key kept off the hosting platform, and retained for 14 days. Restores are tested as part of our ops runbooks.

Access

Production access is limited to the founder. Platform admin tools require a confirmed two-factor authenticated admin account. Outbound monitoring requests are blocked from reaching private and internal network addresses.

Where data lives

Application, database and primary backups run in the United States (DigitalOcean region nyc3 via our hosting platform). Payments are processed by Stripe. Error details may be sent to our error tracker so we can fix failures. See the privacy policy for the full list of service providers.

Privacy Policy

Probe egress for firewalls

Uptime and related checks originate from our nyc3 probe. If your site sits behind a WAF or IP allowlist, permit these addresses so checks are not blocked as bots.

  • 104.28.161.245

Authentication

Accounts can use email and password, or GitHub or Google sign-in. Organizations can require SAML SSO, and paid organizations can require two-factor authentication for their owners and admins. We encourage turning on two-factor authentication for every user.

Passkeys

A passkey signs you in with Touch ID, Face ID, Windows Hello, your phone or a security key instead of a password. Add one in Profile → Security (you confirm your password first), give it a name, and choose “Sign in with a passkey” on the login page; supported browsers also offer it when you click the email field.

Passkeys are bound to observe.live, so a look-alike site cannot use them, and each sign-in needs your fingerprint, face or device PIN. That makes a passkey sign-in two-factor on its own: it skips the authenticator code, and it satisfies organizations that require two-factor. If you use an authenticator app, you can also answer its sign-in prompt with a passkey.

We email you whenever a passkey is added or removed. Removing your last passkey never locks you out: your password and any two-factor stay as they are.

Questions

Email support@observe.live for security questionnaires or vulnerability reports. We do not yet publish a SOC 2 report.