Full User Privacy
Private Users - Private Containers
A Private Channel is set up by one of the participants, not the system owner, and managed by the users within the container. The owner does not have access to the users' private keys and can only view the content if participants directly grant them access.
This setup is ideal when privacy is the priority, but some oversight may occasionally be necessary. Any external access can be granted only by the participants who set up the container.
System Roles
The table below outlines system roles in this scenario:
| Application | Application Server | PrivMX Bridge | |
|---|---|---|---|
| Generating Users' Key Pair | |||
| Storing Users' Private Keys | |||
| Storing Users' Public Keys | |||
| Registering Users' Public Keys in Bridge | |||
| Creating and managing containers | |||
| Managing System Owner's Public Key | |||
| Storing always encrypted data |
Example Applications
- Research Teams: Researchers working on sensitive projects or developing new technologies may use this setup to restrict access only to authorized team members, thereby protecting their intellectual property.
- Investigative Journalism: Journalists working on sensitive material can securely communicate and store information within a container inaccessible to platform administrators, safeguarding journalistic sources and data privacy.