These Plugin Terms supplement the ChromaChecker End-User License Agreement (the "EULA") and apply only if you install or use the Cloud Storage Plugin. Capitalised terms not defined here have the meaning given in the EULA. In the event of conflict, these Plugin Terms prevail for matters specific to this Plugin; the EULA governs everything else (EULA §2.4).
Acceptance. These Plugin Terms are accepted by an administrator of your Organisation, not by individual operators, because using this Plugin means connecting ChromaChecker software to accounts your Organisation holds with third-party providers.
1. What this Plugin does
Cloud Storage lets an operator browse, open and save files held in your Organisation's own cloud storage accounts — typically proof PDFs opened for softproofing — without leaving CC Capture. It adds a file browser and a transfer mechanism. It does not itself store your files.
2. The third-party services, and whose accounts they are
This Plugin connects to the following services. In every case the account and the registered application are yours, not ChromaChecker's:
| Provider | What you must supply | Governed by |
|---|---|---|
| Dropbox | Your own Dropbox application key, plus sign-in to your Dropbox account | Dropbox Terms of Service |
| Google Drive | Your own Google Cloud project and its client_secrets.json, plus sign-in to your Google account | Google Terms of Service and the Google API Services User Data Policy |
| Amazon S3 | Your own AWS IAM access key, secret key, bucket and region | AWS Customer Agreement |
ChromaChecker is not a party to your agreement with any of these providers. ChromaChecker does not operate them, does not control their availability, security, pricing or data handling, and does not hold an application registration on your behalf. Where a provider requires verification, security review or a fee for the application you register, that obligation is yours.
You are responsible for holding the rights necessary to grant this Plugin access to the accounts you connect, and for the content you transfer through it.
3. What leaves your computer, and where it goes
- Files you choose. When an operator opens a file, this Plugin downloads it from your provider to this computer. When an operator saves a file to cloud storage, this Plugin uploads it to your provider. Transfers are between this computer and your provider only — no copy of a file transferred by this Plugin is sent to, or stored on, ChromaChecker servers.
- Folder and file listings are read from your provider to display the browser.
- Nothing else. This Plugin does not scan, index or transmit the rest of your storage.
Measurement data and other results that CC Capture sends to ChromaChecker as part of its normal operation are covered by the EULA and the Privacy Policy, not by these Plugin Terms.
4. Access this Plugin requests
- Google Drive: the OAuth scope
https://www.googleapis.com/auth/drive, which grants read and write access to the files in the Google account that signs in. This is a restricted scope under Google's API Services User Data Policy; because the application registration is yours, Google's verification and limited-use requirements apply to your project. - Dropbox: the permissions granted to your Dropbox application when the operator signs in, which include reading and writing file content and metadata.
- Amazon S3: whatever the IAM credentials you supply permit. We recommend issuing credentials scoped to a single bucket and to the minimum actions required (list, get, put) rather than reusing broad administrative keys.
5. Where credentials and cached files are stored
- Credentials (OAuth tokens, AWS keys) are stored in the operating system's credential store — macOS Keychain or Windows Credential Manager — under the service name
ChromaChecker-CloudStorage. They are not written to ChromaChecker's servers and not stored in plain text in application settings. Non-secret metadata (which provider, which account identifier) is kept in the application's own settings. - Downloaded files are cached on this computer under
~/.cc_capture/cloud_cache/, with a default limit of 500 MB, evicted least-recently-used, and refreshed when the provider reports the file has changed. The cache is local to the computer and to its user account.
6. Security and network behaviour (EULA §7.5)
- Outbound only, HTTPS (port 443) to the providers you enable:
*.dropboxapi.com,www.dropbox.com,googleapis.com,accounts.google.com, and the Amazon S3 endpoint for your region. - One temporary inbound listener. Signing in to Google opens a loopback listener on
localhoston an operating-system-assigned port, for the seconds it takes the browser to return the authorisation. It is not reachable from your network and closes when sign-in completes. - No background service. This Plugin runs only inside CC Capture and only while it is enabled.
- No browser cookies are set or read by this Plugin; sign-in happens in your own system browser, under the provider's own session.
A consolidated network summary for all of CC Capture, suitable for review by your IT department, is published in the Network Connections & Firewall Requirements guide.
7. Who administers what
- Your Organisation's administrator decides whether this Plugin may be used, registers the provider applications, and issues the credentials.
- Your Organisation controls the accounts and remains the data controller for everything held in them.
- An operator signs in with the credentials your Organisation provides and chooses which files to open or save.
- Revoking access is done in the provider's own console (Dropbox connected apps, Google account permissions, AWS IAM) and, on this computer, by disconnecting the provider in the Plugin's settings.
8. Licence and evaluation status
This Plugin is licensed under EULA §2.4: to your Organisation and assigned to a specific computer. During the evaluation period the Plugin is available for testing without a separate fee; after it, use may require a paid licence. Costs charged by Dropbox, Google or AWS for your own accounts and storage are yours in every case.
9. Availability, support and liability
- Provider outages are not defects in the Software. If a provider is unavailable, changes its API, suspends your account or alters its pricing, this Plugin may stop working through no act of ChromaChecker. Section 9 (Disclaimer of Warranties) and Section 10 (Limitation of Liability) of the EULA apply.
- ChromaChecker support covers the Plugin's own behaviour. It does not cover your provider accounts, their billing, their access policies, or recovery of data held with them.
- Back-ups remain yours. This Plugin is a means of access, not a back-up mechanism.
10. Removing the Plugin
Disabling or uninstalling this Plugin stops all access to your cloud accounts from this computer. Delete the stored credentials by disconnecting each provider before removal, or remove the ChromaChecker-CloudStorage entries from your operating system's credential store afterwards. The local cache directory may be deleted at any time; nothing in it is required by CC Capture. Files held with your providers are unaffected — ChromaChecker holds no copy to delete.
11. Changes to these Plugin Terms
These Plugin Terms are versioned. A new version replaces this text at the same address, and CC Capture asks your Organisation's administrator to accept it before the Plugin continues to be used. A change here does not alter the EULA or the terms of any other Plugin.
The version you accepted is recorded by the application, and every earlier version is kept below, so the text your Organisation agreed to can always be produced.
Revision history
| Version | Effective | What changed |
|---|---|---|
| 1.0 | August 5, 2026 | First publication |
ChromaChecker Corporation · 4324 Sanddollar Court, New Port Richey, FL 34652, USA · legal@chromachecker.com
Published at https://chromachecker.com/legal-plugin-cloud-storage