1. Scope and current status
This policy covers the Orylin website, Cloudflare Worker rendezvous service and voluntary peer relay. The current service provides temporary browser communication without accounts or cloud session history; messages, files and Direct voice use end-to-end encryption.
Orylin aims to minimize data; it does not promise absolute anonymity. During a Direct WebRTC connection, the peer and relevant network infrastructure may receive network metadata needed to establish that connection.
2. Data Orylin processes
When an invitation is created, the browser generates a high-entropy secret. The secret is placed in a URL fragment, which ordinary HTTP requests do not send. After reading it, the page removes it from the address bar and uses it only in volatile browser memory.
- Basic request data: Cloudflare may process IP address, request time and path, User-Agent, errors and security events for delivery, security and abuse prevention.
- Temporary coordination data: public room binding, role, short-lived encrypted connection signaling and resource counters may be processed briefly in Worker or Durable Object memory. Orylin servers expose no application-data endpoint for messages, file chunks or voice frames.
- Connectivity metadata: WebRTC setup may expose candidate network addresses, candidate types and connection quality to the peer; network operators may also observe that communication occurred.
- Voluntary relay data: after a user opts in, the browser forwards only bounded single-hop end-to-end ciphertext and minimal circuit state; the volunteer relay receives no session keys or application plaintext.
- QR scanning: camera permission is requested only after the user explicitly opens the scanner. Video frames are processed locally in the browser to recognize the QR code and are not uploaded or persistently stored by Orylin.
- Session interaction data: message times, typing state, delivery/read receipts and unread counts are processed only in the peers' current browser memory; message, file and Direct voice content is protected with end-to-end encryption. Orylin does not create searchable message or receipt history.
- Voice and devices: microphone permission is requested only after the user explicitly starts voice. After permission, the browser may expose input-device names for local selection. Names and input levels are not written to Orylin servers, and voice pauses automatically on a relay path.
- Not currently processed: account profiles, contacts, advertising identifiers, payments, cloud message history, cloud files, cloud recordings or marketing profiles.
3. Purposes and principles
Data is used only to serve the static site, establish a temporary connection, verify Direct or relay paths, enforce resource limits, diagnose faults and protect the service. Orylin does not sell personal information, share it for cross-site advertising or use session content for model training.
Where applicable law requires a legal basis, processing may rely on delivering a user-requested service, legitimate interests in protecting the service and its users, legal obligations, or consent obtained before new optional processing.
4. Storage and retention
The current Orylin application sets no first-party cookies and writes no sessionStorage or IndexedDB. It stores only the non-sensitive interface-language and color-theme preference keys orylin.locale and orylin.theme in localStorage after you choose them. Invitation secrets, session keys, messages and current connection state remain in volatile memory; a refresh never restores session content.
Orylin does not use R2, D1, KV or Durable Object persistent storage for messages, files, voice, session keys or session history. Cloudflare may retain limited logs under its own security, operations and legal policies; that retention is controlled by Cloudflare policy and account configuration.
5. Recipients and international processing
Cloudflare supplies DNS, TLS, static delivery, Workers, Durable Objects and STUN, and may therefore process limited network data as an independent controller or service provider. The communications peer receives network metadata needed for connectivity. Orylin does not disclose data to other parties except where required by law or needed to protect users and maintain the service.
Cloudflare's global network may process network data outside a user's region under Cloudflare's published privacy, contractual and transfer terms.
6. Individual rights and requests
Depending on location, a person may have rights to know, access, correct, delete, restrict or object to processing, withdraw consent, obtain portability, and avoid discrimination for exercising rights. Because Orylin has no account or persistent user database, the project usually cannot re-identify a person from a temporary connection alone; a requester would need to provide enough non-secret information to locate any relevant record.
Privacy, accessibility and general support requests may be sent to support@orylin.link.
Do not include invitation secrets, keys, SDP, ICE, IP addresses, identity documents or session content in a rights request or any public post.
Where local law provides it, a person may also complain to a competent data-protection or consumer authority.
7. Children and policy changes
Orylin is not directed to anyone under 18 or below the local age of majority, whichever is higher. It has no child-directed features and does not actively collect age. Any future audience change or known processing of children's data requires appropriate guardian notice, consent, access and deletion processes first.
This policy will update its version and effective date when features, infrastructure or legal requirements change. Material changes will be presented on this page before they take effect where required.