Our Commitment To Privacy

Your privacy is important to us. To better protect your privacy we provide this notice explaining our online information practices at stablebit.cloud. To make this notice easy to find, we make it available at https://stablebit.cloud/privacy.

The Way We Use Cookies

  • The stablebit.cloud service does require the use of cookies in order to facilitate:
    • The functionality of the stablebit.cloud service (for example, authentication, authorization, persistent session data, etc...).
    • Analytics data in order to track and analyze visitors to stablebit.cloud.
    • In order to facilitate access to APIs provided at stablebit.cloud.

The Way We Do NOT Use Cookies

  • We do NOT use cookies to track or sell usage data for advertisement purposes.

The Information We Collect

This notice applies to all information collected or submitted on the stablebit.cloud website, or using software that interoperates with stablebit.cloud.

The Types of Information Collected at stablebit.cloud:

  • Information is provided to us by our users at stablebit.cloud in order to facilitate the functionality of the service.
  • Information is automatically collected from systems running StableBit software in order to facilitate the functionality of the stablebit.cloud service.
  • For example, some of this information may include (but is not limited to):
    • Email addresses, phone numbers, addresses, location names, that are entered by our users.
    • Real-time operating metrics from computers running StableBit software.
    • Performance metrics, such as temperatures and operating throughputs.
    • Hardware identification information, such as model numbers, serial numbers, plug-and-play identifiers, etc...
    • And any other information that is required to facilitate the functionality of the stablebit.cloud service.

The Types of Information NOT Collected at stablebit.cloud:

  • We do not automatically collect diagnostic information from systems running our software. 'Automatically' refers to the collection of information without explicit, case-by-case consent from the user.
  • For example, we do not collect usage data, log files, telemetry, or diagnostics information from systems running our software without your consent.
Collection of Diagnostic Information Under Specific Circumstances:

Diagnostic information may be collected only with your explicit consent in specific instances, such as:

  • Engaging with customer service where you may choose to provide us with diagnostic data to assist in troubleshooting issues. For example, if an application error occurs, we might request that you send error reports or diagnostic logs. Consent for this is obtained through a clear, affirmative action on your part before any data is transmitted.
  • Additionally, in the event of an application malfunction, we might request that you submit an error report for analysis. An example dialog might be: "This application has stopped working. Would you like to submit an error report including logs for analysis?" Consent is also obtained through a clear, affirmative action on your part before any data is transmitted.

Troubleshooting Tool

From time to time, Covecube may provide troubleshooting functionality (the "Troubleshooting Tool") to help diagnose issues with StableBit software and the stablebit.cloud service. The Troubleshooting Tool may be delivered as a standalone troubleshooting utility and/or as troubleshooting commands or features built into the StableBit software. Regardless of delivery method, the Troubleshooting Tool runs locally on your computer and will only collect and transmit diagnostic information when you explicitly initiate a troubleshooting submission (for example, by running a troubleshooting command that generates and uploads a diagnostic package). The Troubleshooting Tool requires elevated permissions (for example, Administrator/root) to access certain operating system logs or crash data.

A troubleshooting submission may include, but is not limited to, some or all of the following categories of information (examples):

  • Account identifiers (e.g., user name, user ID, and device name).
  • Application and installer logs generated by StableBit software.
  • Application state (e.g., service state/configuration files and service binaries).
  • System information relevant to troubleshooting (e.g., operating system version and configuration, storage and mount configuration, loaded drivers/services/modules, network configuration and active listening services, and a snapshot of running processes).
  • System and application logs (e.g., Windows Event Logs; Linux journalctl output; macOS unified logs; and other common OS log files, where present).
  • Crash reports and dumps (e.g., OS crash minidumps and/or service crash reports, where present).
  • Service memory dumps which may contain a snapshot of the memory of a StableBit service process.

Important: log files, crash reports, and especially memory dumps can sometimes contain sensitive information (for example, file paths, user names, hostnames, IP addresses, and, in some cases, contents of data that happened to be in memory at the time of collection). If you are concerned about the contents of a troubleshooting submission, you should review the generated diagnostic package before uploading it. The Troubleshooting Tool waits for your confirmation (unless explicitly overridden) before any upload occurs. You are encouraged to review the generated files prior to approving transmission.

How You or Others Can Access Your Information

  • You can access the information collected by using the stablebit.cloud service.
  • Information that you explicitly choose to share publicly will be made visible on the stablebit.cloud service to anyone on the public Internet.

Persistence of Data

  • You can choose to delete your stablebit.cloud account at any time. All information that was collected and linked to your account will be permanently deleted as well.
  • It may take a while to fully purge all of the information associated with your account after account deletion. You will be informed if there will be a delay involved in the account deletion process, otherwise all of your account data will be deleted immediately. This delay is to take into consideration the physical hardware limitations in place on our ability to purge your data, and typically should not last longer than 48 hours.

The Way We Use Information

  • We do not rent or sell any information provided to stablebit.cloud to third parties.
  • Any information provided to stablebit.cloud is used to facilitate the functionality of the stablebit.cloud service and for Customer Service purposes.

Customer Service

  • Any information provided to customer service is archived in our system for record keeping purposes.
  • Employees and contractors of Covecube Inc. (which operates stablebit.cloud) have access to the customer service archived data.
  • Information provided to customer service through stablebit.cloud is never intentionally made visible to the public Internet.