Is Cryptomator phoning home?

I’m running Cryptomator 1.16.0 (appimage-5719) on Manjaro Linux. I have paid for a licence which I entered into the app upon install over a year ago.

I recently installed Portmaster firewall, and Portmaster is showing outgoing connections to api.cryptomator.org IP address 51.15.240.133 port 443.

I understood from searching this forum that all licence checking etc was carried out on the local machine, but even if it wasn’t, and a one time connection was required, that doesn’t explain the ongoing connections.

Could someone please explain why Cryptomator desktop is making this connection?

Hey and welcome to the Cryptomator Community :slightly_smiling_face:,

Cryptomator desktop has two cases where it connects to api.cryptomator.org

Update Check

If an user clicks on “Check for updates” or have the auto updater active, requests are made against api.cryptomator.org to check for updates, see cryptomator/src/main/java/org/cryptomator/updater/FallbackUpdateMechanism.java at develop · cryptomator/cryptomator · GitHub with cryptomator/src/main/java/org/cryptomator/updater/FallbackUpdateMechanism.java at develop · cryptomator/cryptomator · GitHub

Error reporting

If an user runs into an error, an “An error occured” dialog is shown (Error Handling | Cryptomator Documentation). If the user then clicks the “Lookup Solution” button, the error database is loaded from api.cryptomator.org to the device, see cryptomator/src/main/java/org/cryptomator/ui/error/ErrorController.java at develop · cryptomator/cryptomator · GitHub with cryptomator/src/main/java/org/cryptomator/ui/error/ErrorController.java at develop · cryptomator/cryptomator · GitHub .

2 Likes

Thank you very much for clarifying that :slight_smile: I had ticked “check for updates” and promptly forgotten!