Retention and abolition policy
- Last update
- 7 October 2026
- Version
- 2.0
- To whom it applies
- Customers and data holders
In summary
- We separate the periods the platform already applies automatically from those still applied manually or being implemented.
- Tracking links, emails, webhooks, Michiva logs, and other short-lived data are already deleted automatically.
- Vehicle positions (12 months), the audit log, delivery photos and signatures, and backups do not yet have automatic deletion.
- Deletion of an entire company at the end of the contract is currently carried out on request, within committed time frames.
This summary guides the reading and does not replace the text of the document.
01How a time limit is set
A retention period is based on three questions: what is the purpose of keeping the data, what legal obligation does it require to retain even if the purpose has been extinguished, and what period of limitation makes it prudent to retain it to defend or exercise a right.
For fleet data, the period is decided by the customer, which is the controller. The values on this page are the ones we apply if the contract does not set others.
02Periods already applied automatically
| Date | Deadline | How it applies |
|---|---|---|
| Tracking link for the recipient | 30 days from issuance, or 14 days from the close of the delivery, whichever comes first | The link stops working; also when the order is canceled or reissued |
| Address and content of transactional emails | 30 days | Deleted by an hourly process; sooner if the email hard-bounces |
| Email sending log | 180 days | Deleted by an hourly process |
| Webhook events and deliveries | 30 days by default, configurable between 1 and 365 | Deleted by an hourly process; we never store the destination's response |
| Michiva usage log | 90 days | Deleted automatically; never contains the question or the answer |
| After-hours alerts | 2 days | Deleted automatically |
| Import attempts from integrations | 7 days | Deleted automatically |
| Approximate address cache | 7 days | Deleted automatically |
| Sign-in events | 1 day | They expire in the identity system |
| Positions stored on the phone by Dromivia | 7 days or 20,000 records | Deleted on the phone; also upon logging out |
| Drometra Vision video in the lab cloud | 24 hours | Deleted automatically |
| Drometra Vision video on the device | 7 days by default, configurable between 1 and 30 | Deleted on the device |
03Periods not yet applied automatically
For these categories, the period has been decided or proposed, but automatic deletion does not yet exist. In the meantime, the data is retained and, at the request of the customer or the data subject, we delete it manually.
| Date | Target period | State |
|---|---|---|
| Vehicle positions and driver phone positions | 12 months | Decided; automatic deletion being implemented |
| Action audit log | 12 months | Being implemented |
| Proof-of-delivery photos and signatures | To be defined with each customer | No automatic deletion; manual, on request |
| File import batches | To be defined | No automatic deletion; manual, on request |
| Expired tracking links | Deletion after 90 days | Being implemented; today the expired link does not work, but the record is retained |
| Database backups | 30 days | Being implemented; today backup deletion is manual |
Why we publish it this way
A policy that promises periods the system does not meet is worse than one that discloses what is pending. We will update this table as each automatic deletion goes into production.
04Data for which we are responsible
| Date | Deadline | Basis |
|---|---|---|
| Trade contact without conversion | 24 months from last contact | Sales cycle of the sector |
| Account and access | Contract monitoring + 12 months | Post-term recitation |
| Tax documents and accounting | 6 years | Tax Code and Trade Code |
| Contracts and their annexes | 5 years from the end | Civil action statute |
| Support emails | 36 months from closure | Tracability of recurrent incidents |
| Unselected posts | 12 months, or 24 with your consent | Future processes |
| Reports to the channel of conduct | 5 years since closure | Tracability of the investigation |
These periods are managed manually by our team.
05How do we delete
- 1.Where an automatic process exists, the record is deleted from active systems when the period expires, without human intervention.
- 2.Where it does not, deletion is carried out by our team upon written request to [email protected], within 30 days, and it is documented.
- 3.When a contract ends, the customer has 60 days to export; afterward, or earlier if so instructed, we delete their data from active systems within 30 days.
- 4.Backup copies are encrypted and are not used to reconstruct deleted data. Until automatic rotation is in production, deletion of backups containing data of a customer whose contract has ended is done manually.
- 5.When deletion is not possible without compromising the integrity of a dataset —an aggregate series, for example— we apply irreversible anonymization instead and disclose it.
Anonimization only counts as such if it is irreversible. Replacing a name by a stable identifier is pseudonimization, remains personal data and remains subject to the term.
Status of this document
Text prepared by Drometra and pending review by external legal advice before its final publication. Its structure and content were built on the current Chilean legislation and on Law 21.719, which has been in force since 1 December 2026. It does not constitute legal advice for third parties.
Related documents
- Platform privacyHow we process the fleet, route, delivery, driver, recipient, and video data generated by a customer's operations, in the console, Michiva, Dromivia, Drometra Vision, and Drometra Spaces.
- Privacy policyWhat personal data we process, in which products, where it is stored, how long we keep it, how we use artificial intelligence models, and how you exercise your rights.
- Privacy in DromiviaWhat data the field app records during the workday, what permissions it requests, where it stores them, and when it deletes them.
- Video and biometryHow Drometra Vision captures, processes, stores, and deletes video, and why it does not process biometric data today.
