PulseMaze · privacy

Privacy
policy

Not written yet
PulseMaze hasn't shipped, so there is nothing honest to say here yet. The headings below are the shape this policy will take; each one gets a real answer before the app goes anywhere near Google Play.

Last updated: [DATE] · Applies to: PulseMaze for Wear OS, version [X.Y]

The short version

[TO BE COMPLETED — the one-paragraph summary. If the app collects nothing at all, say exactly that, here, in plain words.]

What stays on your watch

[TO BE COMPLETED — best times, settings, anything else kept locally, and how to clear it.]

Sensor data

[TO BE COMPLETED — the accelerometer is read to move the ball. State whether readings are ever stored or transmitted, or used only for the current frame and discarded.]

Diagnostics and crash reports

[TO BE COMPLETED — name the SDK if there is one, list exactly what it sends and what it never sends, and say whether it can be switched off.]

Third parties

[TO BE COMPLETED — any analytics, ad networks or SDKs, with links to their policies. If there are none, say so.]

Permissions

[TO BE COMPLETED — each Android permission the app requests and why.]

Children

[TO BE COMPLETED — the minimum age, and anything Google Play's Families policy requires.]

Deleting your data

[TO BE COMPLETED — how to clear on-watch data, and who to contact for anything held elsewhere.]

Changes to this policy

If this policy changes in a way that matters, the date at the top changes and the previous version stays in the site's git history.

Contact

hello@bitesizebureau.com. [CONFIRM: data controller name and postal address, if required.]

← Back to PulseMaze