HabitatOS All policies

Sensor Integrations and Third-Party Provider Notice

Effective Date: June 15, 2026

Last Updated: June 15, 2026

This Sensor Integrations and Third-Party Provider Notice explains how HabitatOS handles optional sensor-provider integrations, connected-device credentials, environmental telemetry, alerts, and third-party service limitations. This Notice is part of the HabitatOS Privacy Policy and Terms of Use.

1. Optional Sensor Integrations

HabitatOS may allow you to connect third-party sensor, thermostat, climate, automation, or connected-device providers. Supported providers may include MOCREO, Govee, Tuya/Smart Life, SensorPush, Inkbird, Herpstat, Shelly, SwitchBot, and other providers added over time.

Sensor integrations are optional. You do not need to connect a third-party sensor provider to use core HabitatOS recordkeeping features.

2. Authorization to Access Provider Accounts

If you connect a sensor provider, you authorize HabitatOS to use the credentials, tokens, API keys, device identifiers, or connection details you provide to access that provider on your behalf.

Depending on the provider, HabitatOS may request or store information such as email address, password, API key, API secret, client ID, client secret, region, local host address, device address, access token, refresh token, provider account metadata, provider device IDs, device names, hidden-device preferences, and selected assets. You are responsible for ensuring that you are authorized to connect the provider account, devices, sensors, APIs, and environmental data you configure in HabitatOS.

3. Third-Party Provider Terms

Your use of each connected provider remains subject to that provider's own terms, privacy policy, API rules, account rules, rate limits, subscriptions, warranties, and service availability.

HabitatOS is not responsible for third-party provider outages, device failures, API changes, data inaccuracies, billing issues, account restrictions, revoked credentials, or provider decisions to limit or discontinue access. Provider names are used to identify compatibility or integration options. Unless expressly stated, HabitatOS is not sponsored, endorsed, certified, or approved by those providers.

4. Sensor Data Collected

When you connect a provider, HabitatOS may collect, retrieve, generate, or store sensor-related information, including temperature readings, humidity readings, device online/offline status, captured timestamps, device names and provider device IDs, enclosure, zone, room, rack, or reptile mappings, alert rules and threshold settings, trigger values and alert events, acknowledgement and resolved status, aggregated hourly or daily readings, and integration connection status and sync metadata.

5. Credential Storage and Security

HabitatOS uses technical safeguards intended to protect provider credentials stored by the Service, including encryption for provider credentials where implemented.

No method of transmission, storage, encryption, or authentication is completely secure. You should only connect provider accounts that you are authorized to use, and you should protect your provider passwords, API keys, and account access.

If you believe a provider credential has been exposed, you should revoke or rotate it through the provider's own account tools and disconnect or reconnect the integration in HabitatOS where available.

6. Telemetry Retention

HabitatOS may poll connected sensor providers periodically and store raw readings for a limited period. Raw sensor telemetry is designed to be retained for 14 days before cleanup.

HabitatOS may also generate aggregated readings, summaries, alerts, dashboards, and trend data. Aggregated readings may be retained longer unless deleted with your account or as otherwise required.

7. Alerts and Monitoring Limitations

Sensor readings, alerts, thresholds, dashboard summaries, and notifications may be delayed, incomplete, inaccurate, unavailable, duplicated, or missed. Causes may include device failure, dead batteries, calibration issues, enclosure placement, Wi-Fi or internet outages, provider outages, API errors, sync delays, user configuration, app downtime, cloud hosting issues, notification delivery failures, or operating-system limits. HabitatOS is not an emergency monitoring system, animal-safety system, veterinary service, medical device, life-safety system, fire-safety system, or guaranteed climate-control system.

You remain responsible for directly monitoring animals, enclosures, temperatures, humidity, equipment, and safety conditions.

8. Animal Care Responsibility

Sensor integrations are informational tools only. HabitatOS may help organize, display, summarize, or alert on environmental data, but the Service cannot guarantee that readings are correct, that alerts will arrive in time, or that connected equipment is functioning safely.

You should use independent judgment, direct observation, backup thermometers or hygrometers where appropriate, and qualified professional advice for animal health or safety concerns.

9. Disconnecting Integrations

You may disconnect integrations where the Service provides that option. Disconnecting an integration may stop HabitatOS from retrieving new readings from that provider.

Disconnecting HabitatOS does not necessarily delete your provider account, provider data, provider billing relationship, or provider-side device history. To delete or manage information held by a third-party provider, contact that provider directly.

10. Local and Automation-Related Features

Some integrations may use local network details, device addresses, API endpoints, or automation-related controls. These features may depend on device compatibility, firmware, network configuration, provider APIs, account permissions, and feature flags.

Any automation, climate control, or advanced device-control feature should be treated as experimental unless expressly released as a production feature. Automated or semi-automated features must not be relied on as the only safeguard for animal health or safety.

11. Changes to Supported Providers

We may add, remove, limit, rename, or change supported providers, integration methods, polling intervals, alert behavior, telemetry retention, or related features at any time.

A provider integration may stop working if the provider changes its API, terms, authentication rules, device firmware, rate limits, or account requirements.

12. Contact Us

Paladin Labs LLC

11 Municipal Drive, Suite 200, PMB 1022

Fishers, Indiana 46038

United States

Email: Support@habitatos.io

Website: https://habitatos.io

State of Formation: Indiana

Paladin Labs LLC, Fishers, Indiana, United States. Contact: Support@habitatos.io

View all policies  |  Back to HabitatOS