Privacy controls at the boundary
Tenant-owned schemas, labels, retention rules, and redaction controls make data handling explicit before events become reporting inputs.
Privacy-first event analytics
Custd collects, validates, retains, and prepares event data for reliable analytics and raw replay. It gives product teams one supported path from an accepted event to an answer, with privacy and operational state kept visible throughout.
Custd is currently available through selected HaakCo products and approved integrations. Public self-service registration is not open.
Send product and operational events through supported Custd SDKs. Custd validates each event at the ingestion boundary before accepting it.
Accepted events are durably landed, kept replayable, and prepared into compressed analytical data with visible processing state.
Use tenant-scoped APIs, reports, and operational views to answer product questions without rebuilding the data path in every client.
Analytics is only useful when teams can see what was accepted, how it was handled, and what to do when part of the path needs attention. Custd keeps those responsibilities in the platform rather than distributing fragile workflow code across clients.
Tenant-owned schemas, labels, retention rules, and redaction controls make data handling explicit before events become reporting inputs.
Custd keeps a verified raw landing and provenance for prepared segments, so recoverable failures can be replayed instead of silently losing data.
Small, focused services expose their state and use batching, compression, and bounded background work to run efficiently on modest infrastructure.
The public documentation covers authentication, event collection, tenant configuration, and the APIs available to approved clients. Existing operators can sign in to manage their authorised Custd account.