How InternalStatus handles your credentials.

Workspace isolation

Every customer-owned table is protected by row-level security in Postgres, and access is granted through workspace membership rather than checked in application code. A query that forgets to filter by workspace returns nothing rather than someone else’s data.

Credentials

• Connector secrets, provider API keys and OAuth tokens are encrypted before they are written to the database, and are decrypted only in the server-side process that makes the request to that provider.
• Credentials are never returned to the browser and are never written to logs. A signing secret is shown once, at creation, and cannot be retrieved afterwards.
• Where a provider supports OAuth, InternalStatus prefers it over a pasted key, so the provider enforces the scope and you can revoke InternalStatus without rotating a credential your own systems depend on.
• OAuth grants use PKCE wherever the provider accepts it, and the authorization state is single-use, workspace-bound and expiring.

What InternalStatus asks for

Read access, with one exception. InternalStatus polls cost, usage and membership endpoints and receives webhooks; it does not create, modify or delete resources in your providers. The exception is delivery — sending a message to a Slack or Discord channel you connect for that purpose.

Some read scopes are broader than we would like because the provider offers nothing narrower. GitHub’s billing endpoints require organisation administration scope, and there is no billing-only alternative to request.

Incoming webhooks

Every inbound webhook is verified before it is processed: Stripe signatures, HMAC-SHA256 for GitHub, Lemon Squeezy and custom sources, and scoped bearer tokens for agent events. Payloads are redacted of credential-shaped values before storage, and each event is deduplicated on its provider-supplied identifier so a replay cannot double-count.

Data retention

Events, metrics and provider readings are deleted automatically once they pass the retention window of your plan. Retention follows the plan you are actually being given, including during a trial.

What this page does not claim

• InternalStatus is not currently SOC 2 or ISO 27001 certified.
• Data is processed in the regions our hosting and database providers operate in; InternalStatus does not offer customer-selected data residency.
• InternalStatus is a correlation layer above your existing tools. It is not a replacement for monitoring, and it cannot observe anything you have not connected.

Reporting a vulnerability

Email security@binarychakra.com with enough detail to reproduce the issue. We will acknowledge within two business days. Please do not test against workspaces you do not own, and give us a reasonable window to fix an issue before disclosing it.