The inventory
Go to Terrain > Inventory. There is one row per system that touches the property's data, with both layers side by side:
| Column | Shows |
|---|---|
| System | Name and main domain. Click it to open the system |
| Category | For example analytics or advertising |
| Status | Documented, Undeclared, Review Due, Not Observed or Dismissed, plus a Before Consent flag where it applies |
| Observed | The evidence source (Pulse, Echo, or Manual) and when it was last seen, or "Not detected" |
| Purpose, Legal Basis, Owner | From the declaration, or "Not declared" / "Unassigned" |
| Reviewed | When the declaration was last saved |
Use the status chips (All, Undeclared, Before Consent, Review Due, Not Observed, Documented) and the category chips to narrow the list. Filters are part of the page address, so a filtered view can be bookmarked or sent to a colleague.
Declare a system
- In Inventory, click a system. The page has two panels: Observed (written by scans, read only) and Declared (yours).
- Read the Observed panel: detection status, evidence source, last seen, data flow, and the evidence itself with an example page. If the system was seen sending data before consent, a red box says so at the top of the page.
- In Declared, fill in the fields below.
- Click Save Declaration. Saving stamps today as the review date.
| Field | What to enter |
|---|---|
| Purpose Of Processing | Why this system receives data: Advertising and remarketing, Audience measurement, Product analytics, Personalisation, Customer support, Fraud prevention, Consent management, or Sales and CRM |
| Legal Basis | The ground your organization relies on: Consent, Legitimate interests, Contract, Legal obligation, Vital interests, or Public task |
| Data Categories | What kinds of personal data reach the system: Online identifiers, Device data, Browsing behaviour, Contact details, Location (approximate), Location (precise), Transaction data, Inferred interests, Session recordings, Special category data |
| Recipient | The legal entity receiving the data, not the product name |
| Transfer Region | Where the data is processed |
| Retention Period | For example "14 months" |
| Internal Owner | A team that can answer questions about it, rather than one person who may leave |
| Notes | Anything a reviewer would need to know |
A system needs both Purpose Of Processing and Legal Basis to count as declared. If you choose Consent as the legal basis and the system was observed firing before consent, Terrain flags the contradiction on the system and in the Audit Pack.
The Storage Written panel lists the cookies and storage keys this system writes, with type, expiry and the page they were found on. Their purpose comes from the system's declaration, so declaring the system covers every key it writes.
Dismiss a known and accepted system
Use this when a system is on the gap queue but is known and accepted as it is, so it stops coming back after every scan.
- Open the system. In the Known And Accepted panel, click Dismiss.
- Enter the reason. It is required; a dismissal with no reason looks like someone clearing the queue to make it look clean.
- Click Dismiss in the dialog.
The system stays on the inventory with status Dismissed and your reason, and leaves the Gaps queue. To reverse it, open the system and click Undo Dismissal.
Check it worked
- The system's status changes to Documented (or Dismissed), and the Reviewed column shows today.
- On the dashboard, Coverage rises and Undeclared falls.
- After 90 days without another save, the system moves to Review Due and back onto the Gaps queue. Re-open it and save to re-confirm.
Troubleshooting
| Symptom | Cause |
|---|---|
| "Nothing detected yet" | The property has no scan results in Terrain yet |
| The Observed panel looks wrong | Observed data comes from scans and cannot be edited. Check that the Pulse scan reaches the pages concerned |
| A system shows Not Observed | It was declared but not detected in recent scans: either it was removed, or the scan is not reaching the part of the site where it runs |
| "That system is not in this property's inventory." | The link points at a system from another property |
TagPipes monitors, configures and reports. It does not determine legal compliance and does not provide legal advice. Output is informational and reflects observed state at the time of observation. Confirm any regulatory interpretation with your counsel.