Privacy Policy

The short version

Sadan keeps your training records on your own device. There are no accounts, no sign-in, and no copy of your training history on our servers. We cannot see what you lift.

Three optional features send data off your device, and each is separately controlled and off until you turn it on:

If you use none of them, nothing about your training leaves your device.

This page describes all of it in detail. If anything here is unclear, write to support@wapniaklabs.com and we will explain it.

1. Who we are

Sadan is made by Wapniak Labs LLC, a South Carolina limited liability company, 505 Ventura Pl, Mount Pleasant, SC 29464, United States.

For any question about this policy or your data: support@wapniaklabs.com.

For the purposes of the UK and EU General Data Protection Regulation, Wapniak Labs LLC is the controller of the personal data described here.

2. What Sadan records on your device

Sadan is a training log. On your device it records:

• Your training — the movements you perform, the weight, the repetitions, how many sets, and how hard each movement felt.
• How your training is organised — the days you have built, the movements in them, the order, and your current training phase.
• A name — whatever you enter at setup. It can be anything; it is not verified and it is not an account.
• Where you train — a name you type for each gym, such as “Crunch Union St”. This is a label you write. Sadan does not use your device’s location, does not request location permission, and records no coordinates of any kind.
• Injuries and constraints, if you record them — a body area, a status, and any rule you write for yourself, such as what to avoid or what to work around.
• Notes, if you write them — about a session, a movement, or how you felt.
• Cardio, if you log it.

All of this is stored in your device’s own storage. We hold no server-side copy, and there is no account to attach it to. If you delete the app or clear its data, that record is gone — including from us, because we never had it.

3. What leaves your device, and when

There are exactly two network destinations. Nothing else in the app sends anything anywhere.

Sadan contains no analytics, no telemetry, no crash reporting, no advertising network, and no tracking of any kind. We do not know how many times you open the app, which screens you use, or whether you use it at all.

3a. The AI coach — off unless you turn it on

If you enable the AI coach, then each time you finish a session Sadan sends a written summary of that session, through a server we operate, to Anthropic PBC, which processes it and returns written feedback to your device.

What the summary contains:

• The name you entered.
• Your injury flags, by name — and, for any active constraint, the rule you wrote for it, in your own words.
• Any open discomfort threads you have recorded — the movements involved, their status, and the dates.
• Your training phase.
• The gym name you entered for each session included.
• Every set of the finished session: weight, repetitions, whether a target was missed, which side, and whether it was a warm-up.
• The same for up to three previous sessions of the same day type, and any cardio recorded in that window.
• Your structured session context, if you filled it in — sleep, energy, stress, nutrition, hydration.

What the notes setting does, and does not do. Sadan has a separate control for whether your written notes are included. Turning it off removes the free text you typed about a session, a cardio entry, or a discomfort thread. It removes nothing else. Your name, your injury flags, the rules you wrote for them, your gym names, your training phase, and every set you logged are still sent. It is a notes setting, not an anonymiser, and we would rather say so plainly than let the name imply more than it does.

What happens to it at Anthropic. Data sent through Sadan’s AI coach is processed under Anthropic’s commercial API terms. Under those terms Anthropic does not use it to train its models, and API inputs and outputs are deleted automatically after a short retention window, subject to Anthropic’s own abuse monitoring and legal obligations. Anthropic’s terms govern this, not ours, and they can change — read them at anthropic.com/legal.

What our own server keeps: nothing. The server that passes your summary to Anthropic writes nothing to any database, because there is no database. It holds a short-lived count of requests in memory to limit abuse, which disappears when the server restarts. It does not log the content of what you send or what comes back. Our hosting provider, Netlify, may retain ordinary request metadata such as IP addresses and timestamps under its own terms, which we do not control.

Feedback from the AI coach is generated by a machine. It can be wrong. It is not medical advice and it is not a diagnosis. Treat it as a suggestion from software, and consult a qualified professional about any injury, pain, or medical question.

3b. Strava — off unless you connect it

If you connect your Strava account, every session you finish afterwards is posted to Strava automatically. There is no per-workout prompt. Connecting is a standing authorization that applies to everything you log from that point on, until you disconnect.

Each post contains six things: the session’s title, the activity type (“weight training”), the start time, the elapsed duration, a marker indicating indoor training, and a description listing the movements you performed with their sets, plus session totals and the words “via Sadan”.

It contains none of the following, and an automated test that deliberately plants each of them runs on every build to keep it that way: your notes, your effort ratings, your injury information, your gym name, your training phase, or anything the AI coach wrote.

Who can see it. The activity is posted to your Strava account and takes your Strava account’s default visibility. Strava documents that default for adult accounts as “Everyone” unless you have changed it. Strava’s API provides no way for Sadan to set the visibility of a post, so Sadan cannot make a post private. If you do not want your workouts publicly visible, change your default privacy settings at Strava before connecting.

What Sadan can do with your Strava account. Sadan requests one permission: activity:write. Strava describes this as permitting the creation of manual activities and the editing of activities visible to the app. Sadan uses it only to create one activity when you finish a workout. It never edits and never reads. Reading your Strava activities would require a different permission, which Sadan does not request. You can review and revoke exactly what you granted at strava.com/settings/apps.

Where your Strava credentials live. On your device. When you connect, your authorization passes through our server once, in memory, to exchange it for access tokens; we forward only the tokens to your device and keep none of it. Strava sends profile information alongside those tokens — your Strava ID, name, city, country, and photos — and our server discards all of it rather than passing it on. Your Strava tokens are excluded from Sadan’s backup files, so a backup never carries your credentials.

Disconnecting deletes the stored credentials from your device and asks Strava to revoke the app’s access. It does not remove activities already posted — those are yours, in your Strava account, and yours to delete there.

Strava is an independent company and an independent data controller for anything in your Strava account. Their handling of it is governed by their privacy policy, not ours. Strava also collects usage data about the API calls that applications like Sadan make.

3c. Sharing an image of a session

Sadan can generate an image summarising a finished session. The image is made on your device and contains training figures only. It goes nowhere unless you share it, and where you share it is your choice.

3d. Sending your data to someone else

Sadan can export a complete copy of your training records as a file, which you can send to anyone you choose, including a coach.

That copy contains everything Sadan holds, including any injuries and notes you have recorded. Once you send it, the person who receives it has their own copy on their own device. We have no control over what they do with it, and this policy does not govern them. Your Strava credentials are the one thing excluded from an export.

4. Why we process what we process

Each optional feature is off until you turn it on, and you can turn any of them off at any time in Settings. Withdrawing consent stops future processing; it does not undo something already sent.

5. Who else receives data

• Anthropic PBC — processes AI coach summaries and returns feedback. United States.
• Strava, Inc. — receives posted activities if you connect it. United States. An independent controller, not our processor.
• Netlify — hosts the small server functions the two features above pass through. May retain ordinary request metadata under its own terms.
• Anyone you send an export to — because you sent it.

We do not sell your data. We never have and we do not intend to. We do not share it for advertising, we run no advertising, and we do not use your training data for any purpose other than running the features you have turned on.

6. International transfers

Wapniak Labs LLC is in the United States, and the two services described above are United States companies. If you use Sadan from outside the United States and enable those features, the data described goes to the United States.

7. How long anything is kept

• On your device: for as long as you keep it. You can delete individual records in the app, or all of it by deleting the app or clearing its data.
• On our servers: nothing is kept. There is no database and no stored copy.
• At Anthropic: for their retention window under their commercial terms.
• At Strava: in your Strava account, until you delete the activity there.

If you revoke Sadan’s access at Strava, we will delete any related data under our control within 30 days. Because Strava credentials are stored on your device rather than on our servers, the practical effect of revoking at Strava is that those credentials stop working; deleting them from your device happens when you disconnect in Settings or delete the app.

8. Your rights and how to use them

You do not need an account to exercise any right, because there are no accounts.

The most direct route is the app itself. Your data is on your device: you can read it, edit it, export it, and delete it without asking us, because we are not holding it.

You also have the right to ask us for access to any personal data we hold about you, to have it corrected or deleted, to restrict or object to processing, to receive it in a portable form, and to withdraw consent at any time. Write to support@wapniaklabs.com. We will respond within 30 days. In most cases the honest answer will be that we hold nothing, because we do not.

If you are in the UK or the EU you have the right to complain to your data protection authority. If you are in California, Colorado, Connecticut, Virginia, or another state with a consumer privacy law, you have rights under it, including the right not to be discriminated against for exercising them — and we do not discriminate.

If you record injuries, discomfort, or pain, that may be “consumer health data” under the laws of Washington, Nevada, and Connecticut. How Sadan handles it is described in a separate document: the Consumer Health Data Privacy Policy at wapniaklabs.com/health-data-privacy.

9. Children

Sadan is not directed to children under 13, and we do not knowingly collect personal information from them. We hold no server-side data at all, so there is nothing for us to collect. If you believe a child has been using the app and you want something addressed, write to support@wapniaklabs.com.

10. Security

Your training records are protected by your device’s own security — its lock screen, its encryption, and its app sandboxing. Keep your device locked and up to date; that is the strongest protection for data that lives only there.

The two network paths use encrypted connections. Access to the AI coach requires a code we issue, which is stored hashed rather than in plain text.

Because we hold no database of user data, there is no central store of training records to breach.

11. Changes

If we change what leaves your device, we will update this page and change the date at the top. Material changes to what the optional features send will be announced in the app, and where the law requires fresh consent we will ask for it rather than assume it.

12. Contact