HCC Privacy Policy

The Ecosystem

Home Climate Control ecosystem consists of:

• HCC Core;
• HCC Remote;
• Cloud server supporting communications between HCC Core and HCC Remote.

Standalone operation

• HCC Core configured for standalone operation collects no personally identifiable information.

Remote Access Operation

• When configured for remote access, all three components rely on account security features offered by Google (including, but not limited to, authentication, authorization, and encryption).
• A Google Account is required by all three components in order to use the above features. The same identity will have to be provided to HCC Core and HCC Remote, and matched at the cloud server to enable two-way communication between HCC Core and HCC Remote. OAuth 2.0 will be used to request the identity, and the user will have to provide explicit consent at both HCC Core and HCC Remote to allow access. This consent may be revoked by the user at any time. Note: We recommend that you create a separate account specifically for this purpose.
• Android permission to use contacts is required by HCC Remote in order to choose which account to use for authentication and authorization for Home Climate Control. This permission can also be revoked by the user at any time.
• HCC Core configured to use Google Calendar for event scheduling needs a permission to use the calendar. Note: We recommend that you create a separate account specifically for this purpose.

Abuse Prevention

The cloud server may store request originator identity for a reasonable period of time to prevent service abuse.

No Third Party Disclosure

Under no circumstances any user provided information is made available to third parties.