Hello,
Why should we feel safe since you are closed source and you could be leaking credentials and private cloud files ?
Honest question, love the tool but i don’t feel safe
@rcloneview ? Against, not trying to be dismissive, its an honest question as i like the product
@rcloneview one week no answer.. not very reassuring to say the least
We understand the concern about RcloneView being closed source.
Our company has been developing and selling storage-related software such as NetDrive and CloudSync since 2010. At our peak, our products were used by over one million users, and during more than a decade of operation, we have never had a single incident of user data leakage or security breach.
RcloneView is built with the same security-first principles. We do not collect or access user data, and protecting user privacy has always been a core design policy for all of our products.
If you have specific questions about security or data handling, we’re happy to clarify as much as possible.
Best regards.
I just want to know how i can ever feel safe transmitting config password, cloud api info, to a black box ? Potentially all my files.
Compared to less good but open source alternatives ?
It feels like a ticking bomb, and i dont understand why closed source is chosen here and not open ? What does it add for you ?
RcloneView itself is only a GUI layer. All actual operations—authentication, encryption, data transfer, and file handling—are performed entirely by the rclone binary, exactly the same rclone you would run from the command line. RcloneView does not modify rclone’s behavior or intercept file data.
Credentials and config data are stored locally using the OS’s secure storage mechanisms (such as Keychain on macOS or equivalent on other platforms). We do not transmit your credentials or file data to any external servers, nor do we have visibility into your cloud contents.
The decision to remain closed source is mainly about product maintenance, UX consistency, and long-term sustainability, not about data access. It does not grant us any additional technical access to user data.
That said, if full source transparency is a hard requirement for you, using rclone directly or an open-source GUI is completely understandable. RcloneView is intended for users who want a more polished and managed UI without changing rclone’s trust model.
I hope this clarifies the design choice and the actual risk surface.
Best regards.