Control what gets shown
Privacy-aware personalisation
Consent, retention and deletion rules applied throughout events, profiles, embeddings and trained models.
What it does
The mechanism
- 01
Consent state travels with the data it belongs to, so a person's preferences are honoured at ingestion, in their profile, in the embeddings derived from it and in the models trained on it.
- 02
Access is scoped by tenant and by role, with API keys and OAuth clients created, rotated and revoked from the console.
What it gets you
Three things you can point at
01
Deletion that reaches the model
A deletion request is not complete when the events are gone. Profiles and derived representations are covered by the same policy.
02
Credential lifecycle
Issue, rotate or revoke keys and OAuth clients instantly, scoped to the tenant they belong to.
03
Role-aware teams
Team members see the workspaces their role allows, and support access is separated from tenant data.