Retention
Data retention and deletion
The platform data is stored at your site. Retention periods are therefore yours: here is what is stored, and the questions to settle before go-live.
Contents
Your data, your retention periods
The platform is installed on your servers, in containers. Photos, analysis results and accounts are stored on your infrastructure. There is no copy on our side, nor in an online service.
Direct consequence: retention periods are not imposed by the vendor. Default values are proposed (365 days for analyses and their images, 30 days for temporary photos received for analysis); they are set at installation, according to your policy, your obligations and how you use the tool. Our role is to tell you precisely what is stored, so that you can decide.
What the platform stores
| Data | What it is used for |
|---|---|
| Rack photos | Basis of each analysis; make it possible to review a result. |
| Analysis results | Detected devices, family, readable model, U position, confidence, “to check” flag, engine and version. |
| Projects | The site each analysis is attached to. |
| User accounts | Name and username; the password is stored only as a hash. |
| Exports | CSV, Excel, PowerPoint, SVG and draw.io files, once downloaded: they follow your own rules. |
The inventory file dropped for a comparison is read only for the time needed to produce the result; it is not kept on the server. Your inventory itself remains in your tool, which keeps its own retention rules: the platform does not access it and writes nothing to it.
The questions to settle
Before go-live, a few simple decisions avoid accumulating data for no reason:
How long to keep photos
A photo serves as evidence as long as the analysis derived from it remains useful. Set the period to match the pace of your surveys: there is no point keeping a photo well beyond the next survey of the same rack.
How long to keep the analyses
Keeping the history makes it possible to follow how a rack evolves between two surveys and to justify an update to your inventory.
Where to store exports
Downloaded reports and inventories leave the platform: they follow the filing and retention rules for your documents.
What to do with inactive accounts
An account that is no longer used is deleted by the administrator, according to your offboarding procedure.
These periods are recorded in your record of processing activities, for the part that concerns personal data.
Deleting data
Two cases arise in practice. The first: a photo captures information that should not have been captured, such as a face or a badge. It must be removed as quickly as possible. The second: data reaches the end of its retention period and must be erased.
In the platform, an analysis is deleted from the History, one at a time: it immediately disappears from the platform. The image files produced remain on the server until the end of the retention period; to remove a photo immediately, your operations team can erase it from the data volume, following a procedure to be specified within the project. At the end of the retention period, an automatic daily purge erases old analyses and their images (365 days by default, configurable at installation, 0 to never purge). Accounts are deleted by the administrator.
Also think about copies: data deleted from the platform may remain in your backups until they expire.
At the end of the contract
Since the data is at your site, the end of a contract raises no question of returning it: you already have it. You can export what is useful to you, then delete the containers and their volumes according to your disposal procedure.
A few simple precautions keep this step clean:
- export the inventory in CSV or Excel and the site reports in PowerPoint that you want to keep as evidence;
- carry over to your inventory tool, which remains the reference, the discrepancies you have decided to correct;
- delete the data volumes, then the copies in your backups, when they expire.
To prepare these decisions with us, contact us.
This page describes the product and how it is designed. It does not constitute legal advice: check how it applies to your context with your DPO, your CISO or your counsel.