Terms of Service

RelicBeam is a temporary file/text sharing service, an end-to-end-encrypted browser-based Device Portal for Remote View and Remote Files, plus local image and PDF tools. No account is required. These terms are intentionally plain: use the service responsibly, do not abuse it, and keep your own copy of anything important.

By using RelicBeam

You agree not to use RelicBeam to send, store, publish, or facilitate anything illegal, malicious, or harmful. That includes, without trying to list every possible case:

• malware, viruses, exploits, or material intended to damage or gain unauthorized access to a device or service;
• content that is illegal to possess or distribute where you or the recipient are located;
• stolen, leaked, or unauthorized personal or confidential data;
• harassment, threats, abuse, fraud, or material intended to harm another person;
• spam, automated enumeration of Room/Quick Beam/Device Portal codes or temporary Beam links, attempts to bypass limits, or deliberate overloading/scraping of the service.

You are solely responsible for the content you choose to upload, send, or make available through RelicBeam, for having the right to share it, and for complying with applicable law. RelicBeam does not endorse user-submitted content and does not exercise editorial control over files or text transmitted through the service.

Temporary sharing, not storage

RelicBeam Rooms, Quick Beams, and Beam Links are temporary delivery tools. They are not backup storage, a permanent cloud drive, or an archival service. Sessions expire automatically and their content is deleted. If a file or piece of text matters, keep your own copy. Once RelicBeam deletes session data, there is no recovery feature.

Encryption depends on the feature

Room files and standard Beam Link files are accessible to the server during processing because RelicBeam performs server-side malware scanning; clean standard files are encrypted at rest after the scan. Quick Beam always uses E2EE for file contents; Beam Link offers it as an option. On these encrypted paths, the browser encrypts the file contents before upload, RelicBeam temporarily stores ciphertext, and RelicBeam cannot malware-scan the plaintext contents. Quick Beam text/password messages and Device Portal traffic use end-to-end encryption between the connected browsers. Device Portal may use RelicBeam's TURN server to relay encrypted WebRTC packets, but the relay does not terminate the peer connection or store the Remote View screen/audio stream or Remote Files file contents as normal server files. The Privacy Policy describes each data path in more detail.

Malware scanning is not a guarantee

RelicBeam scans files that use its normal server-backed upload pipeline for known malware before making them available, and blocks files the scanner identifies as infected. No malware scanner catches everything. A successful scan does not mean a file is guaranteed safe. Private E2EE files in Quick Beam or Beam Link are intentionally not scanned because RelicBeam cannot decrypt their contents; Quick Beam uses this encrypted path automatically, while Beam Link offers it as an option. Remote Files uploads are also not server-scanned because they travel directly over the end-to-end-encrypted Device Portal connection. Only accept unscanned files from a source you trust.

Local Convert tools

RelicBeam's Convert tools process supported images and PDFs locally in the browser. Conversions can fail, behave differently across browsers, or produce results that are not identical to the original. Keep the original file before converting, merging, splitting, rotating, reordering, or exporting anything important.

Device Portal

Remote View is view-only browser screen sharing. The person sharing the screen must explicitly approve the session and choose what the browser is allowed to capture. When the browser provides audio from the selected display/tab, the sharer may turn that audio on or off after the secure connection is live; audio starts off by default and Remote View does not request microphone access. RelicBeam does not provide mouse or keyboard control in Remote View. Remote View prefers a direct WebRTC connection and may use RelicBeam's TURN relay when a direct path is unavailable.

Remote Files exposes only the folder explicitly selected by the host. It is read-only by default. On supported host browsers, the owner may enable additive uploads; RelicBeam exposes no remote delete, rename, move, or intentional overwrite controls. The owner may approve multiple viewer devices independently. Each approved device uses its own browser-to-browser WebRTC connection and may be revoked separately. The owner may also temporarily pre-authorize an approved device with Away Access for 1 hour, 8 hours, 24 hours, 3 days, or 7 days. Away Access works only while the host computer remains awake/online, the original RelicBeam tab stays open, and browser folder permission remains available. Browser/platform limitations may make Remote Files uploads, very large downloads, streaming, or Away Access unavailable or less capable.

Browser and device differences

Some features depend on the browser or operating system. Examples include PWA installation, Share → RelicBeam support, Remote Files writable-folder access, screen capture, clipboard/file handling, HEIC decoding, and how iOS/Safari opens or downloads PDFs and images. RelicBeam may work differently, or a particular optional feature may be unavailable, on some platforms.

Limits can change

RelicBeam applies file-size, item-count, session-lifetime, rate, disk-safety, and other operational limits so one person cannot exhaust the service for everyone else. Current limits are shown in the product or FAQ where relevant. We may adjust those limits as the service, infrastructure, or abuse patterns change.

No accounts, no identity verification

RelicBeam does not require sign-up and does not verify who is using it. We cannot confirm a user's identity, age, authority, or relationship to another participant. Treat codes and links as access to the session and share them only with the people you intend to invite.

Abuse, removal, and legal compliance

If RelicBeam becomes aware of content or activity that appears unlawful, abusive, infringing, dangerous, or otherwise violates these Terms, the operator may immediately disable access to or delete the relevant file, Beam Link, Room, Quick Beam, Device Portal session, or other temporary data without notice. RelicBeam may also remove content when reasonably necessary for security, abuse prevention, legal compliance, or operation of the service.

RelicBeam does not promise to preserve user content and has no obligation to keep a temporary share available for its originally selected lifetime. Users remain responsible for their content and use of the service.

Reporting abuse

If you believe RelicBeam is being used to distribute unlawful, infringing, or otherwise abusive material, email [email protected]. Include the relevant Beam Link, Room/Quick Beam code, or other information sufficient to identify the temporary share. We may investigate a credible report and disable or delete the identified material where appropriate.

Play nice with the service

Do not deliberately probe, bypass, overload, scrape, reverse-engineer access controls, enumerate active codes, or interfere with RelicBeam beyond normal use. Security research that could affect real users or data should be reported to [email protected] rather than tested destructively against production.

Availability and changes

RelicBeam is currently provided without a usage fee. Some features may become paid in the future; if that happens, pricing and any paid terms will be shown before you choose to use a paid feature. We may also change, suspend, or discontinue features as the project evolves.

No warranty

RelicBeam is provided “as is.” We work to keep it reliable and secure, but we cannot promise uninterrupted availability, perfect conversions, perfect malware detection, permanent operation, or that every browser/device will behave identically. To the fullest extent permitted by applicable law, the operator is not responsible for losses arising from use of, inability to use, or reliance on RelicBeam or material shared through it.

Changes to these terms

If these terms change, the date above will be updated. If you do not agree with a later version, stop using RelicBeam.

Questions or misuse reports

Email [email protected].

Thanks for being reasonable, and happy beaming.