Local Data Storage Governance for Secure, Fast Privacy Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for managing personally identifiable information (PII) in organizations face inefficiencies in access control and data management, particularly due to the complexity of managing access requests and storing approval records across multiple databases.

Innovation Solution

A privacy service computer program authenticates users, collects and cleans user activity data, stores it locally, and purges it after a specified time, using APIs for communication and ensuring secure, efficient data management through a privacy application and database system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If user activity data is stored centrally in a privacy database, then data security and centralized control are improved, but network dependency and access time increase

Engineering Contradiction:
Improvedata securityVSAvoidaccess time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments data storage between central and local locations. The privacy database stores master copies of user activity data centrally, while privacy applications on electronic devices store local copies. This segmentation allows fast local access while maintaining centralized security controls and audit capabilities.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements a nested storage structure where local storage on electronic devices contains user activity data that mirrors or references the central privacy database. The local storage is nested within the broader centralized system, enabling offline access while maintaining connection to central controls when available.

Inventive Principle:
Principle #7Nested doll (Nesting)

2Reliability

If user activity data is retained for audit purposes, then compliance and accountability are improved, but data storage requirements and security risks increase

Engineering Contradiction:
ImprovecomplianceVSAvoiddata storage requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts audit-capable data to local storage on electronic devices, separating it from the central privacy database. This extraction reduces the quantity of data that must be securely maintained centrally while preserving the ability to conduct audits locally, thereby reducing overall security risks and storage requirements at the central location.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent enables selective discarding of user activity data from central storage after it has been replicated to local storage and verified for audit purposes. Once local copies are confirmed, central storage can discard redundant data, reducing storage requirements while maintaining compliance through local retention.

Inventive Principle:
Principle #34Discarding and recovering

3Reliability

If multiple databases are used to store PII and approval records, then data access control is improved, but system complexity and management overhead increase

Engineering Contradiction:
Improveaccess controlVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent makes the privacy database and privacy applications multi-functional, serving both as operational data storage and as audit record repositories. This universal use reduces the need for separate specialized databases for different purposes, simplifying the overall system architecture while maintaining robust access control through the unified privacy service.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12353600B2Systems and methods for local data storage
Publication Date: 2025.07.08 JPMORGAN CHASE BANK NA
  • US12353600B2 patent drawing
  • US12353600B2 patent drawing

AI summary

A method for local data storage governance may include: authenticating, by a privacy service computer program, a user accessing the privacy service using a privacy application; receiving, by the privacy service computer program and from a proxy service, user activity data; saving, by the privacy service computer program, the user activity data to a privacy database; receiving, by the privacy service computer program and from the privacy application, a request for the user activity data; retrieving, by the privacy service computer program and from the privacy database, the user activity data; communicating, by the privacy service computer program, the user activity data to the privacy application, wherein the privacy application stores the user activity data in local storage; receiving, by the privacy service computer program, an acknowledgement of the user activity data; and purging, by the privacy service computer program, the user activity data from the privacy database.