PRIVACY AND STORAGE
What Orylin keeps out of the system
No account, no cloud history: session keys stay in the browser and application records are encrypted.
Keep identity and history out
The current service does not ask for a profile, contact list or password. Temporary sessions reduce the need for durable identifiers and cloud-held conversation state.
Closing or reloading a participating browser ends the browser-memory state unless the current session flow explicitly reconnects. Orylin does not advertise recovery of deleted browser state.
Encrypt application content
Messages and files are protected as application records before they cross Orylin coordination infrastructure or a volunteer relay. Session keys are not supplied to those relays.
Files are verified progressively with SHA-256. That integrity check detects transfer corruption; it is not a claim that a file is safe or trustworthy.
Network metadata still exists
Encryption does not remove the network metadata required to establish and carry a connection. Direct peers can learn the network addresses required by WebRTC, and infrastructure providers can observe ordinary request and transport metadata.
External public relays used by the rescue path may observe or retain encrypted event metadata. Orylin therefore avoids claiming anonymity or resistance to traffic analysis.