The ITYLOS Manifesto
The right to digital oblivion, made operational.
On the Internet, almost everything is copied, indexed, archived, synced and resold.
ITYLOS defends a different logic: sensitive information should not outlive its use.
Why this project exists
The modern web was designed to retain, duplicate and monetize information. Messengers keep histories. Emails remain in multiple inboxes. Screenshots circulate. Backups multiply. Search engines index. Clouds replicate.
In this environment, using a traditional channel for confidential transmission often amounts to creating a lasting and uncontrollable trace:
- Sending a password by email
- Transmitting an API key in Slack or Teams
- Sharing temporary admin access on WhatsApp
- Sending a sensitive document via internal messaging
ITYLOS starts from a simple principle : a useful secret is not an archive document. It is a transitional message. A capsule. A passage. It must be readable once, then permanently removed from active storage.
ITYLOS was designed to forget properly
Our thesis
The total memory of the web is a major security risk.
Declarative trust is not enough: technical cryptographic proofs are required.
Serious confidentiality starts with radical trace minimization.
A secret should be designed to circulate briefly, not to stagnate on a server.
What ITYLOS is / and is not
ITYLOS is
- an ephemeral transmission vector
- a sensitive secret sharing tool
- an architecture where encryption runs locally
- a system designed to reduce unnecessary persistence
- a service that produces cryptographic proofs of events
ITYLOS is not
- a long-term storage cloud
- a password manager
- a complete secure messaging platform
- a document collaboration tool
- a magic promise against all human vulnerabilities
ITYLOS is transport. Not archival.
A digital envelope. Not a permanent vault.
ITYLOS capsule lifecycle
Local creation
Content is prepared on the user's device. AES-256-GCM encryption is performed directly in the browser before any transmission.
Encrypted envelope
Our infrastructure only receives an opaque encrypted payload. We never have access to the plaintext secret.
Secure sharing
The sender transmits a self-contained ephemeral link, optionally protected by an additional password.
Single read
The recipient opens the capsule. Decryption is performed locally on their device.
Server-side destruction
At the exact moment of opening, or upon expiration, the capsule is physically purged from our active storage (Destruction after reading).
Independent verification
A cryptographic proof of destruction is generated, signed and can be audited locally offline.
When to use ITYLOS?
Confidential transmission via an ephemeral link is the ideal tool for:
- Securely sharing a password with a colleague.
- Transmit an API key or access token without leaving a network trace.
- Sending a one-time secret to a client.
- Sharing a temporary confidential file.
- Transmitting temporary admin access (Database, Server).
ITYLOS is useful when the question is not just “who can read this?”, but also: “how long should this information continue to exist?”
Founding principles
Radical minimization
A secret should not outlive its purpose. Less copying, less retention, less attack surface.
Zero-Knowledge
The server carries an encrypted envelope, not the information. We mathematically cannot read your data.
Ephemeral by design
Self-destruction is not cosmetic. Disappearance is built into the base protocol, not just the visual interface.
Verifiability
When a critical action is announced (destruction), it must be mathematically auditable by third parties.
Why destruction matters as much as encryption
Encryption protects access. Destruction reduces persistence.
These two dimensions address complementary problems: encryption limits who can read; destruction limits how long the risk can survive.
An encrypted capsule kept indefinitely on a server remains an exposed asset over time to technological advances (e.g., quantum computing). A capsule destroyed after use mechanically and permanently reduces the attack window.
Our promises, and their limits
We promise
- Rigorous local encryption before transmission
- A single-read and ephemeral logic
- A drastic reduction of persistent server traces
- Independent verification and audit mechanisms
- An architecture designed end-to-end for minimization
We do not promise
- Preventing a screenshot on the recipient's side
- Preventing a malicious recipient from copying the secret
- Erasing peripheral traces from an infected user workstation
- Replacing basic user security hygiene
- Turning a flawed business process into a secure one
Security should not be a belief
We believe that a promise of destruction, confidentiality or integrity must be accompanied by verifiable elements. The mechanisms used rely on industry-proven cryptographic standards such as AES-256-GCM and Ed25519.
That is why ITYLOS provides a complete audit ecosystem:
- Public transparency registry (Append-only log)
- Downloadable signed proofs for each destruction
- Independent local verification laboratory
- Strict separation between secret content and proof elements
- Operational readability for any external audit
Frequently Asked Questions
What is ITYLOS, in one sentence?
Is ITYLOS a password manager?
Does ITYLOS replace Signal or Proton Mail?
Is encryption alone enough?
Can total disappearance really be guaranteed?
Can ITYLOS proofs be verified independently?
Is the right to be forgotten absolute in a legal sense?
Take back control of your secrets
Create an ephemeral capsule, test single-read access, verify the cryptographic proof, and observe what happens to a sensitive share when it is designed to disappear.