A protected request title
The browser opens the encrypted title with the key from the private fragment. The public metadata response does not reveal the owner account.
Encrypted file requests without opening your workspace.
Give a client, customer, or collaborator a focused browser link for sending files back to you. RonikCloud protects the request title on the owner's device, then protects each submitted filename, content type, and file body on the contributor's device before the upload reaches storage.
Founding beta: RonikCloud has not been independently audited. Use non-critical copies and keep another backup.
Focused handoffA browser upload page, not workspace access
Local encryptionProtection begins on the contributor's device
Private link keyCarried in a URL fragment browsers do not send
Bounded collectionExpiry, size, upload limit, and closing controls
From your request to a protected incoming file.
Use one purpose-built request instead of sharing a folder, collecting an ordinary attachment, or granting broader access than the contributor needs.
Create the request
Choose a private request title, expiry, maximum file size, and completed-upload limit for the collection task.
Send the complete link
Share the secret-bearing link through a trusted channel. The private URL fragment carries the key needed by the browser.
Encrypt in the browser
The contributor selects a file. Its name, content type, and body are protected on that device before upload.
Review and close
Receive the protected submission in your owner workflow, then close the request when collection is finished.
Collect the source material without inviting someone inside.
A file request fits the moment when another person needs to send something sensitive, but does not need your folder tree, workspace history, or member permissions.
- Professional documentsRequest signed agreements, project briefs, reports, or other source documents through one focused handoff.
- Creative source filesCollect photographs, design assets, audio, or exported project files without turning the sender into a workspace member.
- Bookkeeping inputsAsk for invoices, receipts, or supporting records with a request that has a clear expiry and upload limit.
- Follow-up materialsOpen a separate bounded request when a client needs to supply another revision or missing input.
A small upload page with explicit limits.
The public page is intentionally narrower than the owner's workspace. It uses a limited metadata endpoint and does not read the private request document directly.
Visible collection boundaries
The page shows the maximum file size, remaining submission slots, and an approximate availability time derived from the coarse request expiry.
Fixed recovery guidance
Invalid keys, closed requests, upload limits, and interrupted transfers use bounded guidance. Provider response bodies are not displayed to the contributor.
The private fragment protects content, not every trace of activity.
Encryption narrows what storage and the public page receive in readable form. It does not make the account relationship, request limits, network connection, or service operation disappear.
RonikCloud still processes the owner relationship, opaque request, upload, and object identifiers, coarse expiry, file-size and upload limits, counts, status, encrypted payload sizes, storage routing, and limited security records. Service infrastructure can observe connection data, timing, and traffic volume.
Founding beta: This page describes the current implementation. Start with a non-critical workflow, keep an independent backup of irreplaceable files, verify the recipient channel, and close a request when the collection is complete.
Follow the file before and after collection.
Explore RonikCloud's existing guides for storage, sharing, backup, client delivery, and small-workspace collaboration.
Secure cloud storage
Understand on-device protection, user-held recovery, private device state, and the metadata the service still needs.
Encrypted file sharing
Pair incoming file requests with password-protected encrypted share copies, expiry, request budgets, and revocation.
RonikCloud for freelancers
Connect client collection and protected delivery with practical comments and review status.
RonikCloud for small teams
Use roles and deliberate invitations for colleagues while keeping external contributors outside the workspace.
Private cloud backup
Learn where protected file copies fit alongside recovery kits, version history, and independent backups.
Secure client file portal
See the broader client workflow for encrypted collection, protected delivery, comments, and review decisions.
Encrypted file request FAQ
Does a contributor need access to my RonikCloud workspace?
No workspace access is needed. The contributor opens a focused public file-request page with the complete private link, chooses a file, and submits it from the browser. Anyone holding that complete link can use the request while it remains active, so send it through a trusted channel.
What does an encrypted file request protect?
The owner encrypts the request title before creating the link. The contributor's browser encrypts the submitted filename, content type, and file body before upload. The private encryption key is carried in the URL fragment, which browsers do not send with the HTTP request, and in a separate owner-encrypted envelope.
How can I limit or close a file request?
A request has an expiry, a maximum file size, and a completed-upload limit. The owner can close it earlier. A temporarily reserved upload slot is released automatically after an abandoned attempt, so that temporary state is different from reaching the completed-upload limit.
Does encryption hide every detail about a requested upload?
No. RonikCloud still processes the owner relationship, opaque request, upload, and object identifiers, expiry, file-size and upload limits, counts, status, encrypted payload sizes, storage routing, and limited security records. Service infrastructure can also observe connection data, timing, and traffic volume.
Collect the file without opening the whole workspace.
Join the tester program with a real client-shaped collection 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.