Cloud provider credentials are intended to stay on your device and are stored through the operating system credential store where supported.
The public platform processes account, device, licensing, support, release, security, and billing metadata needed to operate CloudPairs.
Diagnostics should never include passwords, private keys, API secrets, or sensitive file contents.
Scope of this policy
CloudPairs ("CloudPairs", "we", "us") operates cloudpairs.com, account and licensing services, software downloads, dashboard features, support workflows, and the CloudPairs desktop application.
This policy explains the categories of information involved in those services, how they are used, and the product boundaries around desktop storage credentials. It is written for transparency and should receive legal review before being treated as final legal advice.
Account and authentication data
Authentication is provided by Clerk. We may receive and store account identifiers, email addresses, profile metadata needed for sign-in, organization or plan metadata if enabled, trial dates, device activation records, entitlement status, dashboard preferences, support-related metadata, and security events.
We use this information to create and secure accounts, link devices, enforce plan limits, provide downloads and updates, show dashboard status, respond to support requests, prevent abuse, and maintain service reliability.
Desktop credentials and connection metadata
Cloud storage credentials, API keys, passwords, private keys, and OAuth tokens for supported desktop connections are intended to be stored locally through your operating system credential store where supported, such as Windows Credential Manager or macOS Keychain.
The CloudPairs website does not need those provider secrets to perform desktop transfers. Connection metadata such as names, hosts, bucket names, regions, ports, protocol choices, and non-secret preferences may be stored locally so the desktop app can show saved connections.
Payments and billing
If you purchase a paid plan, checkout and payment processing may be handled by a third-party payment provider such as Stripe. We may store billing status, plan, renewal or expiry date, invoice identifiers, customer identifiers, tax status, and transaction metadata needed to provide access and support.
CloudPairs does not store full payment card numbers on its own infrastructure. Payment providers may independently process card, wallet, tax, fraud-prevention, receipt, and dispute information under their own terms and policies.
Diagnostics, updates, and support
The desktop app may send or store non-secret diagnostic information such as app version, platform, release channel, last visible route, error context, crash details, feature flags, device activation state, or support identifiers to help improve reliability and support the product.
Do not send provider passwords, API keys, private keys, tokens, or sensitive files to support. If a support case requires logs, review them first and redact anything sensitive.
Retention and choices
We keep account, licensing, billing, security, and support records for as long as needed to operate CloudPairs, comply with obligations, prevent abuse, resolve disputes, enforce terms, and maintain business records.
You can revoke provider credentials from provider dashboards, remove or rotate credentials on your own systems, clear local app data from the desktop app, control browser cookies through browser settings, and contact support for account deletion or privacy help.
Contact
Questions about this page, account privacy, billing, security reports, or support can be sent to support@cloudpairs.com. Do not include live credentials, private keys, API tokens, or sensitive files in email.