PRIVACY POLICY
GW WEAR ENGINE
# Privacy Policy for GW Wear Engine
**Last updated: 21 September 2026**
GW Watchfaces ("we", "us", or "our") provides the **GW Wear Engine** Wear OS application (the "App"). This Privacy Policy explains what data the App accesses, how the data is used and stored, when data is sent to a third party, how long it is retained, and how users can delete it.
## Summary
- GW Wear Engine accesses health and fitness data to provide the user-requested **GW Cardio Load** feature.
- Health and fitness data is processed and stored locally on the user's Wear OS device. We do not receive it on our servers, sell it, use it for advertising, or share it with third parties.
- If the user enables **GW Feels Like**, the App sends the watch's location coordinates to Open-Meteo over HTTPS to obtain current apparent-temperature data.
- The App does not create user accounts and does not include advertising or analytics SDKs.
## Data the App accesses and how it is used
### Health and fitness data
When the user chooses to enable GW Cardio Load and grants the requested Android permissions, the App accesses the following data through Wear OS Health Services:
- **Daily step count** — used as a light-movement input for the Cardio Load calculation.
- **Daily calories burned** — accessed and stored for local compatibility and diagnostic state; the current Cardio Load model does not use total daily calories as a direct load input.
- **Heart-rate samples (beats per minute)** — used to estimate cardiovascular intensity, exercise minutes, resting-heart-rate baseline, daily maximum heart rate, and the user's Cardio Load.
- **Derived fitness information** — including Cardio Load score and status, daily load, personalized target range, estimated exercise minutes, resting-heart-rate estimate, and maximum-heart-rate reference.
The App uses this data only to calculate and display GW Cardio Load in the App and in the Cardio Load watch-face complication. GW Cardio Load may continue receiving passive Health Services updates, including heart-rate data, while the App is closed or not actively in use, but only after the user grants the applicable background health permission.
GW Wear Engine does **not** transmit health or fitness data off the watch. We do not receive, sell, share, use for advertising, or use this data to identify the user.
### Location and weather data
The optional GW Feels Like feature requests approximate and precise foreground location permission. When the user taps to enable or update this feature, the App obtains the watch's current or last-known location and stores the coordinates locally. The App sends the latitude and longitude over an encrypted HTTPS connection to the **Open-Meteo** weather API to request apparent-temperature data. Open-Meteo also necessarily receives the request's IP address.
Location is used only to provide local weather/apparent temperature. It is not combined with health data and is not used for advertising, analytics, or tracking. The App does not request Android background-location permission. After foreground setup, automatic weather refreshes may reuse the locally cached coordinates without requesting a new location.
Open-Meteo acts as the external weather service. According to its published policy, its API server logs may contain IP addresses and geographic coordinates and are deleted after 90 days. Its terms and privacy information are available at <https://open-meteo.com/en/terms>.
### Compass sensor data
The App processes compass and motion-sensor readings to provide the compass heading and watch-face complication. These readings are processed locally and are not transmitted off the device.
## Android permissions
Depending on the Wear OS version and features enabled by the user, the App may request:
- `ACTIVITY_RECOGNITION` to access daily step and calorie activity signals for GW Cardio Load.
- `BODY_SENSORS` or `READ_HEART_RATE` to access heart-rate data for GW Cardio Load.
- `BODY_SENSORS_BACKGROUND` or `READ_HEALTH_DATA_IN_BACKGROUND` to receive passive heart-rate updates while the App is closed or not actively in use.
- `ACCESS_COARSE_LOCATION` and `ACCESS_FINE_LOCATION` to obtain watch coordinates when the user enables or updates GW Feels Like.
- `INTERNET` to request apparent-temperature data from Open-Meteo.
Users can deny or revoke permissions at any time through Wear OS settings. Revoking a permission stops future access governed by that permission but does not by itself delete data already stored locally by the App.
## Storage and retention
Health, fitness, location, weather, and derived Cardio Load data are stored only in the App's private local storage on the Wear OS device. Android application sandbox protections restrict other apps from accessing this storage, and Android backup is disabled for GW Wear Engine.
- Today's step, calorie, heart-rate-derived, exercise-minute, and load values are reset when a new day begins.
- Derived daily Cardio Load history is retained locally for up to 28 days to calculate a personalized target.
- Current estimates and settings, such as resting-heart-rate estimate, maximum-heart-rate reference, permission/registration state, cached coordinates, and cached weather data, remain locally until replaced or until the App's data is cleared or the App is uninstalled.
- We do not retain health or fitness data on developer-controlled servers because the App does not transmit that data to us.
- Open-Meteo's retention of API logs is governed by Open-Meteo's policy described above.
## Sharing and sale of data
We do not sell personal or sensitive user data. We do not share health or fitness data with third parties. The only external data transfer initiated by the App is the optional transmission of location coordinates and the network request's IP address to Open-Meteo for the GW Feels Like weather feature.
The App does not contain advertising SDKs, analytics SDKs, social-network SDKs, or developer-operated account services.
## Security
Data retained by the App is stored in Android app-private storage and protected by the Wear OS application sandbox and applicable device security. Network requests to Open-Meteo use HTTPS encryption in transit. No method of storage or transmission can be guaranteed to be completely secure.
## User choices and deletion
Users may stop future access by revoking the App's permissions in Wear OS settings. Users may delete all data stored by GW Wear Engine by clearing the App's storage/data in Wear OS settings or by uninstalling the App. Because the App has no user account and does not upload health data to us, there is no developer-held health-data account or server copy to delete.
Questions or privacy requests may be sent to **gwatchdesign@gmail.com**.
## Children's privacy
GW Wear Engine is not designed or directed to children under 13. We do not knowingly collect personal information from children on developer-controlled servers.
## Health disclaimer
GW Wear Engine and GW Cardio Load are intended for general fitness and wellness information only. They are not medical devices and do not diagnose, treat, cure, or prevent any medical condition. Cardio Load values are estimates and should not be used for medical decisions. Users should consult a qualified healthcare professional for medical advice, diagnosis, or treatment.
## Changes to this Privacy Policy
We may update this Privacy Policy when the App or its data practices change. We will update the "Last updated" date when changes are posted. Material changes will be reflected in the App and/or its Google Play listing as appropriate.
## Contact us
Developer: **GW Watchfaces**
App: **GW Wear Engine**
Email: **gwatchdesign@gmail.com**