HOLK Secure
Concept
Secure mobile communication
A handset architecture in which message contents are protected on the device, and the network only carries ciphertext.
Project overview
A handset architecture in which message contents are protected on the device, and the network only carries ciphertext.
What problem are we solving?
Most messaging convenience depends on a service that can see more than the user intends: contacts, metadata, backups and sometimes the messages themselves. A privacy-first device has to make those choices visible.
How does the technology work?
The concept splits the path into five stages. Phone A prepares the message. Encryption happens on that device. The network transports the protected payload. Phone B decrypts it. Anything the network can read is limited to what is required to deliver the packet. Local storage is protected separately, and a retirement step can erase keys and local copies.
System architecture
- Phone A prepares the message on the device.
- Encryption uses keys that are not published and are not stored in the website.
- The network forwards ciphertext.
- Phone B decrypts and shows the message.
- A data-erasure step is part of the design for loss or retirement.
Development phase
The work is a concept. There is no HOLK TECH handset, no published protocol and no security certification.
Current challenges
- Designing protection that a non-specialist can understand without hiding the limits.
- Keeping identity keys on the device.
- Defining erasure so it is deliberate, not a marketing phrase.
Next milestones
- Keep the public explanation aligned with the concept, and do not describe it as a product.
- Only move the status to Prototype when a device exists and can be shown as such.