Skip to content
Need to Know

SECTOR, read 13 Nov 2026

A SaaS auditor asks how a customer's personal data is minimized, recorded and tracked through reporting

The exposure mapThe Finder

A SaaS company is often a processor for its customers and a controller for its own users and staff. The auditor is usually a customer's security team or a regulator, and the first request is a record of what personal data the product stores and where it flows. Product analytics, support exports and customer dashboards all copy personal fields out of the production database.

The European regulation's articles are quoted in this sector through the UK regulator's guides, which follow the same Articles 5, 25, 30 and 32. Customer security questionnaires may also cite a SOC 2 report; that is an attestation, not a regulator, so the asks below stay with regulator text. Each ask lists the evidence and the map stages that hold it.

What an auditor asks

  • Did you design the reporting layer so that personal data protection is built in? Basis: The ICO guide to data protection by design and by default (UK GDPR, mirroring Article 25) says it is about "considering data protection and privacy at the start of everything you do." (ICO: data protection by design and by default, read 13 Nov 2026). Map stages: Warehouse column, Transformation. Show that a sensitivity tag set on a source column travels into the models that copy it. The column and transformation cells show which tools carry the tag; see where a policy stops.
  • Does your record of processing list the recipients of each category of personal data? Basis: The ICO guide on documentation, covering Article 30, says to document "The categories of recipients of personal data" along with purposes and security measures. (ICO: documentation (Article 30), read 13 Nov 2026). Map stages: Report, Viewer, Agent. Show a record that names internal dashboards, customer-facing exports and any agent as recipients. The report, viewer and agent cells show which tools can feed that list.
  • Do you hold only data that is adequate, relevant and limited to your purpose? Basis: The ICO data minimisation guide asks "How do we decide what is adequate, relevant and limited?" and ties the answer to your specified purpose. (ICO: principle (c), data minimisation, read 13 Nov 2026). Map stages: Warehouse column, BI field. Show which personal columns reach a dashboard field and the purpose each serves. The column and BI field cells show whether a tool can list unused personal fields in reports.
  • What technical and organizational security measures, including access controls, protect the data? Basis: The ICO data security guide, covering Article 32, lists data security as "ensuring appropriate access controls are in place and that data is held securely." (ICO: a guide to data security, read 13 Nov 2026). Map stages: Viewer, Agent. Show who can open customer-facing dashboards and what scope an agent connection has. The viewer and agent cells show which tools document either.
  • Can you delete a person's data and make your service providers do the same? Basis: California's CCPA page says the right to delete lets you ask businesses to "delete personal information they collected from you and tell their service providers to do the same." (California Attorney General: CCPA, read 13 Nov 2026). Map stages: Transformation, Report. Show how a deletion reaches derived tables and saved report extracts. The transformation and report cells show which tools follow a field into those copies.

The map cells that answer these asks

These asks need 6 of the six stages: warehouse column, transformation, BI field, report, viewer, agent. None of the 16 tools documents all 6 on 13 Nov 2026; the most is 4, by Alation.

Tools sorted by stages documented, then by the Need to Know total. Read 13 Nov 2026.
ToolWarehouse columnTransformationBI fieldReportViewerAgentDocumentedTotal
Alationdocumentedpartialdocumenteddocumentedpartialdocumented4 of 654.0
Eunodocumentedpartialdocumenteddocumentedpartialpartial3 of 667.0
Atlandocumentedpartialpartialpartialpartialdocumented2 of 665.5
Snowflake Horizondocumentedpartialpartialpartialpartialdocumented2 of 655.5
Databricks Unity Catalogdocumentedpartialpartialpartialpartialdocumented2 of 655.0
Microsoft Purviewdocumentedpartialpartialdocumentedpartialpartial2 of 654.5
Select Starpartialpartialdocumenteddocumentedpartialpartial2 of 653.5
Informaticadocumenteddocumentedpartialnone foundpartialpartial2 of 630.0
Securitidocumentedpartialpartialnone foundpartialdocumented2 of 629.5
DataHubpartialpartialpartialpartialpartialdocumented1 of 661.0
Secodadocumentedpartialpartialpartialpartialpartial1 of 647.5
Collibradocumentedpartialpartialpartialpartialpartial1 of 646.5
Immutadocumentednone foundnone foundpartialpartialpartial1 of 645.0
Ataccama ONEdocumentedpartialpartialpartialnone foundpartial1 of 641.5
Privaceradocumentednone foundnone foundnone foundpartialpartial1 of 630.0
OneTrustdocumentednone foundnone foundnone foundnone foundpartial1 of 626.5

Other sectors

Sources

  1. ICO, data protection by design and by default, read 13 Nov 2026
  2. ICO, documentation, read 13 Nov 2026
  3. ICO, data minimisation, read 13 Nov 2026
  4. ICO, a guide to data security, read 13 Nov 2026
  5. California Attorney General, CCPA, read 13 Nov 2026
  6. EDPB, Guidelines 4/2019 on Article 25, read 13 Nov 2026

Last reviewed 13 Nov 2026.