Version 1.5.4 · Effective September 18, 2026 · Last updated November 8, 2026

Read with the WagDev Privacy Policy, General Terms of Service and Data Security Standards.

sesh Privacy Policy Supplement

Effective Date: September 18, 2026 Last Updated: November 8, 2026

This Privacy Policy Supplement is specific to sesh and supplements WagDev LLC's general Privacy Policy and Data Security Standards.

1. Summary

sesh is a no-account, local workout tracker. All of your workout data (exercises, sets, reps, weights, durations, and routines) is stored on your device, and we never receive it. Copies leave the device only when you choose to export them or your own device backup includes them. We do not operate a server, we do not run analytics on your workout content, and we do not have a copy of your workout data anywhere.

A few limited flows of technical data leave your phone. None of them includes your workouts:

2. Data Collection

2.1 What You Provide

All of the following is stored on your device via local SQLite storage:

We never receive or store any of this data on our infrastructure.

2.2 What sesh Does Not Collect

2.3 Advertising: What AdMob Collects on Google's Behalf

sesh is supported by advertising. You see a single banner strip anchored above the tab bar. It never covers your workout content and never appears over a dialog or modal.

When sesh requests an ad, the embedded Google Mobile Ads SDK collects the following on Google's behalf, for ad serving, measurement and fraud prevention (never your workout content):

Consent in the EEA, the UK and Switzerland. If you are in the European Economic Area, the United Kingdom or Switzerland, sesh presents Google's User Messaging Platform consent form before it requests a single ad. Nothing is requested from AdMob until you have answered it. This applies even when ads are non-personalized: serving any ad at all still involves storing or reading information on your device, so the form is shown either way, and choosing non-personalized narrows what is used rather than skipping the question. If you decline, sesh may still request a banner, but Google will serve only a limited ad: no personalization, and no use of cookies or device identifiers except, where enabled, to detect invalid traffic. Your IP address is still used to deliver it. Sometimes no ad is shown at all. Users outside these regions are never shown a consent form.

Changing or withdrawing your consent. Your answer is not final. Open Settings, then tap Privacy options, to bring the same consent form back up whenever you like: change any choice, or withdraw your consent entirely. A withdrawal takes effect on the next ad request. The Privacy options row appears only where Google's consent tools require it, which today means the EEA, the UK and Switzerland.

Ad personalization. On Android, ads may be personalized, subject to your consent answer and to your system Ad ID settings. sesh never asks for tracking permission on iOS. There is no App Tracking Transparency prompt, so the advertising identifier stays unavailable to the ad SDK and your ads on iOS are non-personalized. Nothing you do can change that, and there is nothing for you to decline.

Removing ads. sesh offers a one-time in-app purchase that removes advertising permanently. sesh has no account, so the purchase is tied to your App Store or Google Play account rather than to anything we hold: if you reinstall, or move to a new device, use Restore purchase in Settings to bring it back. Once ads are removed, sesh stops requesting ads and the AdMob SDK collects nothing further.

The full disclosure of AdMob data practices appears in Section 4.3 ("Advertising in Some Apps") of the WagDev Privacy Policy, which is incorporated here by reference. Your AdMob data is governed by Google's privacy policy.

2.4 What Sentry Collects for Crash and Error Reporting

To diagnose and fix bugs, sesh integrates Sentry, a crash and error reporting service operated by Functional Software, Inc. (d/b/a Sentry).

When the app encounters a runtime error or crash, the Sentry SDK transmits:

What Sentry does not receive from sesh:

IP address and approximate location. Like any internet service, Sentry sees your IP address when a report or session reaches it. We have set Sentry not to store that address. Sentry still uses it on arrival to estimate your approximate location (city, region and country) and stores that estimate with error reports. We use it only to diagnose problems, and sesh requests no location permission of its own.

App stability sessions. Separately from error reports, the Sentry SDK records a session each time you open and close the app, so we can measure how stable each release is and whether the app is being used at all. A session contains only: the app version, the device model and operating system version, the random installation identifier described above, when the session started and how long it lasted, and whether it ended normally or in a crash. The installation identifier lets us count how many installs a problem affects, and a reinstall replaces it. Sessions carry no advertising identifier, no location, and none of your workout content, Sentry sees your IP address when one arrives as described above, and sessions are never linked to your identity or used to track you across apps or websites.

Reports are deleted after 30 days. Sentry data is governed by Sentry's privacy policy. The full disclosure of how WagDev uses Sentry across apps appears in Section 4.2 ("Service Providers") of the WagDev Privacy Policy.

2.5 Other Services

3. How sesh Uses Your Data

3.1 Local Use Only

Your workout data is used solely to power the app's features on your device:

No remote processing, no machine learning on your content, no human review.

3.2 No Cross-Device Sync

Because sesh does not have a server, your data does not sync between devices. On a new device, you start fresh unless you import an export you made. If you delete and reinstall sesh on the same device, your local data will be erased (see Section 5 below).

4. Data Sharing

4.1 We Do Not Share Your Workout Data

4.2 AdMob Receives Only Ad-Serving Data

AdMob receives only the data categories listed in Section 2.3 above. It does not receive your workout data, custom exercise names, routine names, or any content you create.

4.3 Sentry Receives Only Diagnostic Data

Sentry receives only the data categories listed in Section 2.4 above. Our SDK configuration explicitly disables PII collection, performance traces, and session replay, and scrubs breadcrumbs that originate from user-typed content. App-stability sessions are enabled and are described in Section 2.4: they carry a random installation identifier, no advertising identifier, and no workout content. Section 2.4 explains how Sentry handles your IP address and approximate location. Sentry receives no workout data of any kind.

5. Your Privacy Controls

5.1 On-Device Controls

Because all data is local to your device, you have direct control:

5.2 Advertising Controls

5.3 Data Export

sesh offers a full export in Settings → Your data, which you can keep somewhere safe and import on a new phone. Because the data lives on your device, you cannot lose it to a server outage, but we cannot retrieve it if your device is lost. On iPhone, iCloud and computer backups can include your sesh data. On Android, Google device backup does not include it, so use the export.

6. Data Retention

6.1 As Long As You Have the App

Your workout data is retained on your device for as long as you have sesh installed and your device's storage permits. We do not impose any time-based retention limits because we never receive your data.

6.2 After Uninstall

7. Children's Privacy

sesh is made for adults and is not directed to children. You must be at least 18 to use it. sesh has no accounts and does not ask your age. It does not mark its ad requests as child-directed, because it is not made for children. If you believe a child has used sesh, deleting the app removes all of its data from the device, and you can contact privacy@wag.dev.

8. Security

8.1 On-Device Security

Your sesh data is stored using Apple's and Google's standard application sandboxing. It is not encrypted by sesh beyond what the operating system provides at rest. We rely on:

Because sesh has no network sync, there are no transit-layer security concerns for your workout data.

8.2 AdMob Security

Data sent to AdMob is encrypted in transit using TLS by the Google Mobile Ads SDK.

9. Compliance Notes

9.1 Apple App Privacy Details

The following data types are declared in sesh's App Store privacy nutrition labels:

Nothing is declared as used for tracking, so sesh's App Store product page carries no "Data Used to Track You" section. sesh presents no App Tracking Transparency prompt, so the advertising identifier is never available to the ad SDK on iOS and your app data is never combined with third-party data for targeted advertising or measurement.

"Linked to you" describes linkage to a persistent advertising identifier held by Google, not to any account with us: sesh has no accounts. No data from your workout content is declared, because no workout content is collected.

9.2 Google Play Data Safety

The Google Play Data Safety section declares the same AdMob categories above, as Device or other IDs, Location → Approximate location and App activity → App interactions, each collected and shared with Google for advertising, analytics and fraud prevention. Sentry data is declared as App info and performance → Crash logs and → Diagnostics, not linked to a user, and the Approximate location row also covers Sentry's IP-derived estimate, for app functionality. Both AdMob and Sentry traffic carries the "Data is encrypted in transit" affirmation.

sesh does not claim a "Users can request that their data be deleted" affirmation, because we hold no copy of your workouts and no account for you, so you delete your workouts yourself, in the app or by deleting it (Section 5.1). We do hold crash reports in Sentry, which are deleted after 30 days and are not linked to your name or email. If you want them deleted sooner, email privacy@wag.dev and we will delete any reports we can match to an identifier you give us. You can review Google's ad settings at My Ad Center.

10. Changes to This Supplement

We will update the version and Last Updated date for every change. If we materially change how sesh collects or uses data, we will tell you in the app before the change takes effect, and we will not apply a new use to data collected earlier without your consent.

11. Privacy Contact

For sesh privacy questions:

For urgent privacy concerns:

This Privacy Policy Supplement should be read together with WagDev LLC's general Privacy Policy and Data Security Standards for a complete understanding of our privacy practices.