Cloudbolt

CloudBolt Privacy Policy: Key Points and Risks

1. Data Collection and Use

CloudBolt may collect:

• Identifiers: Name, email address, account/user ID, and payment information such as credit or debit card details.
• Technical and usage data: IP address, browser and device type, operating system, pages viewed, clicks, visit frequency, time spent, access dates/times, connection speed, network location, server location, and log data.
• Information from login providers: If you use Google, Facebook, Apple, or another authenticator, CloudBolt may receive your name, email address, and other information you authorize that provider to share.
• Automatically collected data: Cookies, Flash/local storage objects, web beacons, traffic data, location data, and communications-related data.

CloudBolt says it uses this information to:

• Provide, operate, secure, personalize, improve, and develop its services;
• Create and manage accounts;
• Process payments and prevent fraud;
• Provide support and respond to inquiries;
• Conduct surveys, promotions, testing, research, analytics, and product development;
• Send marketing, targeted offers, emails, or text messages where consent or applicable law requires it;
• Comply with legal and law-enforcement requests.

Potential risk: The policy permits broad use for analytics, product development, personalization, and marketing. It does not clearly specify how long different categories of data are retained or identify all applicable legal bases for non-EU users.

2. User Rights

All users

You may:

• Close your account;
• Request deletion of personal information, subject to legal and operational exceptions.

Deletion may be refused or limited where information is needed for legal compliance, investigations, disputes, litigation, security, debugging, or internal business purposes. Deleting required information may prevent you from using CloudBolt.

California residents

The policy describes rights to:

• Know what personal information is collected, its sources, purposes, and specific data collected;
• Receive portable copies of data;
• Correct inaccurate information;
• Delete information, subject to exceptions;
• Avoid discriminatory treatment for exercising these rights.

Requests require identity verification. Requests to know may generally be made twice in a 12-month period, and CloudBolt aims to respond within 45 days, with a possible additional 45-day extension.

Important limitation: CloudBolt states it is currently not a “covered business” under the CCPA, although it says it will honor these rights if it becomes covered.

EU/EEA users under GDPR

Users may have rights to:

• Access, correct, erase, restrict, or port personal data;
• Object to processing, including direct marketing and certain profiling;
• Withdraw consent;
• Avoid decisions based solely on automated processing, subject to exceptions;
• Complain to an EU supervisory authority.

The policy says data is processed in the United States. It requests consent for transfers to the U.S., which lacks an EU adequacy decision. The policy references processor contracts and security measures but does not clearly identify specific transfer mechanisms, such as Standard Contractual Clauses.

3. Third-Party Sharing

CloudBolt may disclose information to:

• Contractors, service providers, data processors, and other business partners;
• Payment processors, identity-verification providers, analytics providers, and marketing providers;
• Third parties when you consent;
• Government authorities or other parties when legally required.

CloudBolt states it does not sell personal information. However, “sale” may have a narrower legal meaning than other forms of advertising, analytics, or data sharing. The policy does not provide a detailed list of recipients or identify each processor.

4. AI/ML Training

The policy does not expressly state whether user content, account data, support communications, or usage data is used to train artificial-intelligence or machine-learning models.

Although “testing, research, analysis, and product development” is permitted, that language does not clearly confirm or exclude AI training. Users should seek clarification before submitting confidential, proprietary, or sensitive information.

5. Key User Obligations and Restrictions

Users are responsible for:

• Keeping usernames and passwords confidential;
• Not sharing login credentials;
• Providing and maintaining a current, active, deliverable email address;
• Managing browser cookie settings, understanding that disabling cookies may impair functionality;
• Using CloudBolt only if they accept the Privacy Policy and related Legal Agreements.

Users who disagree with the policy must stop using CloudBolt. The policy does not detail broader acceptable-use restrictions; those may appear in the separate Legal Agreements.

6. Liability and Disputes

CloudBolt says it uses “commercially reasonable” security measures, including encryption, access controls, firewalls, and secure servers. However:

• Internet transmission is not guaranteed to be secure;
• CloudBolt does not guarantee complete security;
• Transmission is at the user’s risk;
• CloudBolt disclaims responsibility for circumvention of privacy or security settings.

This policy does not state a governing law, forum, arbitration requirement, dispute procedure, or specific monetary liability cap. Those terms may be contained in the separate Legal Agreements. The policy itself offers limited protection if a data incident occurs.

7. Policy Changes

CloudBolt will post changes on the same policy page. For material changes to how personal information is treated, it says it will provide notice, but does not specify whether notice will be by email, account notification, or another method.

Users must maintain a valid email address and periodically check the website and policy. Continued use after changes may effectively mean acceptance under the related Legal Agreements.