What we store, and for how long
| Data | Retention |
|---|---|
| Report artifacts (envelope, screenshots, recordings, logs) | Maximum 30 days, then deleted automatically |
| Attachment download URLs (presigned) | Expire about 1 hour after delivery |
| Lightweight event metadata | May be kept longer for analytics and abuse prevention |
| Account, billing, and configuration | While your account is active, then as law requires |
The 30-day window exists for one reason: to deliver, retry, and dead-letter a webhook. Once that lifecycle is complete the artifacts are purged. Your own receiver (or the advanced dashboard) is the long-term system of record — not the pipe.
Idempotency
The ingest API de-duplicates the same report across the retention window, so an SDK retry never results in a second delivery. Receivers still get a per-attempt delivery id so they can stay idempotent independently. See webhooks.
Keeping payloads minimal
The smallest useful report is the safest one. You control what leaves the device:
- Capture toggles — enable only the capture types you need (screenshot, UI tree, focus, logs, network).
- Sensitive subtrees — mark elements (or secure text fields) as sensitive; their descendants are omitted from the captured UI tree.
- Redaction — users can blur regions of the screenshot before submitting.
- User context is optional — attach an end-user id, email, or display name only when you need attribution.
Your responsibilities and ours
For bug-report data, you are the data controller and TraceItX is your processor: you decide what is captured and are responsible for notice to and consent from your end users; we process it only to deliver it. For the full legal picture see the Privacy Policy, and for how the data is protected in transit and at rest see our security practices. A Data Processing Agreement is available on request from support@traceitx.com.