Data policy
Three modes. One explicit choice.
Nothing trains on your users by default. Pick a mode per project, in plain language, and see exactly what is kept, for how long, and what it is used for.
Contribute
higher quotaHelp the rules and models get better for everyone, and get a bigger allowance on the same plan in return.
- kept
- de-identified samples
- training
- yes, after de-identification
- quota
- higher
Limited retention
you pick the windowKeep your own traffic for a window you choose, so you can replay it against a rule change and see exactly what would flip.
- kept
- content, for 24h to 90 days
- training
- never
- quota
- standard
Zero retention
memory onlyContent exists in memory for the length of the request and nowhere else. What remains is the observability trail.
- kept
- decision, category, latency, stage
- training
- never
- quota
- standard
Retention and contribution are separate switches. Keeping your own data for your own replay never means contributing it to anyone else.
Every mode is an opt-in you can change. The current mode is visible in the dashboard, and switching applies from the next request.