How ingestia.io handles personal data: how long each item is kept, what is customer data vs. platform data, and how to fulfill the data subject's rights (access, portability and erasure).
Controller × processor boundary (read first)#
This changes who is responsible for each piece of data:
- ingestia.io is a PROCESSOR of the datalake (analytical data and file area): the business data the customer ingests belongs to the customer (controller). A final data subject of the customer's customer is served by the customer itself, using the export tools via service account and datalake erasure.
- ingestia.io is CONTROLLER of account/operational data: authentication, members, audit trail, marketing (leads) and delivery receipts. It is about these that the platform answers directly.
Retention policy (control database)#
Declarative and auditable retention periods, with purpose and legal basis:
| Resource | Retention | Counted from | Purpose (summary) |
|---|---|---|---|
| audit log record | 730 days | createdAt | security/operations trail |
| Report run | 365 days | createdAt | immutable snapshot of the report sent |
DashboardRun | 90 days | createdAt | snapshot/refresh (operational cache) |
DeliveryReceipt | 180 days | queuedAt | proof of delivery |
| Alert event | 180 days | firedAt | alert firing history |
Lead | 730 days | updatedAt | marketing lead without conversion (minimization) |
| Exam attempt (Ingestia Academy) | 730 days | submittedAt (or startedAt, if never submitted) | backs the credential during its 24-month validity |
| Quiz attempt (Ingestia Academy) | 730 days | createdAt | progress and best result per lesson |
| Ingestia Academy event | 365 days | createdAt | operational telemetry without PII |
The policy is the single source of truth for retention periods; the calculation of what has expired feeds the purge. A resource without a defined policy never expires by mistake — this is the case of the Ingestia Academy credential, which is a publicly verifiable record and lives until revocation (see below).
DSAR — access and portability (art. 18, I/II/V)#
The DSAR report gathers, by the data subject's email, everything that the control database holds linked to them — each section declaring the source (table + fields) and the matching criterion, with the collection date (verifiability).
Sources covered: User (login registration), Member (participation in the workspace),
audit log record (actions of the data subject — without raw SQL), DashboardAnnotation
(comments and mentions), UserDashboardView (personal views), DeliveryReceipt,
alert events and marketing contacts. In its own group, the Ingestia
Academy (global data subject base, outside the workspace): learner profile
(certificate name, consent and option to hide the name), enrollments, progress
aggregated by course, exam attempts (date, certification, status and score —
never the form, the answers or the answer key), challenge submissions
(date, certification, approval) and credentials (public code, certification,
issuance, validity, revocation — without signature or identity hash).
- Never includes secrets (password, TOTP, hash) nor raw SQL (which may contain third-party data).
- Output in JSON (portability) and Markdown (reading by the data subject).
- Out of scope: the customer's datalake (business data) — served by the customer as controller.
Account and data deletion (right of erasure — art. 18, VI)#
30-day grace period, with undo
Requesting deletion deletes nothing right away. In Settings, in the Danger zone — Delete account and data section, you type the confirmation and click Delete account and all data (in 30 days). From then on:
- a 30-day grace period starts. A red banner at the top of every screen shows how many days are left, and the Danger zone card shows the date and who requested it;
- the environment keeps working: you sign in, query and export your data normally (it is your right before leaving);
- only scheduled runs are paused, so no credit is spent on data that will be deleted. Running manually is still possible;
- you are not signed out: to give up, click Cancel the deletion (on the banner or on the card). Nothing was deleted and scheduled runs come back in the next cycle.
After the 30 days, the deletion runs by itself and is permanent. We do not send a warning email: the banner and the card on screen are the official notice.
Request made outside the product
When the erasure request arrives through the privacy channel (privacidade@ingestia.io) and is handled by our team, the deletion is carried out without the grace period.
What the deletion removes
When the grace period ends, the deletion orchestrates the complete removal of the workspace, step by step and best-effort (an isolated failure does not block the rest):
Cancel the subscription
Ends billing at the payment provider.
Delete the workspace's datalake
Removes the workspace's analytical datasets (Bronze/Silver/Gold) from the datalake.
Remove the control database
Deletes the workspace's dashboards, queries, sources and relations, and the workspace itself.
Data subject erasure (optional)
When requested, removes sessions and linked accounts; then, in the same transaction, anonymizes the Ingestia Academy credentials and deletes the user record (User). If anonymization fails, the user is not deleted (fail-closed) and the step is marked for reprocessing.
Record in the audit log
Writes
account.deletedto the global trail (accountability).
Ingestia Academy credentials
The certification credential is a public verifiable record: the verification
page by code must keep responding even after the account is gone — a false
"not found" would tell an employer that it never existed. Therefore, on
account deletion, each credential of the data subject is anonymized and
revoked, not deleted: the name becomes "Titular removido", it stops being
displayed, the credential is marked as revoked for conta_excluida (a credential
already revoked earlier keeps the original date and reason) and loses the link
to the account. Profile, enrollments, progress, quiz/exam attempts and challenge
submissions are deleted along with the user; telemetry events lose the
reference to the data subject.
Independently of deletion, the data subject has the right to hide the name on the public verification page (the page then shows only the code and the status "valid/revoked"); publishing the name requires explicit consent at the time of issuance. The DSAR lists everything the Academy keeps about the data subject (previous section), always without the exam content.
Irreversible action
After the 30-day grace period, data deletion is permanent. Export what you need to preserve during the grace period.
Plan and permissions#
- Operational governance/LGPD: from Business on (PII governance, audit) — see Plans.
- Who performs it: exporting DSARs, reviewing access and requesting deletion are actions of the workspace owner (billing/security).
Example#
A former employee of Comércio Aurora (fictional) requests their data. Maria (owner)
generates the DSAR for ana@example.com: she receives a JSON/Markdown with registration,
participation, audited actions (without raw SQL), comments, views and deliveries.
Later, when the contract ends, she requests the total deletion of the workspace.
Expected outcome#
- DSAR: verifiable report with sources, fields, criteria and collection date.
- Deletion request: red banner with the remaining days and Cancel the deletion available for 30 days.
- Deletion (at the due date):
ok: truewith the list of executed steps; data removed.
Security and privacy#
- Minimization: only necessary fields go into the DSAR; secrets never leave.
- Workspace scope: DSAR and deletion always operate within the session's workspace.
- Auditable: deletion records
account.deleted. - Academy fail-closed: the user is deleted only after the Ingestia Academy credentials have been anonymized — a public name never remains on an orphaned credential.
Limits#
- Retention/purge covers the control database, not the customer's datalake (controller governance).
- Periods are conservative and explainable; changing them alters the single source of truth of the policy (product decision, not self-service per workspace).
- Deletion is best-effort per step: an unavailable dependency does not prevent the other steps, but may require reprocessing.
Common errors and how to fix them#
| Symptom | Likely cause | What to do |
|---|---|---|
| I want to give up the deletion | 30-day grace period in progress | Cancel the deletion on the red banner or in Settings |
| Pipelines stopped running on their own | a scheduled deletion pauses scheduled runs | cancel the deletion, or run manually what you need to export |
| "Empty" DSAR | data subject without records in the sources | expected; the absence is itself verified evidence |
| DSAR without the SQL of the actions | intentional omission (third-party data) | expected behavior (privacy) |
Deletion with a :error step | isolated dependency unavailable | reprocess; the other steps already ran |
| "My business data did not come" | the datalake belongs to the controller (customer) | served by the customer, not by the platform |
Deletion with academy-anonymize:error and db-user:skipped | anonymization of the Academy credentials failed | reprocess the deletion; the user was preserved on purpose (fail-closed) |
| Academy credential still responds after deletion | expected behavior (public verifiable record) | it shows as revoked, without a name and without a link to the account |
Related#
- Audit logs
- Row-level security (RLS)
- Users, groups and permissions
- Legal documents: Privacy · DPA · Subprocessors
Last reviewed: 2026-10-05.