TRUST

Your telemetry is your data.

Production data is a meaningful trust decision. Here's how we handle yours.

01AI HANDLING

Your telemetry never trains anyone's model

Your telemetry is never used to train AI models. To draft a root cause on paid tiers, the AI layer receives the evidence it needs — service names, error categories, timestamps, and the top error patterns and representative messages from the incident window. That content is never used for training and is not retained by the provider beyond standard abuse-monitoring windows. Statistical detection and rule packs run entirely inside our own infrastructure and never touch an external AI provider.

TRAININGYour telemetry never used for training

RETENTIONProvider-side: standard abuse window only

INPUTSIncident evidence — service, category, timestamps, top patterns + messages

DETECTIONDetectors + rule packs run in-infra · no external AI

02ENCRYPTED

Encrypted in transit and at rest

TLS in transit, modern cipher suites only. Sensitive configuration (notification webhooks, integration credentials) is encrypted at rest. Application database runs on a managed relational backend with provider-side encryption.

TRANSITTLS · modern cipher suites · HSTS

AT RESTEncrypted webhook + integration secrets

DATABASEManaged relational backend · provider-side encryption

03ISOLATION

Tenant isolation on every query

Every read, every write, and every detection query carries account and project identifiers. Ingest streams are tenant-scoped. Concurrency limits apply per tenant so no one's workload starves another.

DATABASEAccount + project ID required on every query

INGESTPer-tenant rate limits and daily byte caps

COMPUTEConcurrency limit per tenant · no shared path

04RETENTION

Retention and deletion

14-day retention during trial. 30 days on Team and Growth. Per-deal retention on the Custom tier. Permanent deletion at end of retention. Tenant-scoped delete on request for GDPR right-to-erasure.

TRIAL14 days · hard delete at expiry

TEAM30 days · hard delete at expiry

GROWTH30 days · hard delete at expiry

CUSTOMPer-deal · scoped retention

GDPRTenant-scoped delete on request

05ACCESS

Access controls

Login via Google today. SAML / enterprise SSO is on the roadmap. API keys are scoped — read, ingest, or both — and listed per-tenant. Alert state changes are recorded with timestamps and actor for after-the-fact review.

LOGINGoogle OAuth · SAML / enterprise SSO on roadmap

API KEYSScoped: ingest · read · both · per-tenant

AUDITAlert state changes recorded with timestamp + actor

06COMPLIANCE

Compliance and deployment

SOC 2 Type II is in progress — we will publish the report here when it's complete, and we won't claim it before then. GDPR-aligned, DPA on request. Primary infrastructure runs in the EU (Germany/Finland); custom residency on the Custom tier. Self-hosted and dedicated deployments on request.

SOC 2Type II in progress · report published here when complete

GDPRAligned · DPA on request

RESIDENCYEU (Germany/Finland) · custom residency on the Custom tier

DEPLOYMENTSelf-hosted and dedicated deployments on request

QUESTIONNAIRESSIG / CAIQ / custom answered within 2 business days

07SUBPROCESSORS

We publish our subprocessors

We don't ask you to take our word for who touches your data. The full list is public, and subprocessors only receive the minimum needed for their function — none of them receive your log content.

INFRAEU data-center provider (Germany/Finland) — compute + storage

EDGECloudflare — CDN, DNS, DDoS, TLS (request metadata, not log content)

AUTHGoogle OAuth — name + email only

BILLINGPaddle — subscription billing (merchant of record)

OPSPostHog (analytics) · New Relic + Sentry (our own monitoring)

LISTFull, current list on the privacy page

Have a security questionnaire?

We answer SIG, CAIQ, and custom questionnaires on request. Procurement, legal, and IT teams welcome.