Support

Pumpfoilytics is a small project run by a single developer who pumpfoils. Replies typically land within 1–3 days. There's no phone support or live chat.

Email

Reach us at pumpfoilytics@gmail.com. Please include:

Common questions

The watch app is on the Connect IQ Store but I cannot install it

Make sure your watch is paired with the Garmin Connect Mobile app and you are signed in with the same Garmin account on both. The Connect IQ Store app needs to "see" the watch to push the install. If the install hangs, restart Garmin Connect Mobile and retry.

How do I get the Companion app?

The Android Companion app is in beta — join the tester waitlist on the Companion page and we'll send your invite (Play Store beta or a direct APK download). Public release follows the testing window. iOS comes later and has no firm date yet.

Why does my session show 0 pumps but I clearly pumped?

Pump detection runs second-by-second on the watch, from the GPS speed signal plus motion data from the built-in accelerometer. If the GPS lock was poor, the speed signal is noisy and detection thresholds may not trigger. Try recording in a clear area with no overhead obstructions for the first few minutes so GPS settles.

How do I export my data?

The watch app doesn't store sessions itself — they live in your Garmin Connect account. From there you can sync or upload them into the Pump Lab on pumpfoilytics.com, or use Garmin Connect's standard FIT export and keep the file.

I want to delete all my data

Watch-app data lives in your Garmin Connect account — delete sessions there. The Companion app stores its data locally; uninstalling it removes everything. If you have a pumpfoilytics.com account or you're on a tester waitlist, email us and we'll delete your account and all data we hold for you. (Details in the Privacy Policy.)

Bug reports

If you have a GitHub account and the bug is reproducible, you can open an issue at the project's repository (link shared on request). Otherwise, an email with the watch model + Pumpfoilytics version + steps-to-reproduce is the fastest path.

Feature requests

Welcome — but the project is intentionally small and iterations are slow. The roadmap is shaped by what the developer pumpfoils with, not by issue-vote-count. Email is the right channel; expect a thoughtful "yes / not yet / not planned" rather than a queue position.

← Back to home  ·  Privacy  ·  Imprint  ·  Cookie Settings