Installation guide

Install Companion - macOS

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 - macOS Check SHA-256 checksums Registration helper checksums

Installation - Companion - macOS

Download and verify

Also download checksums.sha256. Compare the file SHA-256 with the line bearing its exact name before installing.

SHA-256 checksums

Connect the browser

Install the PrivCloud browser extension. Keep its exact ID from chrome://extensions or edge://extensions.

Install the extension

Extract the archive

Keep the files in a permanent folder and configure the launcher from that folder.

chmod +x ./privcloud-companion
./privcloud-companion --configure-runtime "$(command -v node)"

Download the registration helper

The portable archive does not contain this helper. Download it into the same folder. Its checksum is available in the helper checksum list.

macOS helper

Connect Chrome or Edge

Run without sudo. Replace the IDs with those of your extensions. Safari does not support this extension.

PRIVCLOUD_COMPANION_PATH="$PWD/privcloud-companion" PRIVCLOUD_CHROME_EXTENSION_ID=CHROME_ID PRIVCLOUD_EDGE_EXTENSION_ID=EDGE_ID sh ./install-native-messaging-macos-0.1.4.sh

Check that it works

Return to Integrations, select Refresh and check that the extension and Companion are detected. Sign in and try importing a small WebDAV file using a revocable app password.

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

All integrations