On this page
1Who we are
Heedery is run by Come Back Agency, LLC, 911 Main St Unit 2009, Kansas City, Missouri 64105, United States. We are the controller for the data of the people who sign up and use the product. You can reach us through our contact form.
Some data belongs to your own customers: the email addresses that subscribe to your status page, and whatever appears in the browser flows you run against your sites. For that data you decide what is collected and why, and we process it on your behalf under the Terms of Service.
2What we collect
Your account
Your email address, your name if you give one, your password as a bcrypt hash, when you signed up and when you last signed in. The 6-digit codes we email you to verify the address or reset the password are stored as HMAC hashes, never in clear. If you turn on two-factor sign-in we keep the TOTP secret encrypted with AES-256-GCM, and the hashes of your recovery codes.
Your workspace
The workspace name, the plan, who is a member and with which role, pending invitations (the address invited and a link token that expires after 7 days) and an activity log: who added or changed a monitor, who joined or left, who acknowledged or closed an incident, with a timestamp. Comments your team writes on an incident are kept with it.
Phone alerts
Only if you turn on SMS or call alerts: your mobile number, when you confirmed it and which kind of phone alert you chose. For each SMS or call we send: the number, when, what it was for (an alert, an all-clear or a confirmation code), the credits it used and the delivery status and error code Twilio reports back. The code that confirms the number is stored as an HMAC hash, like the email codes.
Monitors and check results
The targets you monitor and their settings: the URL, host or port, the check type, interval, expected status codes, the keyword or JSON path a response must contain, and for HTTP monitors the request headers and body you enter. Those headers are stored as you typed them, so do not put a credential in one that you would not want in our database.
Every check writes one row: the time, up or down, the HTTP status code and the latency, split into DNS, TCP connect, TLS handshake, time to first byte and transfer. We read a response body only when a keyword or JSON check asks for it, read at most 1 MB of it, and never store it. What we keep of a failure is a short reason such as "HTTP 503" or "Keyword not found", on the monitor's latest status and on the incident.
SSL checks read the certificate of your host. Domain expiry checks send the root domain name to public WHOIS servers. A heartbeat monitor records the time each ping arrives; the ping URL carries a secret token and nothing else is read from the request.
Browser flows and screenshots
A browser flow is a list of steps you write (open a page, fill a field, click, check for text) that a real Chromium browser runs against your site. Values you mark as secret, such as a test account's password, are encrypted with AES-256-GCM before they are saved.
After every run we keep the timing of each step and one JPEG screenshot of the last page the browser saw. When a run fails we also keep the screenshot taken at the failure. Each monitor holds at most two screenshots, up to 200 KB each, and every new run overwrites the previous one. A screenshot shows whatever was on the page, which may include personal data of the test account you use. Do not point a test at pages that show real customers' data.
Status page subscribers
When someone asks for updates on your status page we store their email address, the language the page was in, whether they confirmed by clicking the link we sent, and an unsubscribe token. Nothing is sent before the confirmation. Every email carries an unsubscribe link, and an unsubscribed address keeps a record of the opt-out so it is not emailed again.
Status page visitors
A public status page needs no account and sets no cookie. It remembers the chosen language and which groups the visitor collapsed in their own browser only (see Cookies and local storage). There is no analytics script on any page.
A private status page can be opened with a password you set (we store a bcrypt hash), with a one-time code sent to a work email on a domain you allow (the code is kept as an HMAC hash for 15 minutes, with 5 attempts), or from an IP range you allow. The visitor's IP address is compared with your allowlist and used to rate-limit the sign-in form for 15 minutes in memory; it is not written to the database. A successful sign-in sets one cookie for that page, valid for 30 days. Private pages tell search engines not to index them.
Billing
Payments go through Stripe. Your card number is entered on Stripe's checkout page and never reaches our servers. We store your Stripe customer and subscription identifiers, the price you are on, the subscription status, the billing interval, the end of the current period, trial and cancellation dates, and the identifiers of the Stripe events we have processed. Invoices and receipts live in Stripe's billing portal, which you reach from Settings.
Alert channels
If you connect Slack, Microsoft Teams, Discord, Telegram or a webhook, the webhook URL, chat ID or signing secret is encrypted with AES-256-GCM before it is stored. An alert carries the monitor's name and URL, the failure reason, and a one-click acknowledge link that is signed and expires after 7 days. We keep a record of each delivery: when it was sent, how many attempts it took and the last error. Alert emails go to the workspace's owners, admins, the site admins assigned to the monitor, and any extra addresses you list.
Support and email
If you write to us we keep the conversation. Emails we send (verification codes, alerts, security notices, plan changes, status page updates) go out through Resend and are not used for marketing. We do not send newsletters.
A message sent with the contact form reaches us as an email with your name, address and message, together with your IP address, your browser, the page you came from and, when you are signed in, your account and workspace; we use these to answer you and to keep spam out.
Server logs
Our reverse proxy and application write logs on the server that can contain your IP address, the request path and the time. We read them to find faults and abuse. They stay on the server for a short period and are not copied anywhere else.
3Why we use it, and on what basis
- To provide the service you signed up for (performance of a contract): your account, your monitors and their results, alerts, status pages, billing and support.
- To keep the service secure and running (our legitimate interest): rate limits on sign-in and on public forms, the emails we send when a password or two-factor setting changes, server logs, nightly backups, and the superadmin console our staff use to help a locked-out user (reset two-factor, sign out everywhere) or to grant a complimentary plan. Those staff actions are written to your workspace's activity log.
- With consent: status page subscribers confirm by email before they receive anything, and can withdraw with the link in every message.
- To meet legal obligations: invoices and payment records are kept as tax law requires.
We do not sell personal data, do not share it with advertisers and do not profile anyone.
Your mobile number and your consent to receive texts are used only to send the alerts and codes you asked for. They are never shared with third parties or affiliates for marketing or promotional purposes.
4Who processes it for us
- OVH hosts the application and the database on a virtual server in Virginia, United States.
- Resend delivers our email. It sees the recipient address and the message.
- Stripe handles payments, invoices and the billing portal.
- Twilio sends SMS and makes calls for phone alerts, if you turn them on. It sees your phone number and the text of the alert.
- Cloudflare R2 stores the nightly database backup.
- The alert services you choose: Slack, Microsoft Teams, Discord, Telegram (through the Heedery bot, to the chats you connect) and the webhook endpoints you configure receive the alerts you asked for, under those services' own terms.
- Public WHOIS servers receive the domain name of a monitor with domain expiry checks on.
There is no analytics or advertising provider. The fonts are bundled with the application, so no request goes to a font service. Where a processor is outside the EEA, the transfer rests on standard contractual clauses or an adequacy decision.
5How long we keep it
- Raw check results: 7 days. They are compressed after one day.
- 5-minute averages: 30 days. Hourly averages: 90 days. Daily uptime: kept for as long as the monitor exists. Your plan decides how much of this history the pages show (30, 60 or 90 days).
- Latest status, incidents, comments, alert deliveries and the activity log: kept while the workspace exists.
- Phone number: until you remove it in Settings or delete your account. SMS and call records: kept while the workspace exists, like the other alert deliveries.
- Screenshots: only the last run and the last failure per monitor; overwritten by the next run, deleted with the monitor.
- Sign-in sessions: 7 days, or until you sign out everywhere, change your password or change two-factor settings. The one-time email codes expire after 15 minutes; their hashed records stay with the account.
- Invitations: 7 days. Private status page sign-in: 30 days.
- Subscribers: until they unsubscribe, you remove them, or the status page is deleted.
- Backups: a nightly copy of the database, each kept for 30 days. Data you delete therefore leaves the backups within 30 days.
- Billing records: as long as tax law requires.
Deleting a monitor deletes its raw checks, incidents, comments and screenshots at once; the 5-minute and hourly averages age out under the periods above, and the daily uptime figures are removed on request. Deleting a status page deletes its subscribers. Deleting a workspace deletes everything in it; see Your rights for how.
7How we protect it
- Passwords are hashed with bcrypt (cost 10) and must be at least 8 characters. A sign-in with an unknown email takes as long as a wrong password, so the form does not reveal which addresses have accounts.
- Sign-in is limited to 30 attempts per IP address and 10 wrong passwords per account in 15 minutes. An account cannot sign in until its email is verified.
- Optional two-factor sign-in with an authenticator app and recovery codes. Secrets at rest (two-factor keys, alert channel credentials, test passwords) are encrypted with AES-256-GCM.
- Changing your password or two-factor settings signs out every other session and sends you an email. You can also sign out of all other devices from Settings.
- Every page is served over HTTPS. Caddy obtains and renews certificates automatically, including for status pages on your own domain. The application is reachable only through that proxy.
- Webhook alerts are signed (an
X-Heedery-Signatureheader) so your endpoint can verify they came from us. Acknowledge links are signed and single-purpose. - A nightly backup of the database is kept for 30 days.
No system is perfect. If we learn of a breach that affects your data we will tell the workspace owners by email without undue delay and, where the law requires, the supervisory authority.
8Your rights
Under the GDPR and similar laws you can ask us for a copy of your personal data, ask us to correct or delete it, restrict or object to how we use it, and take it with you in a machine-readable form. You can also complain to your data protection authority. If you are in California, you have the right to know what we collect and to delete it; we do not sell or share personal data as the CCPA defines those terms, and we will not treat you differently for exercising a right.
Most of this you can do yourself. You can change your name, email and password, turn two-factor on or off, delete monitors, status pages, subscribers and alert channels, remove members and leave a workspace, all from the application. Status page subscribers unsubscribe with the link in any email.
You can delete your account yourself, in the web app under Settings → Profile or in the mobile app under Settings → Delete account; Delete your account walks through it. You confirm with your password, and with a code as well if two-factor is on. Your profile, password, two-factor secrets, sign-in codes and the phones registered for push alerts are deleted at once. A workspace nobody else is in is deleted with the account, with everything in it, and its subscription is cancelled. From a workspace you share you simply leave; if you are its only owner, make someone else an owner first. What your team already has stays with them: comments you wrote on incidents, and activity log lines and alert records that name you. The backups expire 30 days after the deletion, and billing records stay as long as tax law requires.
There is no button yet to delete a workspace on its own while keeping your account. Write to us through our contact form from the owner's address and we delete it within 30 days; the backups expire 30 days after that. Access and export requests go the same way.
For data in your workspace that belongs to your own customers (subscribers, test screenshots), send their requests to us if you need help, and we will act on your instruction.
9Children
The service is for businesses and is not directed at children. We do not knowingly collect data from anyone under 16. If you believe a child has created an account, tell us and we will delete it.
10Changes to this policy
When we change what we collect or who processes it we update this page and the date at the top. For a change that matters to you we email every workspace owner at least 14 days before it takes effect.
11Contact
Questions about this policy or your data: our contact form. Post: Come Back Agency, LLC, 911 Main St Unit 2009, Kansas City, Missouri 64105, United States.
See also the Terms of Service.