The short version
cadshot turns your 3D/CAD file into an image and then forgets the file. We keep the resulting image for a limited time so that repeat requests are fast, we keep technical logs for a limited time so that we can run and protect the service, and we keep the account details needed to sign you in and bill you.
- Your input file is held in memory or temporary storage only while it is being rendered, then deleted. It is never stored afterwards.
- We never use your files or images to train machine-learning models, or for anything other than your render request.
- Rendered images are cached for at most 30 days and then expire automatically.
- Logs are kept for at most 30 days and never contain file contents or file names.
- The in-browser converter runs on your own device. Files you open in it are never uploaded, so there is nothing for us to retain.
Retention table
| Data | What it is | How long we keep it | How it is removed |
|---|---|---|---|
| Input files | The model you upload, or that we fetch from the URL you give | Only for the duration of the render (at most 10 seconds of render time) | Deleted automatically when the render finishes or fails |
| Rendered outputs | The PNG image, cached under a hash of the file and the render parameters | At most 30 days | Automatic expiry |
| Request logs | Request id, key id, format, triangle count, timings, byte sizes, status, IP address (for abuse prevention and rate limiting) | At most 30 days | Automatic deletion |
| Account data | Email address, hashed API keys, plan, usage counters, billing status | While your account exists | Deleted within [30] days of account closure, except billing records below |
| Revoked API keys | Hash and identifier of a key you revoked | [TO CONFIRM – e.g. deleted with the account, or after 30 days] | Automatic deletion |
| Sign-in links and session | Single-use token sent by email; dashboard session cookie | Token: until used or expired ([15 minutes – TO CONFIRM]). Session: [SESSION LIFETIME – TO CONFIRM] | Automatic expiry; signing out ends the session |
| Billing records | Invoices and the usage totals they are based on; payment records held by Stripe | As long as tax and accounting law requires ([typically 5 years in Poland – TO CONFIRM]) | Deleted after the statutory period |
| Website analytics | Cookieless, aggregated page statistics | Aggregates only; nothing that identifies a visitor is kept | Not applicable |
| Support correspondence | Emails you send us | [Up to 3 years after the last contact – TO CONFIRM] | Manual deletion |
| Backups | Backups of the account database (never of input files; [output cache not backed up – TO CONFIRM]) | [BACKUP RETENTION – TO CONFIRM, e.g. 30 days] | Automatic rotation |
Things to know
We cannot recover your files. Because inputs are not stored and outputs expire, the service is not a place to keep data. Keep your own copies.
Cached images. An identical file with identical parameters produces the same cache key, which is how a repeat request can be answered from the cache. [DECISION: whether cache entries are scoped per account, and whether customers can purge the cache or opt out of caching.]
Legal holds. We may keep specific data longer where the law requires it or where it is needed for a legal claim, and only for as long as that is necessary.
More detail is in the Privacy Policy and the Data Processing Agreement. Questions: [CONTACT EMAIL].