How does MonkeyCode handle data retention?
Data retention for a self-hosted MonkeyCode deployment is governed by how you configure environments, logs, and backups, not by a fixed vendor policy. Public materials do not specify universal retention defaults.
Important context
Map what each component retains — task state, execution environments, logs, model-provider request data, and backups — and apply your own retention and deletion rules. Connected model endpoints have their own terms.
| Retention policy | Deployment-configured |
|---|---|
| Components | Task state, logs, environments, backups |
| Model provider | Separate terms apply |
| Defaults | Not universally documented |
What to do next
Inventory retention for each component and connected endpoint, then set explicit retention and deletion rules for your compliance regime.