QUICK ANSWERS
Questions before you connect
The short version: no account, temporary browser state, encrypted application content, Direct-first transport and explicit capability limits on fallback paths.
Read the boundaries, not just the headline
Orylin is designed to reduce durable account and cloud-content surfaces, but it still relies on browsers, network providers and limited coordination infrastructure.
The answers below describe the current production boundary. They do not replace the Privacy, Security, Data Practices or Acceptable Use documents.
Questions and answers
Do I need an account?
No. The current temporary-session flow does not publish an account-registration requirement or cloud inbox.
Can Orylin read my messages or files?
Application messages and file chunks are encrypted in the browsers. The current Orylin service does not expose an endpoint that accepts them as plaintext, though request and network metadata still exist.
Is Orylin anonymous?
No anonymity claim is made. Direct peers, network providers and external public relays can observe metadata needed to carry traffic.
What happens if Direct connection fails?
A user-enabled volunteer browser relay may forward bounded ciphertext. Public Nostr rescue can carry encrypted messages only. Capability changes are shown in the interface.
Can I send large files?
Direct transfers can stream to a user-selected destination in compatible Chromium browsers; otherwise they are constrained by a browser-memory budget. The volunteer relay limit is 2 MiB.
Is voice relayed?
No. Voice is Direct-only and pauses when the active path is not Direct.
Where are keys and session state stored?
Active keys and session state stay in volatile browser memory. The current app stores locale and theme preferences in localStorage.
Has Orylin been independently audited?
No independent-audit claim is made. Published protocol and policy material should not be treated as a certification.