1. Describe the policy
The reference date, duration and safeguards are declarative. Free-form SQL is forbidden.
Technical journey
An architecture explainable to security teams and auditors alike.
Start with a minimal policy, simulate it, approve its digest and verify the evidence.
2. Build the plan
The planner sends a signed count request; the connector returns aggregates and time boundaries only.
3. Approve the digest
The approver reviews impact, not row contents, then signs an immutable version.
4. Apply and verify
The connector recounts, applies its local policy, deletes in batches and returns a signed result verified by the SaaS.