Purpose
This policy defines a practical retention baseline for Availight Cloud. The goal is to keep enough data to operate Smart Display, support device ownership, troubleshoot reliability, and protect the service without keeping sensitive data longer than necessary.
Data Categories
- Account profile: email, account ID, and profile timestamps kept while the account is active.
- Claimed devices: Controller install ID, product type, room name, firmware/protocol versions, and claim timestamps kept while the device is claimed.
- Delivery tokens: hashed Controller delivery token and active/revoked state kept while needed for device delivery and security.
- Pending deliveries: normalized event delivery or clear-source commands kept until acknowledged, expired, failed, or device unclaimed.
- Provider connections: provider source, encrypted token reference, selected calendars, and connector settings kept while connected.
- Provider event cache: redacted event window, source, status, title if needed, and transition timing kept only as needed for sync and upcoming context.
- Cloud audit events and diagnostics: privacy-safe claim, unclaim, token rotation, provider connect/disconnect, delivery, sync, and health information kept for support and security review.
Deletion Triggers
Disconnecting a provider should delete or invalidate its encrypted token reference, clear source-specific active events, stop provider polling or webhook/watch channels where supported, and queue a clear delivery to the Controller.
Unclaiming a Controller should revoke active Controller delivery tokens, fail or clear pending deliveries, disable cloud polling from the mobile app when local access is available, and remove the device from the account's active registry.
Account deletion should disconnect providers, unclaim or detach devices, revoke active delivery tokens, delete provider token references and feed URLs, and delete or anonymize profile data where technically and legally practical.
Data Minimization Rules
- Do not store Wi-Fi passwords or setup codes in Availight Cloud.
- Do not return OAuth tokens, delivery tokens, token hashes, or feed URLs through diagnostics.
- Avoid storing provider raw payloads after normalization.
- Avoid storing attendees, descriptions, locations, and conference links unless a future feature explicitly requires user consent.
- Prefer current state plus short operational history over indefinite logs.
Operational Retention Targets
- Pending deliveries should expire at or before their event transition or queue expiry.
- Provider event cache should keep only current and near-future windows needed for Smart Display, generally within the next 18 hours unless sync requires a provider token cursor.
- Audit events should be kept 90 days during beta unless investigating abuse or support issues.
- Connector diagnostics should keep latest state and last sync/error timestamps.
- Deleted account cleanup should complete within 30 days where technically and legally practical.
User Request Process
Users can request account or device deletion through support. Support should verify account ownership before deleting cloud data or unclaiming devices.
- Email: support@availight.com
- Website: https://www.availight.com