Text, files, media, and groups
The whitepaper describes end-to-end encryption for supported conversation content.
In development
XecureCom
Private messaging with documented boundaries.
XecureCom is a Greenlyz messaging product in development. Its current public whitepaper describes end-to-end encryption, passwordless access, and a content-blind relay architecture.
Features and security properties may change before release.
Product overview
CONTENT
ACCESS
IDENTITY
REGISTRATION
A messaging design that makes trust assumptions visible.
The current XecureCom materials describe a server that forwards encrypted data while user devices create, hold, and use the private encryption keys.
Development status: XecureCom does not have a public release path on this site. The information below describes Greenlyz’s published design, not independently audited production behavior.
Passkey-first authentication
The design specifies FIDO2 and WebAuthn passkeys instead of reusable account passwords.
Safety-number verification
Users are intended to compare safety numbers when verifying an encrypted relationship.
No phone number planned
The published design does not require a phone number as the primary account identifier.
Encryption design
Encrypted on the device. Relayed as ciphertext.
The current whitepaper specifies X3DH for session establishment and the Double Ratchet for message-key evolution.
The design aims to limit exposure of earlier messages and support recovery after a key compromise, subject to the protocol state and a fresh ratchet step.
XecureCom / Published architectureWhitepaper v12.3 · First-party document
Sender deviceCreates and encrypts content
Blind relayStores or forwards opaque data
Recipient deviceDecrypts received content
Design says the relay cannot access
- Message plaintext
- Contact relationships
- Private keys
- File names and types
- SOS coordinates
- Safety numbers
Design says the relay handles
- Encrypted ciphertext
- Public keys
- User and display information
- Approximate message size
- Delivery timestamps
- Account creation date
Identity verification
SAFETY NUMBERS
KEY CHANGE
Make key changes visible.
The published design includes safety-number verification and identity-key change warnings. These controls are intended to help users detect unexpected changes and verify a secure relationship through a separate trusted channel.
Out-of-band comparison
Users can compare a fingerprint through another trusted channel before treating a conversation as verified.
Visible identity changes
A changed identity key should be surfaced rather than silently accepted by the client.
Planned capabilities
Useful features, scoped as design goals.
These capabilities appear in the current Greenlyz-authored materials. Their final behavior and release timing have not been announced.
Encrypted contact storage
The design describes contact information encrypted on the client before server storage.
Emergency alert workflow
The published concept includes optional GPS and battery information sent to user-selected trusted contacts.
User-controlled key backup
The whitepaper describes portable key material intended to remain under the user’s control.
Desktop and mobile direction
The planned product is described for both desktop and mobile use; supported platforms are not yet final.
Documented boundaries
OUT OF SCOPE
OUT OF SCOPE
OUT OF SCOPE
VISIBLE TO RELAY
Transport security cannot make a compromised device safe.
Compromised endpoints
Malware or unauthorized access to an unlocked device can expose content after decryption.
Physical access
Device locks, operating-system security, backups, and local handling remain important.
Global traffic analysis
The design does not claim to conceal every communication pattern from a global observer.
Limited routing metadata
The design acknowledges account information, public keys, approximate sizes, and delivery timing.
No compliance claim is made. Greenlyz does not currently present XecureCom as independently audited, certified, HIPAA compliant, or sufficient by itself for a regulated workflow.
Follow development
Evaluate the design. Ask hard questions.
Read the public whitepaper for the current architecture, or contact Greenlyz with a product or security question.