Personal Data Logs Using User-Controlled Blockchain Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Users lose control over their personal data as it is managed by service providers, making it difficult to determine the processing done on this data and complicating data portability and access to new services.

Innovation Solution

A method involving a user's terminal to encrypt personal data with a symmetric encryption key, organizing it in a blockchain-based graph structure using a pre-established data model, with cryptographic data like dynamic non-fungible tokens or digital wallet public keys to ensure immutability and portability, and execute contracts in a trusted environment to analyze this data without exposing it to parties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If service providers manage user personal data, then data processing can be performed, but user control over personal data is lost

Engineering Contradiction:
Improveuser controlVSAvoiddata management system
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent segments the data management system by separating control functions from storage functions. Users maintain cryptographic control keys locally on their devices, while data is stored distributed across a blockchain network. This segmentation allows users to retain control without managing the entire data infrastructure, resolving the contradiction between user control and system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces cryptographic intermediaries (digital signatures, hash functions, and blockchain consensus mechanisms) that mediate between user control requirements and system operations. These cryptographic primitives enable users to control data access through keys without directly managing the complex distributed storage and processing infrastructure, thus maintaining user control while reducing operational burden.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If personal data is stored in a blockchain, then immutability and user ownership are guaranteed, but data access complexity increases

Engineering Contradiction:
Improvedata immutabilityVSAvoiddata access system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the complexity of blockchain data access by separating the immutable storage layer from the access interface layer. Data is stored immutably on the blockchain, but access is facilitated through simplified cryptographic proofs and smart contract interfaces that hide the underlying blockchain complexity from users, allowing reliable storage without proportionally increasing access complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses cryptographic copying mechanisms where data hashes and verification proofs are stored on the blockchain while actual data may reside in decentralized storage systems. This allows verification of data integrity through copies/hashess without requiring direct access to the entire data structure, maintaining immutability while simplifying access patterns.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If cryptographic data is used to link user identity, then data portability is improved, but system complexity increases

Engineering Contradiction:
Improvedata portabilityVSAvoidcryptographic system
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universal cryptographic identifiers (such as decentralized identifiers and verifiable credentials) that serve multiple functions: authentication, data ownership proof, and portability across different services. These cryptographic primitives provide a single mechanism that handles various identity and access control requirements, improving data portability while avoiding the need for separate complex systems for each function.

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

4Reliability

If personal data is encrypted with user keys, then security is improved, but data processing capability decreases

Engineering Contradiction:
Improvedata securityVSAvoiddata processing
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies encryption selectively based on data sensitivity and access requirements rather than uniformly encrypting all data. Different cryptographic schemes are applied to different data types and access scenarios, allowing frequently accessed non-sensitive data to remain more accessible while maintaining strong security for sensitive information, thus balancing security and processing efficiency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent employs adaptive encryption parameters where encryption strength and methods are adjusted based on data classification, access frequency, and security requirements. This allows the system to optimize between security and processing speed by using stronger encryption only when necessary, rather than applying maximum security uniformly to all data operations.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP4512034B1Methods, terminal and server for managing personal data
Publication Date: 2025.07.23 PIGNELA CAPITAL SA
  • EP4512034B1 patent drawingFigure 1~2A
  • EP4512034B1 patent drawingFigure 2B
  • EP4512034B1 patent drawingFigure 3A~3B

AI summary

The invention relates to a method for creating a personal data log (DPA) for a user, the method being implemented by a terminal (TA) of the user. It comprises: - a step of obtaining a symmetric encryption key (KSA) associated with a profile of the user; - a step (E50) of collecting personal data (DPA) from the user; - while collecting said personal data: (i) a step (E52) of encrypting said personal data using the symmetric encryption key (KSA) of said user; and (ii) a step (E56) of recording, in a general database (BDC), blocks (Bi) comprising the encrypted data ([BiA]), the blocks (Bi) being organised in blockchains constituting a subgraph (SGA) of a general graph (GC) of which the topology is defined by a pre-established data model, a root block of the subgraph (SGA) being associated with a dynamic non-fungible token of said user.