MOBILE PRIVACY POLICY · VERSION 2026-07

Privacy boundaries for future native access

This module prepares a documented API for a future native client. It does not mean an iOS or Android application has been released, reviewed by an app store, or approved for emergency use.

Information the mobile API may process

Account profile, approved synchronization namespaces, My Forest people and places, Care Circle records, alert preferences, published county resources, device identifiers, access-token metadata, native push tokens, app version, operating-system version, language and synchronization-conflict records.

Information excluded

Employer administration, employee wellness activity, diagnoses, treatment details, medical history, insurance information, passwords, one-time login links, private API keys, unrelated WordPress data and another household’s records.

Tokens and devices

Access tokens are stored only as one-way hashes. Native push tokens are encrypted at rest. Device access can be revoked, and refresh tokens rotate after use.

Offline synchronization

When a device writes against an older revision, the API returns a conflict instead of silently overwriting newer server data. The client must use the server version, the client version or an explicit merged version.

Emergency boundary

The future native client must not present cached information as current or replace 911, official AQI sources, evacuation warnings, county alerts or emergency orders.

App-store status

No iOS or Android application is represented as released, reviewed or approved by an app store through this module.