Integration Core · checked 2026-10-15
What crosses between two systems can carry a customer's name, address or email. Here is what Integration Core keeps, for how long, and how a System Manager erases one person's data when they ask.
What is kept, and for how long
- The full message each connection receives, and its headers, are cleared 30 days after they arrive once the arrival is finished. An arrival that is waiting, failed or unsettled keeps them, because they may be the only copy.
- On Integration Activity, the error text and the waiting reason are cleared 30 days after a record is done or has failed. Copy a failed record's error into your ticket before then. A Skipped record keeps its reason. An incoming record's own copy of the error is not cleared.
- Request Data, Response Data and Content from Connected System are never cleared by time. Only Erase personal data removes them.
- A closed difference is cleared 30 days after it was closed. An open difference keeps its values until someone deals with it.
- Without the site's scheduled jobs, nothing is cleared.
Erase personal data
- Find the person's records on Integration Activity, Incoming Records or Differences — filter by the Reference or the ID in Connected System.
- Tick the records and choose Erase personal data from Actions.
- Read the question and confirm. Your name and the time are recorded on each record, with a comment.
Only a System Manager can erase. It cannot be undone, and a later retry, re-check or the other system sending the change again does not bring the details back.
What it reaches
| Screen | What it clears |
|---|---|
| Integration Activity | what was sent and received (Request Data, Response Data, Content from Connected System), the error and waiting-reason text, and where to fix a wait |
| Incoming Records | what arrived (Received Content, Received Headers) and its error; its tries on Integration Activity are erased with it |
| Differences | the two values and the note on what happened |
An Integration Activity erase keeps what the other system sent on its Incoming Record — erase it there too.
What it keeps
Amounts, currencies, states, references, IDs, times, and any decision note or reason a person wrote — the evidence a money record is reconciled on. A note that itself names a customer is not erased.
Erase personal data even if unfinished
On Integration Activity and Incoming Records, Erase personal data refuses a record that is still being worked on: In progress, Waiting, Set aside, Unverified or Reversal not confirmed. The connection may still decide what to do from those details. Erase personal data even if unfinished erases them anyway. Use it only for a record that will never finish: on a live one, the connection may no longer recognise what it last sent, and an incoming record not yet applied can no longer be applied. Each record's comment records the state it was erased in.
Each connection's own copies
A connector may keep its own copy of a record. After Integration Core's erase, each connection is asked to erase its copies too, where its connector says how — each connector's own page says what it keeps. If a connection cannot, the screen says Not erased by …: a copy kept there may still hold this data, each record gets a comment naming that connection, and the Error Log a line. Integration Core's own erase still stands.
What it does not reach
Alerts already in the bell, emails already sent, and any copy someone exported or printed.