Install Companion - Windows
Import WebDAV files onto your device, encrypt them locally and upload them to PrivCloud.
Before downloading
Using Companion, WebDAV and the native app requires a Pro account or active Team membership.
- Node.js 20 or newer, available to the user account that runs the browser.
- Install the PrivCloud browser extension. Keep its exact ID from chrome://extensions or edge://extensions.
- This beta distribution requires manual installation. Windows/macOS archives are not signed or notarized.
Beta download
Manual installation. Packages are not yet distributed through stores. Verify the checksum before installing and keep your recovery data safe.
Download Companion - WindowsCheck SHA-256 checksumsRegistration helper checksumsInstallation - Companion - Windows
Download and verify
Also download checksums.sha256. Compare the file SHA-256 with the line bearing its exact name before installing.
SHA-256 checksumsConnect the browser
Install the PrivCloud browser extension. Keep its exact ID from chrome://extensions or edge://extensions.
Install the extensionExtract the archive
Place the files in a permanent folder. Keep privcloud-companion.cmd and privcloud-companion.mjs together and check that node --version reports at least 20.
Download the registration helper
The portable archive does not contain this helper. Download it here and place it in the same folder. Its checksum is available in the helper checksum list.
Windows helperConnect Chrome or Edge
In this folder, open an administrator PowerShell to create the shared registration folder. The browser registration uses the current user profile. Replace the path and both IDs with your actual values.
powershell.exe -ExecutionPolicy Bypass -File .\register-native-messaging-0.1.4.ps1 -CompanionPath "C:\PrivCloud\privcloud-companion.cmd" -ChromeExtensionId "CHROME_ID" -EdgeExtensionId "EDGE_ID" -Scope CurrentUser
Need help?
If Companion is missing, check Node.js, the launcher path and the extension ID, then reload the extension and PrivCloud. After an NVM update, configure the Node.js path again. A Flatpak browser may need explicit access to the Companion folder.
Return to integrations and connection checks