---
title: "Data retention and deletion"
description: "What MIOSA keeps, for how long, and what \"delete\" actually removes for sandboxes, snapshots, the audit log, usage records, and stored data."
last_updated: 2026-10-11
url: https://miosa.ai/docs/data-retention
---

# Data retention and deletion

This page describes what MIOSA keeps and for how long, and what each delete operation removes. Where a retention window is not published, the page says so rather than guessing.

## Sandboxes

Deleting a sandbox (`DELETE /api/v1/sandboxes/{id}`) permanently deletes the record, removes its saved filesystem state, and settles billing. There is no undo. Use pause when the user is done for now but may come back.

A paused sandbox keeps its workspace until it is destroyed. Destroy it when the saved state should be removed.

## Snapshots

Snapshots have their own lifecycle and can end in a `deleted` state, either because you deleted them or because a retention policy removed them. Deleting a snapshot does not affect sandboxes that were previously restored from it. See [Snapshots and persistence](https://miosa.ai/docs/develop/snapshots.md) for the full status list.

If you are relying on a specific retention window for snapshots, confirm it for your tenant before you depend on it.

## Audit log

Egress audit events are retained for **90 days** for every tenant, and longer on enterprise plans. The [Egress API](https://miosa.ai/docs/api-reference/egress.md) documents the audit query endpoint and its retention.

The audit log is for security and compliance, not billing. Usage records are separate and carry the same attribution.

## Usage and credit records

Usage records drive billing and chargeback. Credit balances and transactions are read through the [Credits API](https://miosa.ai/docs/api-reference/credits.md); credits expire **180 days** from purchase.

## Webhook events

Failed webhook deliveries are retried eight times over roughly **15.5 hours** (within a 24-hour window). After that the event is dropped, so if you need to backfill missed events, read the audit log or usage records instead of relying on redelivery.

## Volumes and stored data

Sandboxes and storage services are separate lifecycles. Destroying a sandbox does not delete a [Volume](https://miosa.ai/docs/data/volumes.md) or an object storage bucket; delete those explicitly when their data should go.

## Stricter retention

MIOSA does not publish a zero-data-retention mode. If you need stricter or shorter retention than the defaults here, contact [support](https://miosa.ai/docs/support.md) to discuss the terms for your tenant before you build on them.

- [Snapshots and persistence](https://miosa.ai/docs/develop/snapshots.md): What survives pause, restore, and fork, and what a snapshot does not save.
- [Audit log](https://miosa.ai/docs/security/audit-log.md): What every audit row records and how to query it.
- [Support](https://miosa.ai/docs/support.md): How to reach the team for retention and compliance questions.
