Privacy Policy

Last updated 26 October 2026.

The short version

  • TDeWorks AB in Sweden runs Swole.fit and is responsible for your personal data.
  • We collect what we need to run the app: your email, the name or gym handle you choose, your training and your food log. Health data only if you agree.
  • We don't sell your data, show ads or work with data brokers.
  • The AI coach and most AI features run on Claude by Anthropic in the USA. Food photos go to Google's Gemini. The AI only sees your body data and pain ratings if you switch that on.
  • If you connect Withings, we import your scale and blood pressure readings. They never go to any AI.
  • If you import an Apple Health export, your device reads it and sends us only the workouts and body readings you pick.
  • Train in Public is off until you switch it on. What you post there is seen by the people you pick, and public posts by anyone. An AI safety check looks at every post, photo, clip and comment before anyone else sees it.
  • Analytics only run if you click Accept in the cookie banner.
  • You can get a copy of your data, delete your account in the app and withdraw consent at any time.

1. Who is responsible for your data

Swole.fit is run by TDeWorks AB in Sweden ("we", "us"). We decide why and how your personal data is used, which makes us the controller under the EU General Data Protection Regulation (GDPR).

Company
TDeWorks AB
Org. number
559551-8514
Address
Orrakullaliden 9, 438 94 Härryda, Sweden
Contact
Contact form

You can also reach us through our contact form.

2. What we collect and why

We only collect what we need to run Swole.fit. To use it you need to give us an email address and a name or gym handle; without them we can't create your account. Everything else you add is up to you.

Your account

What: Your email address, the name or gym handle you choose, when you accepted the terms and this policy, your experience level and your settings, such as units, time zone and weigh-in day.

Why: To create your account, log you in and keep you logged in.

Legal basis: Contract (Art. 6(1)(b) GDPR).

You log in with a 6-digit code we email you. There are no passwords and no third-party login provider. Codes are stored hashed, work for 10 minutes and allow 5 attempts, and we send at most 5 codes an hour.

Each login session also stores your IP address and browser user agent. We use them, and the limits on login codes, to keep accounts secure and stop abuse. The legal basis for that is our legitimate interest in security (Art. 6(1)(f) GDPR).

Your training

What: Your cycles, workouts, exercises, sets, weights, reps, reps in reserve, notes and check-in ratings (recovery, soreness, pump and workload), and your cardio sessions: activity, time, duration, distance, effort and calories.

Why: To log your training, plan your next sessions and show your progress.

Legal basis: Contract (Art. 6(1)(b) GDPR).

Body data, the heart rate you add to cardio sessions and joint pain ratings are health data and have their own rules: see Health data.

Your food log

What: The foods you log, how much you ate (amount, unit and grams) with its calories, protein, carbs, fat and fiber, which meal it was and when you ate it. Also the foods you create yourself: name, brand, serving size and nutrition values.

Why: To log what you eat, add up your day and week, and show it next to your training.

Legal basis: Contract (Art. 6(1)(b) GDPR).

Foods you create stay private to you. Nobody else can see them or find them in search. Your food preferences (country, food languages, allergies and foods you won't eat) and your saved meals and meal plans are stored with your account too.

Withings readings

What: If you connect a Withings account: the readings we import (weight, body composition, blood pressure and heart rate, with when each was measured), your Withings user ID, the permissions you gave us, when you agreed and to which version of the consent text, and the login keys Withings gives us, stored encrypted.

Why: To show your readings in your timeline and trends, use them for your calorie targets and keep new readings coming in.

Legal basis: Your explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR).

The details are under Connected devices.

Apple Health import

What: If you import an Apple Health export: the workouts you pick (activity, start, duration, distance, calories and average and maximum heart rate) and your weight, body fat, lean mass and waist readings, with when each was measured. Your device reads the file and leaves everything else in it, including your other health data and the names of your apps and devices, on the device. We don't keep the file.

Why: To show your past workouts and readings in your timeline, trends and stats, and use your weight for your calorie targets.

Legal basis: Your explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR), given on the import screen if you haven't given it yet. Undo the import in Settings, under Import, to delete what it added.

Train in Public

What: If you switch it on: your handle, avatar, bio, the posts, photos, videos, comments and reactions you share, who you follow and block, and reports you send. The date you confirmed you're 18 or older.

Why: To run Train in Public, the social side of the app.

Legal basis: Contract (Art. 6(1)(b) GDPR).

Who sees what is explained under Train in Public.

Messages to us

What: The name, email address, subject and message you send through the contact form.

Why: To answer you. Resend delivers contact-form messages to our inbox, which Google hosts (Gmail), and sends you a copy.

Legal basis: Our legitimate interest in answering your message (Art. 6(1)(f) GDPR).

The Beast Mode list

What: If you join the Beast Mode list: your user ID, or the email address you give us when you're not logged in, which page you joined from and when.

Why: To count who wants Beast Mode and tell you once when it opens. We send nothing else to that address, and we delete it when you ask.

Legal basis: Your consent, given with the box next to the email field (Art. 6(1)(a) GDPR), which you can withdraw any time through the contact form. For logged-in lifters: our legitimate interest in knowing who asked to hear about Beast Mode (Art. 6(1)(f) GDPR).

Feedback in the app

What: The type, title and messages you send under Feedback in the app, our answers, and the browser user agent of the device you sent it from.

Why: To answer you, chase down bugs and make the app better. Resend emails your feedback and your email address to our inbox (Gmail) and emails you when we answer.

Legal basis: Our legitimate interest in answering you and improving the service (Art. 6(1)(f) GDPR).

Coach tips and notifications

What: Which coach tips of the day you've seen, got as a notification or dismissed, and when. If you switch on coach tips as notifications: the push address and keys your browser gives us for that device.

Why: To show at most one coach tip a day, never bring back a tip you dismissed on any of your devices, and send the tip to the devices where you asked for it.

Legal basis: Contract (Art. 6(1)(b) GDPR). Notifications only start after you switch them on and allow them in your browser.

Logs and usage records

What: Server logs with your user ID and, when there's a problem with your login, sometimes your email address. Records of your AI use: token counts and cost.

Why: Logs help us run the service, fix errors and keep it secure. AI usage records let us apply the fair-use limits.

Legal basis: Our legitimate interest in a secure, working service with fair AI use (Art. 6(1)(f) GDPR).

How you found us

What: If you answer the optional question during setup: where you heard about us, such as YouTube, Reddit, a friend or an AI assistant. It's one tap and you can skip it.

Why: To count new signups per source each week, so we know where to keep showing up. We only look at totals, never at who said what.

Legal basis: Your consent (Art. 6(1)(a) GDPR), given by answering. It stays with your account until you ask us to clear it or delete your account.

The link you came in on

What: If you sign up after arriving through a tagged link or from another website: the link's utm tags (such as utm_source=youtube) and the name of the website that sent you (only its domain, like reddit.com, never the full address). Without your cookie consent we only carry this along in the page address while you log in, and store nothing on your device.

Why: To count which links and sites bring new lifters, next to what people tell us themselves. We only look at totals.

Legal basis: Our legitimate interest in knowing which of our links work (Art. 6(1)(f) GDPR). It stays with your account until you ask us to clear it or delete your account. Remembering it on your device for a later visit needs your consent, see Cookies and browser storage.

Analytics

What: How the app is used (page views and events) and how fast pages load, measured with Vercel Web Analytics and Speed Insights. Events contain no names or email addresses.

Why: To see what works and what to improve.

Legal basis: Your consent (Art. 6(1)(a) GDPR). Analytics only run after you click Accept in the cookie banner. See Cookies and browser storage.

3. Health data

Some of what you can log in Swole.fit is health data, a special category of personal data under Article 9 of the GDPR. It covers:

  • your bodyweight, body composition (body fat, muscle, water, bone and visceral fat) and tape measurements
  • your height, birth year and sex (sex is only used in the calorie formula)
  • your goal, pace and calorie and macro targets
  • the heart rate you add to cardio sessions
  • the weight, body composition, blood pressure and heart rate we import from Withings if you connect it
  • the weight, body composition, waist and workout heart rate you import from an Apple Health export
  • the joint pain ratings in workout check-ins
  • the progress photos you add on the Stats page

Why: to calculate your calorie and macro targets, show your progress and adjust your training.

Legal basis: your explicit consent (Art. 9(2)(a) and Art. 6(1)(a) GDPR). We ask for it with an "I agree" checkbox or button before we store your body data, progress photos, heart rate or pain ratings. Progress photos joined the list on 17 October 2026, so if you agreed before that, we ask again before your first photo.

It's optional. Your training works without it. Without your consent, we skip the pain question in check-ins and don't store heart rate. If you say no when a check-in asks, we also remove pain ratings and heart rates you logged before.

Notes are free text. They're stored with your training and the AI features read them (see AI features), so only write health details in a note if you're fine with that.

Withdraw any time in Settings, under Health data. We then disconnect Withings and delete your body data, progress photos, heart rates and pain ratings. Withdrawing doesn't affect what we did with your data before. You can also delete just your body data in Settings.

The AI coach only sees your body data and pain ratings if you also switch on "Coach can see health data". That's a second, separate consent. It's off by default, and you can switch it off any time in Settings or on the Stats page. The same switch decides whether the AI sees your calorie and macro targets, with no exceptions. AI meal plans need your targets, so they only run with the switch on; with it off, your meal plan is built in code without AI (see AI features). Readings imported from Withings never reach any AI feature, whatever that switch says. Workouts and readings imported from Apple Health follow the switch: the AI only sees them while it's on.

Progress photos are private. We store them in a private Vercel Blob store and show them only to you, through links that expire within an hour. Your device shrinks each photo before upload, which removes its location and camera details. Nobody else sees a progress photo unless you share it: each share is a separate Train in Public post with its own copy of the image, you choose whether it shows dates and weight, and unsharing deletes that post and its copy. Sharing one photo never changes the rest. The AI coach never sees your progress photos. Deleting a photo deletes it from our storage.

We never sell your health data or use it for ads.

4. AI features

Swole.fit has AI features you choose to use. To answer you, they send some of your data to AI providers. None of them gets your email address. This is what goes where.

Your switch

You decide whether any of this runs. In the Swole.fit app we ask before the coach's first answer, on a screen that lists who gets what. The "AI coach" switch, under More, Coach in the app and Settings, Coach on the web, turns every AI feature in this section off and back on. It's one setting for your account: switch it off in the app and it's off on the web too, and the other way round.

With it off, we send nothing about you to Anthropic, Google or TypeSafe AI: no chat, debriefs, recaps, coach lines or decisions, memory, meal names, food photos or AI meal plans (you get the plan we build in code instead). The one exception is the Train in Public safety check below. It runs on everything you post whatever the switch says, because it keeps everyone in Train in Public safe. If you never post, it never runs. We keep your choice, when you made it and whether it came from the app or the web, so we can show we asked.

Who runs the AI

Most features run on Claude, AI models made by Anthropic PBC (USA), through Anthropic's API. Under Anthropic's standard commercial terms, Anthropic doesn't use this data to train its models and keeps it for up to 30 days.

Three features go through Vercel AI Gateway, which we set to zero data retention: food photos and the safety check of Train in Public clips (Google's Gemini) and the small decisions the coach makes (TypeSafe AI's Jev model).

AI coach chat and workout debriefs

Answered by Anthropic's Claude. We send your name, your program (your cycle, upcoming and recent workouts, sets, weights, notes and check-in ratings), your cardio (activity, time, duration, distance and calories, never heart rate), your food log (foods, amounts, meals, times, calories and macros), the food allergies and foods you won't eat that you set, what the coach remembers about you and the chat, including anything you type. Your body data, calorie and macro targets and pain ratings are only included if "Coach can see health data" is on.

After a workout, the coach can open a debrief chat about it with the same information. When you ask, the coach looks up your cycle history and food log, and can change your plan or log things for you. We keep your coach chats in Swole.fit until you delete your account.

Coach memory

The coach saves short facts you tell it in chat (goals, schedule, equipment, how you eat, how you like to be coached) so it knows them next time. Anthropic's Claude Haiku checks each new fact against what the coach already knows and writes it down. Injuries and other health facts are only saved if "Coach can see health data" is on. You can see, edit and delete every memory under Settings, What your coach knows, or switch memory off there.

Timeline recaps

Short recaps on your timeline are written by Anthropic's Claude Haiku. We send your workout numbers, records and up to five exercise notes. Pain ratings are only included if "Coach can see health data" is on. Never your name.

Coach lines

When you log a set, food or cardio, the coach sometimes pops up with a short line. Some of these lines are written by Anthropic's Claude Haiku. We send what just happened: the exercise and how the set compares to your plan and your best, the food's name, calories and protein, or the cardio activity and minutes. How your day compares to your calorie and protein targets is only included if "Coach can see health data" is on. Never your name. You can turn the coach's lines down or off in Settings.

Meal names

When you save foods as a meal, Anthropic's Claude Haiku can suggest a name. We send the names of the foods and the meal's label. Nothing else.

Meal plans and swap ideas

AI meal plans only run if "Coach can see health data" is on, on the free plan and in Beast Mode alike. With the switch off, we build your plan in code on our own servers and send nothing to an AI provider. With it on, Anthropic's Claude writes the plan. We send your calorie and macro targets (a plan can't hit them otherwise), your plan settings, the food allergies you set, the plan you're building on, anything you type as instructions, and foods from our food catalog to pick from. For swap ideas, we send the meal you want to replace (its name, foods, calories and protein) and anything you type, never your targets. Never your body data, pain ratings or name.

Meals in your plan made only from foods in our food catalog may be saved, without your name, as suggestions for other people's meal plans in your country. Foods you created yourself are never shared.

Food photos

When you log food from a photo, the photo goes to Google's Gemini model to recognize the food and estimate how much is there. It goes through Vercel AI Gateway with zero data retention. We shrink the photo on your device first, which normally removes its location and camera details. We also send the note you add and the language of your food tables. We don't store the photo.

Coach decisions

TypeSafe AI's Jev model makes small decisions for the coach: when to show a tip or a line, which follow-ups to offer after a workout, which chat starters and progress views fit, which meal swaps fit and which supermarket aisle a food belongs in. It runs through Vercel AI Gateway with zero data retention. We send summarized set comparisons, the status of your week, exercise notes, the food or meal in question and the question being decided. How your day compares to your calorie and protein targets only if "Coach can see health data" is on. Never body data, pain ratings or your name.

Cycle builder chat

Also answered by Anthropic's Claude. We send your name, your experience level, the exercise list and the chat. It may ask about injuries, and whatever you answer is part of the chat. We don't store this chat.

Train in Public safety check

Before anyone else can see a Train in Public post, photo, clip or comment, an AI checks it against our community rules: no nudity or sexual content, nobody who looks under 18, no violence, self-harm, hate, harassment or body shaming, no drug dealing and no spam. Text and photos go to Anthropic's Claude Haiku. Clips, and photos too large for Claude, go to Google's Gemini through Vercel AI Gateway with zero data retention. We send only what you posted, never your name or email address, and we keep the result (cleared, or the rules it may break) with the post.

If the check flags something, or can't run, the post or comment stays visible only to you until one of our staff looks at it. The AI never deletes anything: a person approves it or takes it down. Your private progress photos are never checked unless you share them in a post. The check doesn't count towards your AI allowance.

Legal basis: our legitimate interest in keeping Train in Public safe for everyone in it and meeting the app store rules for user content (Art. 6(1)(f) GDPR).

Legal basis: contract (Art. 6(1)(b) GDPR), because these are features you choose to use. Your body data, calorie and macro targets and pain ratings only go to the AI with your separate explicit consent (Art. 9(2)(a) GDPR).

Fair use. AI features count towards a monthly AI allowance. Some, such as food photos and swap ideas, are part of Beast Mode.

AI can be wrong. Answers are generated automatically, so check anything important and don't treat them as medical advice. We don't make decisions about you based solely on automated processing that have legal or similarly significant effects (Art. 22 GDPR).

5. Train in Public

Train in Public is the social side of Swole.fit. It's off until you switch it on, and it's only for adults: you confirm you're 18 or older with your birth date, which we check and don't store.

  • Your profile shows your name or handle, avatar, bio and follower counts to anyone with the link, including people who aren't logged in. Your badges and training stats (total workouts, when you started and how many posts) only show if you switch them on.
  • Your posts can share a workout (exercises, sets, weights, reps, records, volume, duration and muscles), a week, an achievement, a note or photos and videos, with an optional caption. Posts never include your body data, heart rate, pain ratings or food log.
  • You pick the audience for each post. Public posts and their comments can be seen by anyone, including people who aren't logged in, and show up in Discover. Followers-only posts are seen by your followers. Anyone using Train in Public can follow you without asking; you can block people.
  • Comments and reactions you leave are seen by everyone who can see the post. Reports you send come to our staff, who can dismiss them or take the post, comment or profile down. The person you report never sees who reported them.
  • Safety check: an AI checks every post, photo, clip and comment before others see it (see AI features).
  • Photos and videos are stored privately with Vercel Blob and shown through links that expire within an hour. Before upload, your device removes location and camera details from them.
  • Profile and post pages tell search engines not to index them. A link you share yourself can show a preview of a public post.

Delete a post and we delete its photos and videos too. You can switch Train in Public off any time.

Invites

Links you share carry your invite code, which is your Train in Public handle. When someone opens one, we remember the code in a cookie for 30 days. If they create an account in that time and finish their first workout, you both get a week of Beast Mode. You then see their first name, and they see yours. We keep who invited whom while both accounts exist.

6. Connected devices (Withings)

You can connect a Withings account (Withings SA, France) in Settings, under Connections, to bring in readings from your scale or blood pressure cuff. Withings is a source of your data, not a provider we use: you link your own account, Withings looks after the data in it under its own privacy policy, and we only read from it. We never write anything back.

  • What we import: weight, body composition (fat, muscle, water and bone), blood pressure and heart rate, with when each was measured. When you connect, we pull in up to two years of history.
  • What we store: those readings, your Withings user ID, the permissions you gave us and the login keys Withings gives us, which we store encrypted.
  • Your consent: these readings are health data. Before we send you to Withings, you tick a box agreeing that we import and store them. That's your explicit consent (Art. 9(2)(a) GDPR). If you haven't given health data consent yet, you give it in the same step.
  • Never sent to AI: Withings doesn't allow its data to go to AI. Readings from Withings never go to the AI coach or any other AI feature, even with "Coach can see health data" on. Neither do numbers we work out from them: the calorie targets and calorie burn the AI sees, including for meal plans, and the calorie estimates for your cardio only use weights you logged yourself. If all your weigh-ins come from Withings, cardio sessions get no calorie estimate until you log a weight or type the calories in.
  • What Withings gets from us: you log in at Withings yourself, and we tell Withings where to let us know about new readings. We don't send Withings anything else about you.
  • Disconnect any time in Settings, under Connections. We give back our access at Withings, delete the login keys and ask whether to keep or delete the readings we imported. The numbers you typed yourself stay either way.
  • Deleting your Withings account deletes them too: Withings tells us, and we delete the connection and every reading we imported from it. If you only unlink Swole.fit on the Withings side, we stop syncing until you reconnect or disconnect.
  • Withdrawing your health data consent or deleting your Swole.fit account disconnects Withings and deletes the readings.
  • Your export includes the readings, marked Withings, and the details of the connection: when you agreed, the permissions and the last sync.

7. Who we share data with

We use these providers to run Swole.fit. They process data on our behalf:

  • Vercel Inc. (USA): hosting, storage for progress photos and Train in Public photos and videos (Vercel Blob), analytics (only with your consent) and the AI Gateway.
  • Neon Inc. (USA): database hosting.
  • Resend (USA): email, such as login codes and contact-form messages.
  • Anthropic PBC (USA): the AI coach, debriefs, coach memory, timeline recaps, coach lines, meal names, meal plans, swap ideas, the cycle builder and the Train in Public safety check.
  • Google (USA): Gemini for food photos and the safety check of Train in Public clips, reached through Vercel AI Gateway, and Gmail for the inbox that receives contact-form messages and feedback.
  • TypeSafe AI: the Jev model that makes the coach's small decisions, reached through Vercel AI Gateway.

Withings isn't on this list: it doesn't process data for us, it's a source you connect yourself (see Connected devices).

Other people only see what you share in Train in Public. We don't sell your data, show ads or work with data brokers.

If you switch on coach tips as notifications, your browser's push service delivers them: Google for Chrome, Apple for Safari, Mozilla for Firefox and Microsoft for Edge. We encrypt each message before it leaves our server, so the push service can't read it. It sees your device's push address and when a message goes out.

Transfers outside the EU

Most of these providers are US companies, so your data may be processed in the USA. These transfers rely on the EU-US Data Privacy Framework where the provider is certified under it, and otherwise on the EU Standard Contractual Clauses. Ask us through the contact form if you want details or a copy of the safeguards.

8. How long we keep data

  • Your account and its data: until you delete your account. You can do that any time in the app under More, Delete account. Deletion is immediate and removes your data from our database, and your progress photos and Train in Public photos and videos from our storage.
  • Login sessions: 30 days, renewed each day you use the app.
  • Login codes: 10 minutes.
  • Body data: until you delete it, withdraw your health data consent or delete your account.
  • Withings readings: until you delete them when you disconnect, delete your body data, withdraw your health data consent, delete your Withings account or delete your Swole.fit account. The login keys go as soon as you disconnect.
  • Pain ratings and heart rates: until you withdraw your health data consent, say no when a check-in asks for it, or delete your account.
  • Coach chats and AI usage records: until you delete your account.
  • Coach memories: until you delete them, they expire (temporary facts like a trip), or you delete your account.
  • Meal plans: until you delete them or your account. Meals saved as suggestions for others (see AI features) carry no name and stay after that.
  • Progress photos: until you delete them, withdraw your health data consent or delete your account.
  • Food photos: not stored. They're gone once the food is recognized.
  • Train in Public posts, comments, reactions, photos and videos: until you delete them or your account.
  • Messages to us: as long as we need them to handle your request.
  • Feedback in the app: until you delete your account.
  • Coach tip records and push addresses: until you delete your account. A push address goes as soon as you switch notifications off on that device, or when your browser tells us it no longer works.
  • Server logs: a limited period, set by our hosting provider.

Copies in our providers' backups and logs are deleted on their own schedules.

9. Cookies and browser storage

Everything here is first-party: set by Swole.fit itself. We don't use advertising cookies or third-party tracking cookies.

Necessary cookies

These keep the app working, so they don't need your consent.

  • better-auth.session_token30 days

    Keeps you logged in.

  • better-auth.session_data5 minutes

    A short-lived copy of your login session, so the app doesn't have to look it up on every request.

  • swole-coach-signalUntil midnight

    Remembers today's coach tip.

  • swole-coach-dismissed90 days

    Remembers the coach tips you dismissed.

  • swolefit-analytics1 year

    Remembers that you accepted analytics. Only set after you click Accept.

  • swole_invite30 days

    Remembers whose invite link you opened, so you both get your week of Beast Mode when you join. Only set when you open an invite link.

  • swole_crew_invite1 day

    Remembers the crew invite you opened, so you land back on it after signing up. Only set when you open a crew invite link, and cleared when you join.

  • NEXT_LOCALE1 year

    Remembers your language.

On HTTPS, the names of the two login cookies start with __Secure-.

Browser storage

We keep your cookie choice (for 1 year) and app preferences, such as theme, workout view, timers and timeline and body prompts, in your browser's local storage, under keys that start with swolefit:, plus your theme under theme.

While a tab is open, its session storage can hold a comment you started before joining Train in Public and whether we already matched the app's language to yours. It's cleared when you close the tab.

A service worker keeps a copy of app pages on your device for up to 30 days so the app works offline. That copy is cleared when you log out.

Analytics (optional)

Vercel Web Analytics and Speed Insights only run after you click Accept in the cookie banner. Events contain no names or email addresses. Legal basis: your consent (Art. 6(1)(a) GDPR).

Also only after you click Accept, the first-party cookie swole_attribution keeps the utm tags and referring domain of your first visit for 30 days, so they still count if you sign up later. Click Reject and it's deleted.

Change your choice any time: . You'll also find Cookie settings in the footer of our homepage and in the app under More.

You can also block or delete cookies in your browser settings, but without the necessary cookies you can't log in.

10. Your rights

Under the GDPR you have the right to:

  • Access your data and get a copy of it.
  • Correct data that's wrong. You can edit most of it yourself in the app.
  • Delete your data. Delete your account any time under More, Delete account, or ask us to delete specific data.
  • Restrict how we use your data, for example while we check whether it's correct.
  • Take your data with you (data portability). You can export your workouts, cardio, food log, body data (including readings from Withings), crews, Train in Public posts and comments, and the details of your progress photos as a spreadsheet under More, with your full history on every plan. Your progress photos and the photos and clips you posted download there as one zip file. For a full copy of all your data, send us a message.
  • Object to processing based on our legitimate interests.
  • Withdraw consent at any time, without affecting processing before that: health data in Settings, under Health data; Withings by disconnecting it under Connections; the coach's access with the "Coach can see health data" switch; analytics with Cookie settings.
  • Complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY) at imy.se, or to the data protection authority where you live or work.

To use your rights, send us a message through the contact form or Feedback in the app. It's free, and we answer within one month.

11. Children

Swole.fit isn't for children under 13. If you're 13 to 17, you need a parent's or guardian's permission to use it (see our Terms of Service), and you only get maintenance calorie targets: no cut or bulk.

Train in Public is only for adults (18 or older). If we learn that a child under 13 has signed up, we delete the account.

12. Changes to this policy

When we change this policy, we update the date at the top. If a change significantly affects how we use your data, we'll tell you in the app or by email before it applies, and ask for your consent again where that's needed.

13. Contact us

Questions about this policy or your data? Use our contact form, or Feedback in the app when you're logged in.

Read Terms of Service