Security and data

Plain answers about where your data goes.

Changelog Observer stores less than you might expect, never reads your repository, and treats everything a vendor sends as untrusted. This page says exactly what that means.

Tenants

Your workspace sees only your rows.

Row-level security on every table. The database enforces that a session sees only the workspaces it belongs to. Cross-tenant tests run on every change.

Keys re-scope the API. An API key is bound to a workspace and optionally to one project; the API filters every query by it.

The platform never reads your repository. Your agent reads it with the access it already has and sends only the dependency list.

What we store

Events, settings, and the mail you asked us to receive.

Everything lives in one Postgres database, in the region chosen when the project was created. Raw inbound email is kept in object storage for thirty days by default, then dropped; the extracted text and a header subset stay with the event.

Accounts. Your email, display name and sign-in identities; workspace roles; invitation tokens for seven days.

Configuration. Projects, dependencies, sources, rules, destinations, sender rules and preferences.

Events and incidents. The vendor’s title, summary, link and severity; the decision that classified and routed each event; incident timelines with your status and notes; your feedback.

Inbound mail. Sender, subject, a capped text excerpt, a header subset, extracted links and authentication results. The raw message, for thirty days, unless the project opts out of raw retention entirely.

Ticket credentials. A Jira, Linear, GitHub or Statuspage token is encrypted at rest with AES-256-GCM under a key derived from the platform secret, bound to its destination, readable only by the worker that makes the push. It is never returned by any API.

API keys. Only a hash and a display prefix. The key itself is shown once.

Your dashboard layout. Which sections you hid and where you put them. Nobody else can see it.

Vendor mail

Untrusted input, by design.

An inbound address is a routing id, not a secret. Anyone who learns it can send mail to it, so the product decides what to do with a message by who really sent it, not by the address it arrived at.

Authentication first. SPF, DKIM and DMARC results are read from the mail gateway. A message counts as verified only when it authenticates and the authenticated domain belongs to a vendor the project depends on, or to a sender you trusted.

Unverified mail cannot page you. It is stored and shown, capped at normal priority, and never delivered immediately.

Risky mail is quarantined. A spoofed vendor name, a DMARC failure, content that reads like instructions, or an unknown sender using severe vocabulary: the message is held with its reasons, creates no event, and waits for you to release it or trust the sender.

Links are never followed. Except subscription confirmations, and only when you allowed it for the project, the mail was verified for the vendor’s own domain, and the link stays on an allowed host.

Prompt-injection flags. Content that looks like instructions carries a warning through the API and MCP. Agents are told to summarise it, never to act on it.

Size caps and stripping. Mail over the size cap is refused; attachments are not stored, only their names.

Access and audit

Scoped keys, owners and members, a log of everything.

Scoped keys. project:read, project:write and events:read by default; rules:write, destinations:write and workspace:admin are separate, deliberate grants. A key can be limited to one project.

Roles. Owners administer the workspace and its members; members do the work. A workspace always keeps at least one owner.

Audit log. Every write, by a person or an agent, is recorded with the actor, the target and the change.

Rate limits. Reads and writes through the API are rate-limited per key, and inbound mail per project, so one noisy client cannot crowd out the rest.

Operations

Nothing silently lost.

Durable jobs. Every message, poll and delivery is a queued job with bounded retries. A job that fails every retry is kept as a dead letter for the operator to replay or discard, never dropped.

Delivery records. Every webhook and email attempt, with its response, is visible on the Deliveries page.

No model inference. No AI provider is involved in the product today. Classification, priority and deduplication are rules you can read.

Deletion

Yours to remove.

Archive a project. Its inbound address stops routing, its sources pause, and its data is purged after thirty days.

Delete a workspace. Immediate; stored raw mail is queued for deletion.

Delete your account. Workspaces you alone own go with it.

Drop raw mail now. A project can delete its stored raw mail ahead of retention, or switch raw retention off entirely.

Subprocessors

Who else touches the data.

Three providers run the product. Three more are involved only if you add the matching ticket system to a project.

Cloudflare. Hosting for the API, the dashboard, queues, raw-mail storage, inbound email routing and DNS.

Supabase. The Postgres database and sign-in.

Resend. Outbound email: alerts, digests, invitations and sign-in links.

Atlassian, Linear and GitHub. Only for workspaces that add Jira, Statuspage, Linear or GitHub Issues as a destination; they receive the incident summary you push.

Your workspace sees only your rows.

Row-level security on every table. The database enforces that a session sees only the workspaces it belongs to. Cross-tenant tests run on every change.

Keys re-scope the API. An API key is bound to a workspace and optionally to one project; the API filters every query by it.

The platform never reads your repository. Your agent reads it with the access it already has and sends only the dependency list.

Events, settings, and the mail you asked us to receive.

Accounts. Your email, display name and sign-in identities; workspace roles; invitation tokens for seven days.

Configuration. Projects, dependencies, sources, rules, destinations, sender rules and preferences.

Events and incidents. The vendor’s title, summary, link and severity; the decision that classified and routed each event; incident timelines with your status and notes; your feedback.

API keys. Only a hash and a display prefix. The key itself is shown once.

Your dashboard layout. Which sections you hid and where you put them. Nobody else can see it.

Untrusted input, by design.

An inbound address is a routing id, not a secret. Anyone who learns it can send mail to it, so the product decides what to do with a message by who really sent it, not by the address it arrived at.

Unverified mail cannot page you. It is stored and shown, capped at normal priority, and never delivered immediately.

Prompt-injection flags. Content that looks like instructions carries a warning through the API and MCP. Agents are told to summarise it, never to act on it.

Size caps and stripping. Mail over the size cap is refused; attachments are not stored, only their names.

Scoped keys, owners and members, a log of everything.

Roles. Owners administer the workspace and its members; members do the work. A workspace always keeps at least one owner.

Audit log. Every write, by a person or an agent, is recorded with the actor, the target and the change.

Rate limits. Reads and writes through the API are rate-limited per key, and inbound mail per project, so one noisy client cannot crowd out the rest.

Nothing silently lost.

Durable jobs. Every message, poll and delivery is a queued job with bounded retries. A job that fails every retry is kept as a dead letter for the operator to replay or discard, never dropped.

Delivery records. Every webhook and email attempt, with its response, is visible on the Deliveries page.

No model inference. No AI provider is involved in the product today. Classification, priority and deduplication are rules you can read.

Yours to remove.

Archive a project. Its inbound address stops routing, its sources pause, and its data is purged after thirty days.

Delete a workspace. Immediate; stored raw mail is queued for deletion.

Delete your account. Workspaces you alone own go with it.

Drop raw mail now. A project can delete its stored raw mail ahead of retention, or switch raw retention off entirely.

Who else touches the data.

Three providers run the product. Three more are involved only if you add the matching ticket system to a project.

Cloudflare. Hosting for the API, the dashboard, queues, raw-mail storage, inbound email routing and DNS.

Supabase. The Postgres database and sign-in.

Resend. Outbound email: alerts, digests, invitations and sign-in links.

Atlassian, Linear and GitHub. Only for workspaces that add Jira, Statuspage, Linear or GitHub Issues as a destination; they receive the incident summary you push.

Plain answers about where your data goes.

Your workspace sees only your rows.

Events, settings, and the mail you asked us to receive.

Untrusted input, by design.

Scoped keys, owners and members, a log of everything.

Nothing silently lost.

Yours to remove.

Who else touches the data.

Plain answers about where your data goes.

Your workspace sees only your rows.

Events, settings, and the mail you asked us to receive.

Untrusted input, by design.

Scoped keys, owners and members, a log of everything.

Nothing silently lost.

Yours to remove.

Who else touches the data.

Questions about any of this?