In order to access Basecamp, we need to have your Basecamp account URL, username and password. Learn more.
We need your Basecamp username and password instead Basecamp API token because of the following:
Basecamp API does not support export and import of all types of Basecamp project data
Our patent pending real-time cloud replication technology needs to access information which is not accessible via Basecamp API
This dialog is for Basecamp Classic. Click here to cancel and configure Basecamp Next.
We will store your username and password using 256-bit AES encryption on our secure server. Learn more.
The following best practices are followed to ensure your password is securely stored and data remains secured and private:
Baseacamp credentials are securely stored on cloudHQ secure storage and encrypted with 256-bit AES encryption.
All 256-bit AES keys for encryption and decryption of Basecamp password are encrypted and stored in a special "wallet".
This wallet is encrypted using a password which is not stored on any of our servers. The password to open this wallet is known only to the
cloudHQ administrator who manages our production server.
cloudHQ does not permanently store your files.
When cloudHQ access your data via API, it might temporary cache part of the content, but cloudHQ never stores
any of your files permanently on its servers.
Communication between cloudHQ servers and Google Docs, SugarSync, Basecamp, and Dropbox is always done over a secure TLS v1.3 channel.
Communication between cloudHQ servers and your browser is always done over a secure TLS v1.3 channel.
Our product software and infrastructure is updated regularly with the latest security patches. Our network is protected by
an enterprise-class firewall.
Two-way sync of data between two cloud accounts means that changes (updates, renames, uploads, deletes) from the service will be automatically copied to other services and vice-versa: when you modify something on the second service the changes will
be automatically replicated to the first service.
One-way sync means only changes you make on the first service will be replicated to the second service. However, changes on the second service will not be replicated to the first service. One-way sync with option Archive files before they are changed or deleted by sync is basically a sync for backup.
