Privacy

LiftShift is designed to work without sending your full training history to a LiftShift-owned database. The goal is: you get analytics, without giving up control of your data.

What LiftShift processes

LiftShift reads your workout history (exercises, sets, reps, weights, dates, notes) from Hevy, Strong, or Lyfta to compute analytics locally. This includes exercise names, set-level data, workout dates, and any notes or RPE/RIR values you’ve logged. Muscle mapping is done client-side using a built-in exercise-to-muscle database.

Where data is processed

All computation — heatmap generation, plateau detection, set-by-set analysis, PR tracking, and AI export formatting — happens entirely in your browser using IndexedDB. LiftShift does not upload your workout data to a server for processing. The only network requests are to the Hevy API (if you use API sync instead of CSV import) and to fetch the LiftShift application code itself.

What LiftShift stores

  • Your workout data — stored locally in your browser’s IndexedDB. This never leaves your device.
  • Application preferences — platform selection, date filter ranges, and UI settings are stored in localStorage.
  • Anonymous page view analytics — LiftShift uses Google Analytics to track anonymous page views (URLs visited, no workout data). You can block this with any ad blocker or by disabling JavaScript.

What LiftShift does not store

  • Your full training history is never stored on LiftShift servers.
  • Your Hevy, Strong, or Lyfta account credentials are never seen by LiftShift. Hevy API auth uses OAuth and LiftShift never receives your password. CSV imports are processed entirely in-browser.
  • LiftShift does not use cookies beyond what the app itself needs to function (localStorage preferences).
  • No personal identifiers (name, email, location) are collected or stored by LiftShift.

Important limitation

While LiftShift does not store your data, the third-party apps you connect to (Hevy, Strong, Lyfta) do. LiftShift has no control over their data practices. If you use Hevy API sync, Hevy’s servers will process your request and transmit your workout history to your browser. Review each app’s privacy policy for details on how they handle your data.

For more background on the design choices behind LiftShift’s architecture, see the How it works guide. The full source code is available on GitHub under AGPL-3.0.