This document states how long UDISOFTBOX CONSULTORIA E TECNOLOGIA LTDA ("INGESTIA") keeps each record it creates while operating the ingestia.io platform, why it keeps it and on which legal basis — and what happens when the deadline passes. It forms part of the Privacy Policy.
The tables in section 2 are not descriptive: they are the same list the purge program reads in order to delete. The deadline published here and the deadline executed by the system are, by construction, the same value.
1. The two sides of the line
INGESTIA handles two very different sets of data, and retention works in opposite ways for each:
| Who sets the deadline | Where it is described | |
|---|---|---|
| The Customer's business data (what they load, transform and analyse) | The Customer. INGESTIA is the processor; the deadline is the controller's instruction | The Data Processing Agreement (DPA) and the environment's own settings |
| The Platform's operational records (audit, runs, deliveries, alerts, website telemetry) | INGESTIA, through the tables below | This document |
INGESTIA does not delete on its own initiative the business data inside an active customer's environment. Doing so would mean deciding, in the controller's place, the end of a processing activity that is not ours.
2. Deadlines for operational records
2.1 Audit, delivery and acquisition records
| Record | Deadline | What for | Legal basis |
|---|---|---|---|
| Audit trail (who did what, with the SQL and the cost of the run) | 730 days | Incident investigation and accountability | Legal obligation/record of operations (art. 7, II and art. 37) and legitimate interest (art. 7, IX) |
| Report run that was delivered (the number that reached the page) | 365 days | Proof of what was delivered to the Customer | Legitimate interest and regular exercise of rights (art. 7, IX and art. 10) |
| Dashboard run (materialised snapshot and cost) | 90 days | Operational cache and refresh history | Legitimate interest (art. 7, IX) |
| Delivery receipt (e-mail, WhatsApp, webhook) | 180 days | Proof and tracing of the delivery | Legitimate interest (art. 7, IX) |
| Alert firing | 180 days | History of what fired, when and to whom | Legitimate interest (art. 7, IX) |
| Commercial enquiry that did not convert | 730 days | Prospecting; once the deadline passes without a contract, it leaves on minimisation grounds | Consent and/or legitimate interest (art. 7, I and IX), with minimisation (art. 6, III) |
| Website visitor funnel event | 365 days | Measuring what works in our outreach across an annual cycle | Legitimate interest (art. 7, IX), with minimisation (art. 6, III) |
| Visitor per-page engagement (active time, scrolling, clicks) | 180 days | Diagnosing the journey and fixing the page | Legitimate interest (art. 7, IX), with minimisation (art. 6, III) |
The last two concern people who merely visited the website and never became customers. They are here with a deadline because collecting visitor behaviour with no discard deadline is the opposite of minimisation. What is collected is described in the Website Privacy Notice.
2.2 Ingestia Academy records
| Record | Deadline | What for | Legal basis |
|---|---|---|---|
| Certification exam attempt (the drawn paper, the answers, the score per domain) | 730 days | Supporting the issued credential throughout its 24-month validity, the candidate's appeal and fraud investigation | Performance of a service requested and regular exercise of rights (art. 7, V and VI); legitimate interest — integrity of the certification (art. 7, IX) |
| Lesson quiz attempt (answers and score) | 730 days | Progress and best result per lesson while the credential is valid | Performance of a service requested (art. 7, V); legitimate interest (art. 7, IX), with minimisation (art. 6, III) |
| Academy telemetry (exam started/submitted, credential issued/verified, rate limit) | 365 days | Diagnosis and fraud prevention | Legitimate interest (art. 7, IX) |
An exam attempt counts its deadline from submission; an attempt that expired without being submitted counts from its start. Without that, the abandoned paper would stay forever — precisely the one with no value in keeping.
2.3 Run records: two dates, and why
A pipeline run, an agent run, a flow run, a query run and a publishing-pipeline run each leave two kinds of record on the same row: a summary (status, duration, cost, volume) and a detail (the run log, the SQL executed, each step's output). They do not hold the same value over time: the log loses its usefulness within weeks, whereas the summary is what explains the invoice and a year of history.
That is why retention here has two deadlines: the detail is emptied first and, later, the whole row is deleted. It is minimisation applied inside the record, not only to it.
| Record | Detail emptied at | Row deleted at | Legal basis |
|---|---|---|---|
| Pipeline run (status, volume ingested, cost — run log) | 90 days | 365 days | Performance of contract and billing (art. 7, V); legitimate interest (art. 7, IX), with minimisation (art. 6, III) |
| Task of a pipeline run (log and SQL of the attempt) | 30 days | 90 days | Legitimate interest (art. 7, IX), with minimisation (art. 6, III) |
| Agent run (cost and provenance — steps and the configuration used) | 90 days | 365 days | Performance of a service requested and billing (art. 7, V); legitimate interest (art. 7, IX) |
| Flow run (status and cost — the data that triggered it) | 90 days | 365 days | Performance of a service requested and billing (art. 7, V); legitimate interest (art. 7, IX) |
| One box of a flow in one run (the box's input and output) | 30 days | 90 days | Legitimate interest (art. 7, IX), with minimisation (art. 6, III) |
| Query run (bytes and cost — the SQL text) | 90 days | 365 days | Performance of contract and billing (art. 7, V); legitimate interest (art. 7, IX) |
| Help Assistant conversation turn (question and answer — cited sources) | 90 days | 365 days | Performance of a service requested (art. 7, V); legitimate interest — support (art. 7, IX) |
| Publishing-pipeline run (what was sent and the outcome — the environment's previous state) | 90 days | 365 days | Legitimate interest — change record (art. 7, IX), with minimisation (art. 6, III) |
| Step of a publishing-pipeline run (the step's log) | 90 days | 180 days | Legitimate interest (art. 7, IX), with minimisation (art. 6, III) |
| Processing cluster session (hours and cost — installed libraries) | 90 days | 365 days | Performance of contract and billing (art. 7, V); legitimate interest (art. 7, IX) |
| Prepaid account entry (top-up and charge, with the resulting balance) | — | 1,825 days (5 years) | Legal and tax obligation (art. 7, II; Brazilian Tax Code art. 173 and 174) and regular exercise of rights (art. 7, VI and art. 10) |
The last one is the longest deadline in this entire policy, and that is deliberate: a prepaid account entry is a financial statement, not an operational record. It is the proof of what the Customer paid and of what was debited, for both sides. Deleting it on a log's schedule would destroy the Customer's defence in a billing dispute — and ours. It also has no "detail to empty": the row is small and necessary in full.
The run detail is deleted before the summary it belongs to — never the other way round. A summary without its detail is a poorer history; a detail without its summary would be an orphan record that nobody can explain or trace back.
3. How the deadline is enforced
- The purge runs automatically, once a day.
- It counts the deadline from a date defined per record — creation, queueing, firing, start, end or last update, according to the nature of each one — and deletes whatever lies beyond it. When a record's primary date may be empty (an exam never submitted, a step that never started), the deadline counts from the declared alternative date; a record with neither of the two is not deleted, because with no date there is no deadline passed.
- It deletes in successive batches, until no expired record is left, with a time budget per run. The batch limits each pass so as not to lock the database; the budget limits the run. If the budget ends before an accumulated backlog is exhausted, the remainder leaves on the following run — and that is recorded in the run's result.
- A failure is an incident, not silence. If the purge of any record fails, the run is marked as failed and flagged to operations. A purge that does not purge is a broken promise to the data subject, and it cannot end by reporting success.
Until October 5, 2026 the first six deadlines in section 2.1 were declared internally and were not executed by any routine. The publication of this document accompanies the entry into operation of the automatic purge. We record the date because transparency about a deadline includes transparency about when it began to be met.
On October 6, 2026 the two remaining gaps were closed: the Academy records (section 2.2) began to be actually purged — until then they had a published deadline and no routine executing it — and the run records (section 2.3) were given a deadline, which they previously did not have at all. On the same date, the fixed ceiling of rows per run was replaced by the time budget described above: with a fixed ceiling, a daily volume larger than it let the queue of expired records grow forever.
4. What has no deadline, and why
From October 6, 2026, every deadline declared in this policy is executed by a routine. There is no published deadline waiting for someone to execute it. What remains without a deadline is only the following, each for a reason of its own:
- Ingestia Academy certification credentials. They are a public record, verifiable by third parties, and live until any revocation. On account deletion the credential is not deleted: it is anonymised — the holder's name leaves, the verification keeps answering. The opposite would leave an orphan credential bearing the name of someone who asked to be erased.
- Account and contracting records (registration data, billing, contracts). They follow the applicable statutory and limitation periods, not a deadline of our choosing.
- The Customer's business data in their own environment (section 1): the deadline is the controller's instruction, not ours.
5. Backups
A backup is not a working copy. When a record is deleted from the active database, it may remain for a time in a backup until that backup's cycle ends. During that period the copy is isolated, does not return to ordinary use and does not feed any feature. This is the treatment set out in the DPA.
6. End of contract and deletion requested by the data subject
- End of contract: the Customer may export their data during the term and for 30 days after termination; after that, active data is deleted within 30 days, as set out in the DPA.
- Deletion requested from inside the Platform: a data subject holding the owner role may request deletion of the environment and the account from the settings screen itself. The request opens a 30-day grace period, and only after it is the erasure executed — automatically, by a daily routine. During the grace period: nothing is deleted, the environment keeps working (querying and exporting still function), a notice appears on every screen with the days remaining, and the request can be cancelled at any time from the same screen. Only scheduled runs are paused, so that no credit is spent on data that is going to be deleted. The grace period exists because erasure is irreversible: it is the interval in which a request made by mistake — or by someone who should not have had access to the account — can still be undone.
- Request to the Data Protection Officer: any data subject may exercise the rights in art. 18 of the LGPD through the privacy channel, including erasure, confirmation of processing and portability.
7. Changing a deadline
Changing a deadline in these tables is a change to the system, not just to the text: it is the same list. A material change is published here with a new update date, and is recorded in the Version History.
8. Contact
Data Protection Officer: Encarregado de Dados (DPO) — encarregado@ingestia.io · Channel: privacidade@ingestia.io