Skip to main content
Drometra

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

DateDeadlineHow it applies
Tracking link for the recipient30 days from issuance, or 14 days from the close of the delivery, whichever comes firstThe link stops working; also when the order is canceled or reissued
Address and content of transactional emails30 daysDeleted by an hourly process; sooner if the email hard-bounces
Email sending log180 daysDeleted by an hourly process
Webhook events and deliveries30 days by default, configurable between 1 and 365Deleted by an hourly process; we never store the destination's response
Michiva usage log90 daysDeleted automatically; never contains the question or the answer
After-hours alerts2 daysDeleted automatically
Import attempts from integrations7 daysDeleted automatically
Approximate address cache7 daysDeleted automatically
Sign-in events1 dayThey expire in the identity system
Positions stored on the phone by Dromivia7 days or 20,000 recordsDeleted on the phone; also upon logging out
Drometra Vision video in the lab cloud24 hoursDeleted automatically
Drometra Vision video on the device7 days by default, configurable between 1 and 30Deleted 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.

DateTarget periodState
Vehicle positions and driver phone positions12 monthsDecided; automatic deletion being implemented
Action audit log12 monthsBeing implemented
Proof-of-delivery photos and signaturesTo be defined with each customerNo automatic deletion; manual, on request
File import batchesTo be definedNo automatic deletion; manual, on request
Expired tracking linksDeletion after 90 daysBeing implemented; today the expired link does not work, but the record is retained
Database backups30 daysBeing 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

DateDeadlineBasis
Trade contact without conversion24 months from last contactSales cycle of the sector
Account and accessContract monitoring + 12 monthsPost-term recitation
Tax documents and accounting6 yearsTax Code and Trade Code
Contracts and their annexes5 years from the endCivil action statute
Support emails36 months from closureTracability of recurrent incidents
Unselected posts12 months, or 24 with your consentFuture processes
Reports to the channel of conduct5 years since closureTracability of the investigation

These periods are managed manually by our team.

05How do we delete

  1. 1.Where an automatic process exists, the record is deleted from active systems when the period expires, without human intervention.
  2. 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. 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. 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. 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.