Support

Email support@inbrief.sh. A person reads every message, and you don't need an InBrief account to write to us. We reply within two business days, usually much sooner.

What you can ask us about

• Setting up or changing monitors, incidents, your status page, subscribers and alerts.
• Something in InBrief that looks broken, or doesn't do what the documentation says.
• Signing in and managing your account.
• Questions about a charge or a capability you pay for.
• The public APIs, webhooks, badges and feeds.

The troubleshooting guide starts from the symptom and often has the answer. If it doesn't, write to us.

What helps us answer quickly

• The email address you sign in with, if you have an account.
• The address of the status page it concerns.
• What you expected, what happened instead, and roughly when, with the timezone.
• For an API call, the response status and the request ID.

Sending diagnostic details safely

Please leave out API keys, access tokens and webhook addresses. We never need them to help you. The same goes for heartbeat URLs, webhook signing secrets and database passwords: each one works as a password on its own.

• In a command, log or error message, replace each secret with REDACTED before you paste it, and keep the rest as it was.
• Leave out subscriber email addresses and your own customers' data.
• Crop or blur screenshots so they show only the screen in question, not other browser tabs or private details.

If you send a secret by mistake, treat it as exposed and replace it where you created it.

Your data

The privacy policy sets out what InBrief stores and for how long. To ask for a copy of your data, or for it to be deleted, email legal@inbrief.sh. Deleting your account removes all stored data.

Billing

Questions about a charge can come to the support address. Refund requests go to legal@inbrief.sh, as the refund policy explains, and you can cancel at any time from Billing in your dashboard.

Security

If you think you've found a security problem, email security@inbrief.sh rather than the support address, and please give us the chance to fix it before telling anyone else. Our security.txt lists the same address.