Where your data lives

The application, the background worker and the event warehouse run on one UpCloud server in Helsinki, Finland. The database is UpCloud’s managed PostgreSQL in the same region. There is no region choice.

Events and errors live in the ClickHouse warehouse. Accounts, workspaces, projects, boards, watches, event definitions and the metadata of each error issue live in Postgres. Valkey, on the same server, holds caches and rate-limit counters, nothing that outlives them.

UpCloud keeps its own snapshots of the managed Postgres database. The warehouse is the only copy of your events and errors today.

An end user’s IP address is reduced to a keyed, non-reversible hash before it is stored. The address itself is not written anywhere.

Deleting a project or a workspace purges its events and errors from the warehouse.

Billing goes to Stripe, optional sign-in to Google, and email to Resend; each is on the subprocessor list, added before it first touches data. We run no model, so no AI company is a subprocessor. What a coding agent reads over MCP does go to that agent’s model provider, under your agreement with them; the security page covers the grant, the log and what we do not have.