Skip to content
Go to dashboard

15.1How we protect your data

These are the protections you can see and use in obsrvly.

Secrets#

A secret is a password, token or key that you save once and use in monitors by name (chapter 8).

  • Encrypted as soon as you save it. The create form says: "Encrypted immediately. You will see it once on the next screen, then never again."
  • Shown once only. You must tick "I have copied and stored this value — I understand it cannot be shown again." before you can select done — dismiss forever. If you lose the value, delete the secret and create a new one.
  • Sent only to the sites you allow. Every secret needs allowed sites: the sites that may receive it. A secret is sent only over https, and only to those sites (8.4).
  • Shared with your team. Every member of your team can use a secret in a monitor. Nobody can read its value.
  • Never shown in results. Messages and step lists show ${NAME}, never the value.
  • No screenshot while a secret is on screen. If a failed browser check shows a secret, no screenshot is kept. The monitor shows: "No screenshot: the page was showing a secret."

API keys#

An API key lets a program use obsrvly for your team (chapter 13).

  • A key is shown once, when you create it. It starts with obs_.
  • A key works only on its own team. A teamId in a request body is ignored.
  • A key cannot create, list or revoke keys. It cannot cancel your subscription. It cannot change a secret's allowed sites. You must sign in to the dashboard for these. A key gets permission_denied if it tries.
  • Nobody gets alert channel credentials back, with a key or signed in to the dashboard. These fields come back empty: slackWebhookUrl, teamsWebhookUrl, discordWebhookUrl, telegramBotToken, pagerdutyRoutingKey, jsmOpsApiKey, pushoverUserKey, pushoverAppToken, webhookUrl, webhookSecret, and every value in webhookHeaders (the header names stay). credentialHints shows only the last characters of each. emailTo and telegramChatId are returned.
  • A revoked key stops working within a minute.
  • A team can hold 50 keys.

Audit log#

The audit log shows who changed what in your team. Open the audit log tab (14.5).

  • Only team owners can read it. Other members see "Only a team owner can read the audit log".
  • Entries are kept for a year.
  • Secrets, webhook URLs and monitor settings that can hold credentials are shown only as "changed". Their values never appear.
  • Each entry names who made the change: a member's name, API key "<name>", obsrvly staff, or a system name such as obsrvly (see 14.5).

Status page#

Your public status page (chapter 12) shows only what you choose.

  • It is off until you turn it on.
  • Each monitor on it needs a public name. A monitor's own name is never published.
  • Incidents on the public page never show the error, who acknowledged it, or an ID.

Monitors check public addresses only#

obsrvly can only check addresses on the public internet. A check to a private address fails with this message:

destination is not a publicly routable address

Browser monitors add the host name at the end of the message. Discovery (1.4) refuses localhost or a private IP address with invalid_argument.

Last updated