Privacy Policy

This policy describes what InBrief collects, and why.

What we store

• Account data: your email address (used for sign-in and service notices), your plan state and, if you choose a password, a salted one-way hash of it. If you choose Continue with Google, Google tells us your email address and whether it has verified it. We ask Google for nothing else and keep nothing else from it.
• Configuration: the monitors, languages, branding and incident content you enter.
• Monitoring results: HTTP status codes and response times of the endpoints you configure. Response bodies are never stored.
• Subscribers: email addresses, confirmation state, language and service preferences, and subscription and delivery records used to send requested updates.
• Notification destinations: channel settings and encrypted credentials, such as webhook URLs or bot tokens, used to deliver updates to destinations you configure.
• Internal analytics: reporter identifiers, names, region and team metadata, reporting timestamps, aggregated request counts and latency, and error-message samples you send through the Event API. Avoid sending personal data or secrets in error messages.
• External event storage: encrypted warehouse credentials and local reporter metadata remain in InBrief when event history is stored in your warehouse. Failed writes may be buffered locally as aggregated batches.
• Restricted notification previews: enabled WhatsApp previews store recipient names, phone numbers, verification and delivery records. Browser-push previews store subscription endpoints, encryption keys and preferences. These previews are not enabled for general Cloud use.
• Billing: handled entirely by Paddle (merchant of record). We never see or store card details, only Paddle's customer and subscription identifiers.

What we do not do

• No ads inside InBrief or on status pages, no ad targeting, no selling of data, no third-party analytics on status pages.
• No readable passwords: a password is optional, and we keep only a salted one-way hash of it. When you choose one, a short prefix of a one-way hash of it is checked against Have I Been Pwned's public list of breached passwords; the password itself never leaves InBrief.

Processors

These providers handle data on our behalf, each for one purpose:

• Hetzner: hosts the application and the database, in its EU region.
• Cloudflare: DNS, TLS and proxying for inbrief.sh and for status page hostnames, through its global edge network.
• Resend: sends sign-in links, account email and subscriber notifications.
• Paddle: takes payments as merchant of record.
• Google: optional analytics and ad measurement on our homepage, only after you accept them.
• OpenAI and Anthropic: translate your content on plans that include it. A second provider takes over when the first fails. Only the incident or monitor text you wrote is sent, and no provider trains on API data.
• Destinations you configure: Slack, Discord, Microsoft Teams, Telegram, Meta (WhatsApp) and webhooks receive the updates you send them, under your own agreement with each service.

A data processing agreement is available on request from legal@inbrief.sh.

Visitors to status pages

When aggregate status-page analytics is enabled, a public page sets one host-only, HttpOnly, SameSite=Lax cookie containing only the current UTC day. It expires at the next UTC day and is used only to count one browser once per page per day. Aggregate counts are retained for 90 days. No visitor identifier or IP address is retained, no browser fingerprint is created, and no third-party analytics runs on the page. A visitor's browser may cache page data locally (localStorage) purely to show the last known state when offline.

Optional analytics on our homepage

On inbrief.sh, you can choose to let Google Analytics measure homepage visits, traffic sources, selected link clicks and completed account registrations, and let Google Ads measure which of our ads bring visitors to the homepage. Google receives a pseudonymous browser identifier and technical information such as your IP address when your browser contacts it. Google Ads also receives the homepage address you arrived at, including any ad click identifier in it. We do not send your name, email address, account identifier, sign-in token, form contents or private page addresses. Remarketing, ad personalisation and Google signals are disabled, so your visit is not used to show you ads. This tracking does not run on customer status pages, sign-in pages or inside the dashboard.

Google's browser tag loads only after you accept analytics. You can reject analytics and continue using InBrief, or withdraw consent through Analytics preferences. We remember your choice for 180 days. Analytics and ad measurement cookies are restricted to the inbrief.sh host and expire after 60 days. A separate cookie links a completed registration to the consenting browser for up to 30 minutes and is removed after registration. Google Analytics event and user data retention is configured to two months; aggregate reporting may remain available longer. Google processes this data under its privacy policy.

Retention and deletion

Raw check results are deleted after 90 days; monitoring daily uptime aggregates are kept for the life of the account. Internal event history in InBrief storage is retained for 14 days. Reporter metadata has no automatic expiry. Warehouse history follows your warehouse retention settings. The local external-delivery buffer holds at most 2,000 batches per status page, stops retrying after 50 failed attempts, and makes exhausted batches eligible for deletion seven days after creation. Switching back to InBrief storage discards pending external batches. Deleting your account removes all stored data. Requests: legal@inbrief.sh.

Changes to this document

We may update this document. A material change is announced by email to account holders at least 30 days before it takes effect, and the effective date is shown at the top of this page. Until that date the previous version applies. If you do not agree with a change, cancel your subscription or delete your account before it takes effect; continuing to use the service after that date means you accept it.

Three kinds of change take effect on publication, without notice: changes required by law or a regulator, changes that only benefit you (a lower price, a longer refund window, more rights, a new feature), and corrections to wording that do not change the meaning.

Contact: legal@inbrief.sh