Privacy Policy

Last updated 31 July 2026

Movesesh is a workout tracker that stores your training on your own device. There is no account to create and no advertising. This policy describes every way data leaves your phone, one section per flow, so that anything missing is conspicuous.

The data controller is Porluz LLC, 418 Broadway Ste N, Albany, NY 12207, United States. You can reach us at support@movesesh.com.

What stays on your device

Your workouts, programs, exercise history, personal records, and settings are stored in a database on your phone. They are not transmitted to us, because there is nowhere to transmit them to. We operate no server that receives your training data and no account system that could associate it with you.

Exports are yours to initiate. When you export a CSV, the app hands the file to your operating system's share sheet and you choose where it goes. It does not pass through us.

Your device language is read locally to pick a translation. Fonts are bundled inside the app rather than fetched from a font service.

Flow 1: the version check

The app asks our website whether a newer version of Movesesh exists. This happens when the app cold starts, and when you return to it if the last successful check is more than four hours old.

The request fetches a single static file and carries no query string, no identifier, and no request body. It conveys only what any HTTP request unavoidably conveys: the IP address the request came from and a User-Agent string. Nothing distinguishes your install from any other, and we do not log or analyse these requests beyond the standard access logging described below.

This exists so that a build with a serious defect can be superseded, not to count users.

Flow 2: over the air updates

Movesesh is built with Expo, and Expo's update mechanism checks their servers on cold start for a newer JavaScript bundle. This request transmits your IP address, your platform, and the app's runtime version to Expo, who are a third party to us.

This happens in native code inside the update library rather than in code we wrote, which is precisely why it is disclosed here: a policy written by reading only our own application code would have missed it. Expo's handling of that data is governed by their privacy policy.

Flow 3: crash reports

When the app crashes, it sends a report to Sentry so that the defect can be found and fixed. A report carries the error type and message, the stack trace, your device model, your operating system version, and the app version. It carries no account, because there are none, no name, and none of your training data.

Reports are processed and stored in Sentry's European Union region. The app also sends an anonymous session record when it launches, which is what lets us measure how many sessions end in a crash rather than only counting crashes in isolation.

You can turn this off in Settings, under Privacy, with the Send crash reports switch. Once it is off, later launches send nothing at all: the app does not start the reporter, installs no crash handler, and makes no request to Sentry whatsoever.

Two limits worth stating precisely, because a switch that claims to be instant would be overpromising. In the session where you turn it off, reporting has already started: it stops at once for errors the app catches itself, but a crash severe enough to be handled below the app can still be written to your device in the moment straight after, and it then stays on your device unless you turn reporting back on. Separately, the app keeps your choice in a small file so it can be read before reporting starts, and on the first launch after updating from a version older than that file, or if writing it ever failed, that one launch behaves as though reporting were on: it sends a single anonymous session record and uploads a crash already stored from an earlier run. It then corrects itself and does not repeat.

Flow 4: usage statistics

The app reports a small, fixed set of events so we can see which features are used and whether people come back. It is a closed list of seven: the app launching, onboarding finishing, your first workout being logged, a workout being completed, a program being started, data being exported, and the Appearance setting being changed. Nothing else is reported, and adding to that list means changing this page.

An event carries no workout data, no names, and no account, because there are none. It carries a random identifier created on this install, sent only as an irreversible hash, which exists so that repeat visits can be counted without knowing who you are. Deleting the app's data resets it. Your language, app version and operating system are attached, which is what lets us tell whether a translation is working. Nothing else rides along: the app sends exactly those three fields with each event.

This is processed by TelemetryDeck, a company based in Germany, and stored in the European Union. You can turn it off in Settings, under Privacy, with the Send usage statistics switch. Events are held on your device and sent in batches, so turning the switch off also discards anything not yet sent. One limit worth stating precisely, as with crash reports above: if a batch is already being sent at the moment you turn the switch off, that batch finishes. Nothing after it is sent.

This website

movesesh.com is hosted on Cloudflare Pages. Cloudflare terminates the connection and keeps standard access logs, as any web host does. We have enabled no analytics product, set no tracking cookies, and embed no third party scripts, advertising, or social widgets on any page.

What we do not do

• No accounts, so no email address, password, or profile is collected.
• No advertising and no advertising identifiers.
• No behavioural profiling and no tracking across apps or sites. The app reports the closed list of events in Flow 4 and the crash diagnostics in Flow 3, and nothing beyond them.
• No selling or sharing of personal information. There is nothing to sell.

Children

Movesesh is not directed at children under 13, and because the app has no account system and collects no personal information, it does not knowingly collect anything from them.

Your data, your control

Because your training data never leaves your device except when you export it, you control it directly. Deleting the app removes its database from your phone. The Settings screen also offers a delete-my-data action that clears it without uninstalling, and an export so you can take it with you first.

Changes to this policy

This policy describes Movesesh as it exists today, not as it may exist later. If we add something that transmits data, such as an account system, this page gains a section describing it and the date above changes. We do not backdate.

Contact

Questions about this policy can go to support@movesesh.com.