Plan file retention and secure deletion
Decide how long originals and outputs remain available and how private product files are handled.
CategoryAccount and security
Steps4
Checklist6 verification points
Need help?Use workspace support
Choose a business retention period
Balance repeat-output needs, contractual requirements and the sensitivity of unreleased products.
Separate active and archival needs
Keep active production readily available and move long-term masters only under an agreed storage policy.
Restrict access by assignment
Customer and vendor roles should see only the files required for their work.
Request and verify deletion
Record deletion requests and recognise that limited encrypted backups may expire on a separate controlled schedule.
Questions teams ask before production.
01Are files used to train general-purpose models?＋
Rupato’s privacy notice says not without a separate written agreement.
02Does deletion instantly remove every backup?＋
Active copies are removed while limited encrypted backups may persist temporarily under controlled expiry.
03Should source images be emailed to support?＋
No. Keep private files in the controlled workspace and share order references.
ONE ORDER OR A COMPLETE CATALOGUE
Make the brief clear before the first file moves.
Rupato keeps uploads, specifications, tasks, review and delivery attached to the same production record.
Start an order ↗