Data flow, storage & retention
“Where do my screenshots and recordings actually live? Who can see them? When do they disappear?” — this page walks through the full life cycle of a report in four steps, so you always know where your data goes.
The data flow in four steps
Section titled “The data flow in four steps”- Created locally — screenshots, annotations and recordings are produced entirely inside your browser. Unless you actively share or submit, data never leaves your device
- Submitted or shared on purpose — content is uploaded only after you click “Share” or “Submit”. Uploading is an explicit action; nothing is sent quietly in the background
- Stored server-side — uploaded shares and reports live in server-side object storage (Cloudflare R2); all traffic is encrypted over HTTPS
- Dispatched to integrations — reports bound to an integration are written into your target table (Feishu Bitable / webhook), with a delivery log for every attempt
What stays local, what gets uploaded
Section titled “What stays local, what gets uploaded”| Where | Notes | |
|---|---|---|
| Screenshots, annotations, recordings | Local until you upload | Editing, exporting and trimming never touch the network |
| Share content | Uploaded when you click “Share” | Saved server-side together with the description and technical metadata |
| Reports submitted to a destination | Uploaded when you click “Submit” | Routed into the integration you selected |
| Extension preferences | Always local | Never synced to the cloud |
Retention
Section titled “Retention”| Content | Kept for |
|---|---|
| Anonymous shares (signed out) | 30 days |
| Shares from signed-in users | 90 days |
| Shares from paid workspaces | Long-term |
- Expired content is deleted automatically — no action needed
- Any share can be deleted manually at any time, effective immediately
- Deleting removes both the file and the record; the link stops working right away
Opens the feedback widget — the page URL and title are attached automatically