Executive Summary
A structural weakness in conventional corporate compliance programmes is their excessive focus on static legal documents rather than active information flows. True data privacy, security, and information governance cannot be achieved through one-off drafting exercises; they require a continuous lifecycle approach. This report details the Insight Keepers Data Lifecycle, outlines operational requirements for data discovery, classification, and lineage mapping, and introduces key telemetry metrics to measure and report lifecycle compliance.
1. The Insight Keepers Data Lifecycle
Personal information processed by modern enterprises and complex artificial intelligence models is highly dynamic. It travels through multiple departments, applications, databases, and third-party SaaS platforms. The Insight Keepers platform models compliance as an active lifecycle spanning ten distinct phases:
THE INSIGHT KEEPERS LIFECYCLE
┌───────┐ ┌─────────┐ ┌──────────┐ ┌───────┐ ┌───────────┐
│Discover─────┼─────────┼─────┼──────────┼─────┼───────┼─────┼───────────┤
└───────┘ │ Collect │ │ Classify │ │ Store │ │ Transform │
└─────────┘ └──────────┘ └───────┘ └─────┬─────┘
│
┌────────┐ ┌───────┐ ┌───────┐ ┌────────┐ ┌────────▼┐ │
│ Delete ◄─────┼───────┼─────┼───────┼─────┼────────┼─────┼─────────┤ │
└────────┘ │ Retain │ │ Share │ │ Use │ │ Analyse │◄─────┘
└───────┘ └───────┘ └────────┘ └─────────┘
- Discover: Proactively scan systems to locate and catalog personal data.
- Collect: Ingest personal information lawfully, adhering to minimality principles.
- Classify: Apply taxonomic tags to separate personal, special, and commercial data.
- Store: Secure data in authorized physical and digital storage spaces.
- Transform: Standardise, structure, and pseudonymise data for active utilization.
- Analyse: Query, model, and interpret data to extract business intelligence or train models.
- Use: Deploy model-driven insights to make decisions, execute actions, or power software.
- Share: Safely transfer data to authorized external partners, collaborators, or operators.
- Retain: Preserve records securely in accordance with formal retention schedules.
- Delete: Execute secure, permanent de-identification or irreversible destruction.
2. Operationalizing Data Discovery, Classification, and Lineage
To build a sustainable Trust Intelligence platform, organisations must establish technical controls across three operational pillars:
Pillar A: Data Discovery
An organisation cannot govern information it cannot identify. The Insight Keepers platform integrates with corporate technology stacks to automatically discover personal data residing across nine primary environments:
- Structured Databases (Relational databases, SQL servers)
- Cloud Storage (AWS S3 buckets, Google Cloud Storage, Azure Blobs)
- Unstructured Documents (PDF reports, Word documents, text transcripts)
- Corporate Emails & Communications (Exchange, Gmail, Slack logs)
- Data Warehouses & Analytical Warehouses (Snowflake, BigQuery)
- Data Lakes (Hadoop clusters, unstructured raw storage)
- Application Programming Interfaces (APIs) (In-transit data exchanges)
- AI Systems & Model Registries (Model weights, prompts, fine-tuning sets)
- SaaS Platforms (CRM, HR systems, ERP platforms)
Pillar B: Data Classification
Once discovered, data must be classified. Classification acts as a control input, dictating the level of technical protection (such as encryption, 2FA, or restricted access) a dataset receives. Information must be classified under nine operational categories:
- Personal Information: Identifiable living individuals (names, emails).
- Sensitive Personal Information: Special categories under POPIA (political persuasion, trade union status).
- Financial Information: Credit records, transaction history, bank accounts.
- Employee Information: Disciplinary records, payroll details, performance reviews.
- Customer Information: Operational profiles, transaction records, activity logs.
- Health Information: Medical histories, clinical records, test results.
- Identity Information: National ID numbers, passport numbers, unique codes.
- Confidential Business Information: IP, source code, strategy, proprietary algorithm weights.
- Public Information: Data deliberately made public by the subject, excluded from certain restrictions.
Pillar C: Data Lineage
Data lineage establishes an auditable historical trail of information movements. For every critical data asset, the platform must document:
- Origin: Where did this personal information originate?
- Transit: Where has it travelled across internal systems?
- Processing: Which systems have processed or transformed it?
- AI Association: Which AI models have ingested or been trained on it?
- Access: Which people and processes have accessed or modified it?
3. Data Lifecycle Compliance Metrics
Insight Keepers enables risk officers and CISOs to monitor data compliance through four live dashboard indicators:
A. Classification Coverage (DCC)
Measures the proportion of known corporate data assets that have been successfully mapped and categorized within the data classification registry:
DCC = (Data Assets Classified) / (Known Data Assets) × 100
B. Lineage Coverage (LC)
Tracks the percentage of critical data assets (those containing personal or sensitive information) that have a fully documented, auditable data lineage map:
LC = (Critical Data Assets With Documented Lineage) / (Critical Data Assets) × 100
C. Retention Compliance (RC)
Monitors whether stored personal information is being held lawfully. It calculates the proportion of active records that remain within their approved statutory or contractual retention window:
RC = (Assets Within Approved Retention Period) / (Applicable Assets) × 100
D. Unauthorised Data Exposure (UDE)
A raw volume metric that tracks the count of identified data exposure incidents, leakage events, or unauthorized access attempts within a reporting window:
UDE = Number of Identified Unauthorised Exposure Events
4. Legal Grounding: Minimal Processing and Destruction
Under Condition 3 (Purpose Specification, Section 13) and Condition 7 (Security Safeguards, Section 19), organisations must enforce end-of-lifecycle protocols:
- Section 10 Minimality: Data collected must be adequate, relevant, and not excessive. Discovery tools must verify that databases do not accumulate "dead" or excessive data.
- Section 14 Retention & Destruction: Records must be destroyed or permanently de-identified as soon as their purpose is met. De-identification must be irreversible, ensuring no bad actor can manipulate or link the dataset to re-identify individuals. If data is processed in the cloud or by third-party operators, contracts must enforce secure deletion of all cloud-hosted backups.
