Version 1.5.0 · Last updated 2026-09-18

sesh - Privacy Policy Supplement

Effective Date: September 18, 2026 Last Updated: October 15, 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 an offline-only workout tracker. All of your workout data — exercises, sets, reps, weights, durations, routines, and any notes you add — is stored locally on your device and never leaves it. We do not operate a server, we do not run analytics on your workout content, and we do not have a copy of your data anywhere.

Two outbound data flows leave your device, both narrow and disclosed in detail below:

2. Data Collection

2.1 What You Provide

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

We never see, transmit, 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 refuse consent, sesh does not request an ad at all and simply shows no banner. 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 if you were shown a consent form in the first place, so you will not see it if you are outside 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:

App stability sessions. Separately from error reports, the Sentry SDK records an anonymous 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, when the session started and how long it lasted, and whether it ended normally or in a crash. Sessions carry no advertising identifier, no IP address, no location, and none of your workout content, and are never linked to your identity or used to track you across apps or websites.

Sentry data is retained per Sentry's data retention policy and 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.

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. If you install sesh on a second device, you will start fresh on that device. 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. Anonymous app-stability sessions are enabled and are described in Section 2.4: they carry no identifiers, no IP address, and no workout content. 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 does not currently offer a built-in data export. Because the data lives only on your device, you cannot lose it to a server outage — but you also cannot retrieve it if your device is lost. Back up your device using its native backup system (iCloud Backup, Google One Backup) to preserve your sesh data.

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 not directed to children under 13 and we do not knowingly collect any personal information from children under 13. AdMob is configured with "treat as child-directed" set to No, meaning sesh is not designated as a child-directed app under COPPA. Parents who believe their child under 13 is using sesh should uninstall the app, which removes all local data.

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. 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 there is nothing for such a request to act on: we hold no copy of your data, we operate no server and sesh has no account. You delete your workout data yourself, in the app or by uninstalling (Section 5.1), and the ad data Google holds is managed by you at adssettings.google.com.

10. Changes to This Supplement

If we materially change how sesh collects or uses data, we will bump the version of this document and update the Last Updated date. Continued use of sesh after a change indicates acceptance of the revised supplement.

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.