Temporal Data Containers for Cross-Border Meeting Privacy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web conferencing technologies fail to adequately protect sensitive data during transmission by ensuring compliance with country-specific data privacy laws, potentially leading to unauthorized data crossing borders and violating regulations.
Innovation Solution
Implementing temporal containers that segregate data sharing based on participant location and access levels, ensuring data remains within the user's or entity's control, and automatically deleting the data after the meeting to comply with privacy regulations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If data is shared freely during web conferencing to enable collaboration, then ease of operation and collaboration efficiency are improved, but data privacy compliance and security are worsened due to unauthorized cross-border transmission
Solution Approach 1:
The system segments the conferencing environment into multiple isolated container instances, each assigned to a specific geographic location. Data shared within a container remains confined to that location's jurisdictional boundaries, preventing unauthorized cross-border transmission while maintaining ease of collaboration within each segment.
Solution Approach 2:
The system implements location-specific data handling rules where each container instance enforces local data privacy regulations. Data shared in a container is subject to the privacy laws of its assigned jurisdiction, ensuring automatic compliance with local quality requirements without compromising collaboration efficiency.
2Loss of information
If data is retained after meetings for record-keeping and reference, then information availability is improved, but data security and privacy compliance are worsened due to prolonged exposure risks
Solution Approach 1:
Container instances are designed as temporary, disposable structures that are automatically deleted after their associated meeting concludes. This ensures data is available during the meeting for reference purposes but is automatically destroyed afterward, eliminating prolonged exposure risks while maintaining information availability when needed.
Solution Approach 2:
The system pre-configures automatic deletion policies for container instances before meetings begin. By establishing the temporary nature and automatic deletion timeline in advance, the system ensures data is retained only for the necessary duration without requiring manual intervention, balancing information availability with security.
3Reliability
If container instances are created for each participant to maximize data privacy protection, then data security is improved, but system complexity and resource consumption increase
Solution Approach 1:
The container instance serves multiple functions: it acts as a data isolation boundary, a compliance enforcement mechanism, a meeting workspace, and an automatic deletion target. This multi-functionality allows a single container structure to address multiple privacy and security requirements simultaneously, reducing the need for separate complex systems for each function.
Solution Approach 2:
The system merges geographic location identification, container instance creation, data isolation enforcement, and automatic deletion logic into a unified container management framework. By combining these functions into a single coordinated system rather than separate components, the overall system complexity is reduced while maintaining strong privacy protection.
4Reliability
If automatic deletion is implemented to ensure privacy compliance, then data security is improved, but loss of valuable meeting data and increased re-meeting requirements occur
Solution Approach 1:
The system segments meeting data into location-specific container instances that are automatically deleted after each meeting. This segmentation ensures privacy compliance for each location while allowing participants to access their local container data immediately after meetings if needed, minimizing data loss impact without requiring immediate re-meetings.
Solution Approach 2:
The container instance acts as an intermediary that temporarily holds meeting data during and immediately after the meeting concludes. This intermediary structure allows data to be retained briefly for any necessary follow-up actions while ensuring automatic deletion after a predetermined short period, balancing compliance requirements with practical data access needs.
Data Source
Figure 1
Figure 2
Figure 3A
AI summary
According to one embodiment, a method, computer system, and computer program product for temporal container generation is provided. The embodiment may include identifying a geolocation associated with a user device for each user within a web conference. The embodiment may also include generating a temporal container for each identified geolocation on one or more commonly controlled servers. The embodiment may further include assigning a temporal container corresponding to the geolocation associated with the user device to each user. The embodiment may also include, in response to a user within the web conference sharing a document, storing the document to each temporal container. The embodiment may further include granting each user permission to access the shared document in the temporal container to which each user is assigned.