User Data Deidentification System for Privacy Compliance

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Service providers face challenges in extracting meaningful insights from user data while complying with privacy and security standards that restrict the use and retention of personal identifiable information (PII), making it difficult to retain data for future use without violating regulatory standards.

Innovation Solution

A data deidentification system that processes user data to remove or obscure PII, allowing for the retention of deidentified data and associated insights, which can be used across different geographic locations, while adhering to privacy standards such as GDPR and CCPA, by employing a data pre-processing module, insight extraction module, selective hashing module, and data management module.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If service providers retain and use user data for extracting insights and delivering targeted content, then productivity and business value are improved, but compliance with privacy standards becomes difficult to maintain

Engineering Contradiction:
Improveability to extract insights from user dataVSAvoidcompliance with privacy standards
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system segments user data into two distinct components: identifiable data (retained for compliance periods and used for targeted advertising) and deidentified data (retained indefinitely for analytics and insights). This segmentation allows the service provider to simultaneously satisfy privacy requirements by limiting use of identifiable data while maintaining analytical capabilities through deidentified data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts identifying information from user data to create deidentified datasets. By removing personally identifiable information while preserving the underlying patterns and insights, the system enables continued data utilization for analytics purposes without violating privacy standards that prohibit retention of identifiable data beyond specified periods.

Inventive Principle:
Principle #2Taking out (Extraction)

2Reliability

If service providers obfuscate user data to comply with privacy standards, then compliance with privacy standards is improved, but ability to extract meaningful insights deteriorates

Engineering Contradiction:
Improvecompliance with privacy standardsVSAvoidloss of meaningful insights
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system segments data processing into two parallel tracks: one handling identifiable data with full obfuscation for compliance purposes, and another handling deidentified data with selective preservation of analytical value. This allows the system to maintain compliance while preventing information loss for analytics by working with the deidentified portion that retains useful patterns.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system applies different levels of obfuscation to different portions of data based on their intended use. Identifiable data receives complete obfuscation for compliance, while deidentified data maintains sufficient quality for analytical purposes. This local differentiation of data quality allows simultaneous achievement of compliance and analytical utility.

Inventive Principle:
Principle #3Local quality

3Reliability

If service providers are restricted from retaining user data beyond certain periods, then compliance with privacy standards is improved, but ability to retain data for future use deteriorates

Engineering Contradiction:
Improvecompliance with privacy standardsVSAvoiddata retention period
Core Design Contradiction:
ReliabilityVSDuration of action of stationary object

Solution Approach 1:

The system segments data retention into two timeframes: identifiable data is retained only for the compliance-mandated period (e.g., 24 months), while deidentified data is retained indefinitely. This segmentation resolves the contradiction by satisfying the temporal restriction on identifiable data while enabling long-term retention of deidentified data for future analytics and insights.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts identifying information from user data before long-term retention. By removing the identifying components that trigger retention restrictions, the system enables indefinite retention of the underlying data patterns and insights without violating privacy standards that limit retention of identifiable personal data.

Inventive Principle:
Principle #2Taking out (Extraction)

4Adaptability or versatility

If service providers export data across geographic locations, then adaptability and operational flexibility are improved, but compliance with jurisdictional restrictions deteriorates

Engineering Contradiction:
Improveability to export data across jurisdictionsVSAvoidcompliance with geographic restrictions
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system extracts identifying information from data before exporting it across geographic boundaries. By removing personally identifiable information, the system enables cross-jurisdictional data transfer that would otherwise violate privacy regulations, while still preserving the analytical value of the deidentified data for international operations and analytics.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20240403487A1User data deidentification system for email addresses
Publication Date: 2024.12.05 TELESIGN CORP
  • US20240403487A1 patent drawing
  • US20240403487A1 patent drawing
  • US20240403487A1 patent drawing

AI summary

A data deidentification system that extracts insights from user data and retains both the insights and user data in a form that complies with applicable data privacy and related standards. The system receives user data, which can include personal identifying information and other sensitive data governed by one or more standards, including standards specifying how the data can be used and how long it can be retained. From the data, the system extracts insights characterizing various aspects of the associated users. The system also selectively hashes portions of the data, obscuring the identity of associated users. Neither the insights nor the selectively hashed data identify individual users, and therefore they are not subject to the same standards and can be retained indefinitely. Later, after the standards-protected data has been discarded, the system can provide insight information in response to a request.