Privacy Policy

AdimFit stores what you tell it about your training so your coach can give advice built on your own history. Your training log is visible to you alone, unless you yourself connect a trainer, gym or health plan to it — which you are asked about once, by name, with the exact list of what they would see, and can undo in one tap. Your employer never sees it, with or without your agreement. We do not sell your data, we do not show advertising, and you can delete everything at any time.

This page explains the detail. It applies to AdimFit, operated by Lush Techdia of 28 Adetola Street, Aguda, Surulere, Lagos, Nigeria (“we”, “us”).

You, and nobody else — unless you decide otherwise about one specific trainer, gym or health plan. Your workout log, your coach conversations and your training profile are visible to your own account only. The single exception is a connection you open yourself, to one named organisation or person who already has a relationship with you, after being shown the exact list of what they would see. This is stated here plainly rather than left to be inferred, because it is the promise the rest of this page exists to support.

• Your employer can never see what you logged. Not with your agreement and not without it, and this one is not an exception you can waive. Consent given to an employer is not treated as freely given — the power imbalance in an employment relationship is why — so there is no version of this where you can opt in, and we do not offer one. Where an employer pays for accounts it receives aggregate figures only: enrolment, the share active each month, totals and averages, and department rollups suppressed below ten people so an individual cannot be worked out by subtraction. The indirect route is closed too: if you connect a health plan your employer arranged, what you share reaches the health plan and not your employer, and that is a term of our contract with them.
• A trainer, gym or health plan can see your training — only if you connect them yourself. This is the only exception on this page, and it works the same way in all three cases. If one of them already has a relationship with you — a trainer whose link you joined through, a gym or a health plan that has you on its member list — you are asked once whether to connect. The question lists exactly what they would see and what they would not, before you answer. Saying no is final and we do not ask again. You can end a connection at any time from your profile and it takes effect immediately.
• Each of them sees a different, narrow slice — never all of it. A trainer sees the name you choose, which days you logged, what you logged including sets and reps, and your goal, training location and equipment — they cannot set your sessions without it. A gym sees only the name you choose, which days you trained and how many minutes a week that adds up to; not your sets, not your goal. A health plan sees your training days, your weekly minutes, whether each month met a 150-minutes-a-week mark, and the enrollee number you enter so they can match you to your own record; not what you actually did. None of them ever sees your email address, your weight, your height, your body measurements, your blood pressure, or anything you say to your AI coach — there is no setting that shares those.
• What you log is what they see, and we do not verify it. AdimFit reads no watch, no step counter and no health app, so everything a connected trainer, gym or health plan sees is what you typed. We describe it to them that way. Where a health plan counts your activity towards a reward, it is counting self-reported activity and we tell them so in the data itself.
• Referral partners who are not coaching you see counts, not people. A trainer or creator who refers members sees how many people followed their link, how many created an account, how many subscribed, and what they have earned. Unless you have connected to them as described above, they do not see who those people are and they never see a training log — no name, no email address, no session.
• A sponsored account is still a private account. Where an organisation pays for accounts, it receives aggregate figures across the group and nothing else. Nothing in the product reports one named person's training to whoever is paying for it.

Three ordinary limits apply on top of that, and they are the same ones that apply to any service that stores anything. The providers listed under Who else processes it handle data on our instructions in order to make the product work. Our own staff can reach stored data where operating the service requires it — investigating a fault you report, for example — and we keep that access to what the task needs. And we would comply with a valid legal demand, as we are obliged to. None of the three is a route by which an employer or a gym sees your sessions.

Nothing here is enforced and nothing is checked — we have no way to check it, which is exactly why it is worth explaining rather than demanding.

• Your coach programs from the log and nothing else. It reads your last sessions and prescribes against them, so an entry that flatters you comes back as a session you are not ready for — and then as a week you miss.
• Progressive overload is arithmetic. Adding weight to a lift depends on knowing what you actually lifted last time. Wrong numbers in, wrong weight on the bar.
• A blank day is more useful to us than a filled-in one. The coach is built to pick up after a gap without making a thing of it. It cannot work around a gap it was told did not happen.
• Where you have connected a trainer, gym or health plan, what you logged is all they see. We have no watch or sensor to check it against and we do not claim to — which is exactly why a false entry misleads the one person trying to help you, and nobody else.

There is no penalty for a gap, a short session or a week off. The product is built on the assumption that real weeks are interrupted, and the log is more useful to you when it says so.

Only what the product needs to function:

• Account details — your email address, and your name and profile photo if you sign in with Google.
• Training profile — first name, age, weight, your goal, preferred activities, and optionally where you train and what equipment you have.
• Workout log — the sessions you record: activity, date, duration, intensity, and any notes you write.
• Coach conversations — the messages you exchange with the AI coach, and any training plans it produces.
• Technical data — standard server logs (IP address, browser type, timestamps) generated when you use the service.

We do not collect location data, contacts, photos, or health data from other apps or devices.

When you attach a photo to a workout share card, the image is read by your browser, drawn onto the card, and discarded when you close the dialog. It is never uploaded to us and never stored. The card you post is a flattened image, so any location data your camera embedded in the original is removed rather than published.

• To give your coach the context that makes its advice personal rather than generic — this is the core function of the product.
• To show your progress, statistics, and history.
• To keep your account secure and to operate the service.
• To understand, in aggregate, which features are used, so the product can be improved.

Where the law requires a lawful basis, ours is the performance of our contract with you (providing the service you signed up for) and our legitimate interest in operating and improving it.

AdimFit runs on third-party infrastructure. These providers process data on our instructions and are bound by their own agreements with us:

• Google Cloud and Firebase — authentication, database storage, and hosting. Your account and training data are stored here.
• Anthropic — provides the AI model behind the coach. When you send a message, your message plus relevant profile and workout context is transmitted to Anthropic to generate a reply.
• PostHog — product analytics, hosted in the EU. Receives anonymous usage events (for example “a workout was logged”) tied to a random account identifier. We do not send your name, email, message content, or workout notes to PostHog.

These providers may store and process data outside your country, including in the United States and Europe. We do not sell your data or share it with advertisers or data brokers.

A trainer, gym or health plan you have connected to is not one of these providers. Each is a separate recipient of a narrow slice of your data, acting on their own account rather than on our instructions, and nothing reaches any of them until you have said yes to the question described under Who can see your training log. Once it does, they are responsible for it under their own privacy terms and we are not responsible for what they do with it. If that concerns you, do not connect, or disconnect.

Your data stays for as long as your account exists. Delete your account and we remove your profile, workout log, and coach conversations from our active systems. Backups and server logs may persist for a limited period before being overwritten in the ordinary course.

You can clear your coach conversation at any time from the AI Coach screen without affecting the rest of your account.

You can ask us to:

• Give you a copy of the data we hold about you.
• Correct anything inaccurate.
• Delete your account and its data.
• Restrict or object to certain processing.

Email support@adimfit.com and we will respond within 30 days. If you are in Nigeria, you may also complain to the Nigeria Data Protection Commission; in the EU or UK, to your local supervisory authority.

Data is encrypted in transit and at rest by our infrastructure providers. Access is scoped so that you can only ever read or write your own records, enforced at the database level rather than only in the app.

No system is perfectly secure. If a breach affects your data, we will notify you and the relevant authority as required by law.

AdimFit is not intended for children under 13, and we do not knowingly collect their data. If you are between 13 and 18, you should have a parent or guardian's permission to use it. If you believe a child has given us data, contact us and we will delete it.

We use browser storage to keep you signed in and to remember preferences such as whether you have dismissed the install prompt. We do not use advertising or cross-site tracking cookies.

AdimFit may in future be restructured, incorporated in another country, or acquired. If that happens, your account and its data may be transferred to the successor entity as part of that transaction, so the service can continue without interruption.

Any successor will be bound by commitments no less protective than those in this policy. We will tell you before your data moves to a different controller, and you may delete your account instead.

If this policy changes materially, we will update the date at the top and, where the change is significant, tell you in the app. Continuing to use AdimFit after a change means you accept the revised policy.

Questions about this policy or your data: support@adimfit.com.