Private request details
The request title, submitted filename, content type, and file body are protected on the contributor's device.
Encrypted file sharing with control over the handoff.
Create a separate encrypted share copy, protect it with a password, limit how long it stays available, and revoke it when the work is done. After the password proof is accepted, the recipient's browser downloads and decrypts the protected copy.
Founding beta: RonikCloud has not been independently audited. Use non-critical copies and keep another backup.
Separate share copyYour workspace original stays separate
Password boundaryProtects content and private metadata
Link controlsExpiry, request budget, and revocation
Honest revocationDownloaded copies cannot be recalled
From private workspace to intended recipient.
A public link is a capability. RonikCloud gives you concrete ways to narrow that capability before you send it.
Create a protected copy
RonikCloud creates an encrypted derivative for sharing instead of exposing the workspace object directly.
Choose boundaries
Set a password, expiry, and request budget appropriate for the recipient and sensitivity.
Send secrets separately
Send the complete link and password through different trusted channels when possible.
Close access
Watch the request count and revoke a link when the transfer is complete or no longer expected.
The URL alone is not enough to fetch encrypted bytes.
New share links keep the filename and content type inside the same password boundary as the file. The browser derives a proof from the password, and the backend verifies it before releasing the encrypted payload.
- Source checks on every requestThe share is available only while its source remains active and the owner still has the required access.
- Finite request budgetNew links default to ten encrypted-payload requests, with an owner-selected limit from 1 to 1,000.
- Coarse expiryNew expiry boundaries are rounded to the next UTC hour rather than storing an exact public-link lifecycle time.
- Emergency closureRevoke every active link across Personal and Business files from file management or the Data Safety Center.
Collect client files without asking them to join your workspace.
A contributor opens the request, selects a file, and encrypts it in the browser. The private URL fragment carries the encryption key and is not included in the HTTP request sent by the browser.
Bounded submissions
Set an expiry and completed-upload limit. Temporary reservations are released if an upload is abandoned.
Owner-controlled closure
Close the request after collection. Anyone with the complete URL can use it until expiry, revocation, or its limit.
A revoked link cannot pull back a downloaded copy.
Encryption and link controls narrow access before and during a transfer. They cannot control a file after an authorized recipient has decrypted and saved it elsewhere.
Treat the full share link, file-request link, and password as sensitive. Confirm the recipient, use separate channels for the link and password when practical, and revoke access that is no longer needed.
Support safety: Never send support a complete secret-bearing link, password, recovery material, private key, or authentication code.
For recurring two-way client handoffs, compare the workflow in the encrypted WeTransfer alternative guide.
Encrypted file sharing FAQ
How does a password-protected RonikCloud share work?
RonikCloud creates a separate encrypted share copy. The recipient's browser derives a proof from the password, the backend checks it before encrypted bytes leave storage, and the browser decrypts the protected file.
Can a share link be limited or revoked?
Yes. New links have an expiry and encrypted-payload request budget, and the owner can revoke a link. Revocation cannot recall a copy that a recipient already downloaded.
What does a recipient need to decrypt a shared file?
The recipient needs the complete share link and its password. After the backend accepts the password proof, the browser downloads and decrypts the protected share copy.
Give every file handoff a clear beginning and end.
Join the tester program and exercise a protected delivery workflow, or review the product and current pricing first.
Founding beta: RonikCloud has not been independently audited. Use non-critical copies and keep another backup.