Poke Workout privacy policy
Poke Workout is made by an independent developer. Any data you submit to this app is submitted to the developer, not to Garmin. Data is kept only as long as needed to run the game and its purchases.
What stays on the watch
Your activity and step data never leave the watch. Poke Workout has no analytics, advertising or telemetry, and it never exports raw health data.
Poke Workout reads activity only after you choose Accept on the fourth activity notice page. Decline or BACK keeps activity access disabled; existing saved adventures remain available. The Garmin UserProfile permission is separate from this app choice. Home → Data / privacy opens the notice and withdrawal/deletion controls. A fresh install can reopen the notice by confirming a starter; no activity is read until acceptance.
Steps award XP to the saved active companion. Available recorded workouts of at least 1,200 seconds award one credit per qualifying summary, regardless of sport or distance. No route, location or heart-rate history is requested.
Local storage contains the adventure (owned species/XP, selected companion, credits, gyms and badges), setup eligibility timestamp, daily step high-water checkpoints, calendar/omission context, credited or ambiguous workout start/duration identities, closure/update counters, save generations, the activity consent and the purchase consent. Purchase state on the watch (unlock status, the delivered-item cursor and the hash of the last license key that got an answer) is stored with it. Two slots protect committed progress. Activity probe observations are transient memory and are cleared with the app.
Available step recovery is bounded by up to seven daily objects. An eight-epoch-day rolling reconciliation window closes older step corrections permanently. Workout identity retention is bounded to 64 combined credited/ambiguous rows; at capacity workouts stay pending and saved step progress can continue. Workouts are never silently pruned. Garmin history retention/completeness, timer-versus-elapsed duration, unique identities, multisport grouping and travel/calendar behavior remain unverified on physical hardware. Cross-device or all-account history is not promised.
Purchases and network use
The free part of the adventure (up to the Boulder Badge) needs no network at all. Purchases use the network, and only after you choose Allow purchases on the purchase notice. The notice appears the first time you open the unlock page, the Shop or the license-key path. "Not now" goes back and sends nothing.
The watch has no direct internet connection. Every request goes through the Garmin Connect app on your paired phone to the developer's purchase server. The watch sends:
- its watch code (an 8-symbol code generated on the watch; it is also shown in the unlock QR address),
- a cursor (the number of the last purchase item the watch has received), to check for and confirm purchases,
- the license key you type into the app settings, only when you ask to move the unlock to this watch.
Nothing else is sent: no name, no email, no activity, steps or other health data.
Ordering after consent: the purchase check at app start runs only once you have allowed purchases. After a reinstall, the unlock comes back once you open the unlock page or the Shop and choose Allow purchases again.
Garmin Connect and your phone handle the connection itself; their own privacy terms apply to that transport.
What the phone may keep
The license key you type is stored as an app setting by Garmin Connect. The watch clears that setting after the server gives a definitive answer, but until then Garmin Connect may keep the last value you entered on the phone.
What the purchase server keeps and for how long
The purchase server (a Cloudflare Worker with its database) keeps:
- orders: the watch code, the item bought (SKU), its status (paid, refunded, disputed), the creem product, checkout and order ids (the price follows from the item; no card or billing details);
- the buyer email passed on by creem with each completed checkout, stored as plain text and as a keyed hash, so support can find the orders of a buyer;
- the license-key hash (never the key itself) and a count of how often the unlock was moved to another watch;
- purchase items delivered to a watch code and the cursor the watch has confirmed;
- rate-limit rows holding a keyed hash (HMAC) of the requesting IP address, deleted after their time window ends.
The server keeps no raw IP addresses, no names, no plaintext license keys and no health data. Server logs record only the event type, an outcome and a short order token; request logging is off because request addresses carry the watch code.
Orders and emails are kept for as long as needed to restore purchases, handle refunds and disputes, and meet legal record-keeping duties. No fixed automatic deletion period is implemented today.
This website
The pages of this website are served by the purchase server. They set no cookies, run no scripts, load no third-party assets and have no analytics. Request logging is off.
Payment
Payment is handled by creem (creem.io), which acts as merchant of record and reseller. You pay on your phone on creem's checkout page; card and billing details go to creem, never to the watch or to the purchase server. creem's own buyer terms and privacy policy apply to the payment. Refunds are described in refund policy.
Remove my data
Data / privacy → Withdraw / delete → Confirm deletion removes the adventure (both save slots), the checkpoints, the activity consent and the purchase consent from the watch. Cancel preserves everything. The unlock and every purchase come back to a new adventure once you allow purchases again. This button does not delete anything on the purchase server.
Confirmation immediately stops pending scans/battle results, writes a deletion marker and verifies both slots and consent are absent before clearing it. On storage failure the app shows deletion pending, disables reads and hides old slots; reopening retries deletion. A marker-write failure also attempts to remove consent and reports failure, never success. If the storage system refuses all writes/deletes, persistence cannot be guaranteed: retry is required. Reaccepting and choosing a new starter establishes a fresh baseline, with no inherited step or workout rewards.
Watch data otherwise persists locally until confirmed deletion or app removal.
Deleting server records
To ask for your purchase server records to be erased, write to support@pokebattle.dev and include the email you used at checkout or your watch code. An erase removes the stored email and its hash from all of your orders. The order records themselves, without the email, are kept to handle refunds and disputes and to meet legal record-keeping duties. Erasure is a manual operator action today; there is no self-service erase. creem keeps its own records of the payment under its own terms.
Contact
Support: support@pokebattle.dev.