Skip to content

Privacy & Disclaimer

Michal Zaniewicz edited this page Jul 14, 2026 · 2 revisions

Please read this before using the integration.

Unofficial - use at your own risk

This is an unofficial, experimental hobby project. It is not affiliated with, endorsed by, or supported by Suunto Oy, Amer Sports, or Sports-Tracker. All trademarks belong to their owners.

  • Built on shifting ground. It talks to a private, undocumented endpoint (the Sports Tracker backend the Suunto app uses) that can change or stop working at any moment - a single app update may break it.
  • Possibly against Suunto's Terms of Service. Check them yourself. Excessive requests could get your account limited or closed; that's on you.
  • Your account only. Use it strictly for your own data - never to collect or aggregate anyone else's.
  • No warranty, no liability. Provided "as is". None of this is legal advice. If any of it gives you pause, just use the official Suunto app.

How your data is handled

The integration runs entirely inside your Home Assistant. It fetches your own Suunto data from Sports Tracker and stores it in HA. It does not send your data anywhere else, and there is no third-party server involved beyond Suunto/Sports Tracker itself.

Credentials

  • Your password is used once (at setup, and again only on reauth) to obtain a session token, then discarded. It is never written to disk.
  • Only your email and the revocable session token are persisted to HA's .storage.
  • A revocable token is safer to persist than a reusable password. Note that HA .storage is plaintext - a Home Assistant limitation; keeping only a token (not your password) limits the exposure.
  • There is no silent re-login with a stored password (none is stored). An expired session surfaces as an explicit reauth prompt.

See Configuration for the user-facing flow and Architecture for the login pipeline.

"New login" emails

Suunto sends a notification email on every login. The integration caches and reuses the session token across restarts to minimise these - expect one on first setup and on reauth, not during normal polling.

Rate / load

Keep the history poll interval modest (default 60 min). The long-term-statistics backfill means a slower poll still captures late syncs, so there's little reason to hammer the API. See Long-term Statistics.


Credits & license

  • Login pipeline ported from tajchert/suuntool.
  • See the repository's LICENSE for license terms.

Clone this wiki locally