Data and privacy
This page describes what the code running at shriek.dev does with data
today.
What Shriek stores
Everything below is kept per tenant.
| Data | Contents |
|---|---|
| Alerts | Everything you send in an alert or incident (source, severity, title, detail), the time, and the alerts Shriek adds itself. |
| Sources | Each registered source, its period, last heartbeat and status. Retired sources are marked retired, not removed. |
| Incidents | Each incident’s id, source, severity, title, when it opened and when it was resolved. |
| Public components and updates | The labels and messages you publish. |
| Phones | The push token of each phone registered through the Shriek Android app, and a random leave key that lets that phone stop its notifications or move them to a new push token. A replaced token is kept, marked with the token that replaced it. |
| Notifications sent | For each notification: a random receipt id, the alert’s source and title, when it was sent, and whether the app reported it shown. |
About people and services. Shriek stores which ChirpAuth clients and which people belong to which tenant. For a person, that is the ChirpAuth id that ChirpAuth issues for the Shriek app; Shriek stores no email address or name.
Logs. Operational logs are kept for 14 days. They include, for each
critical alert, the service, component and title, and how many phones were
notified.
Shriek runs on AWS in the us-east-1 region (United States). Phone
notifications go through Google’s Firebase Cloud Messaging and carry the
service, component, title, severity, time, and the start of the detail (up to
240 bytes).
How long
Shriek deletes nothing. Alerts, incidents, sources, public components and updates, and phone registrations are kept for as long as Shriek runs. Logs are the exception, at 14 days.
Who sees what
- Your tenant. Every service and person in your tenant can read everything in it: the whole feed, every source, every incident.
- Anyone. Your public board (service names, component labels and
greenorred) and your public updates can be read by anyone who knows your tenant name. Alert titles and details, component names and incidents are never part of them. - Other tenants can’t read your data.
Put nothing in an alert that the people in your tenant shouldn’t see, and nothing in a public label or update that the world shouldn’t.
Deleting data
Not yet:
- No endpoint deletes data. Alerts can’t be edited or deleted, by design. Public components, public updates and phone registrations can’t be removed through the API either.
- Retiring a source takes it off the board but keeps its record and every alert it produced.
- Deleting a ChirpAuth account does not remove anything from Shriek.