Skip to content

Privacy Policy

Effective 4 October 2026 · Terms of Service

Kinehub ("we", "us") helps people move better through guided rehab and mobility sessions. This policy explains what we collect, why, how long we keep it, and the choices you have. We've tried to keep it short and plain.

1. Who we are

Kinehub is a trading name. The service is run by Junaid Dikko, a sole trader — an individual rather than a company — established in England and Wales, who is the data controller for the personal data described in this policy. Processing is governed by the laws of England and Wales. The controller's postal address is 41 The Marlowes, London NW8 6NB. General enquiries go to dikkojunaid21@gmail.com. For data-protection questions, or to exercise any of the rights in section 10, email dikkojunaid21@gmail.com. Kinehub has not appointed a data protection officer; the controller answers these requests directly.

2. Information we collect

  • Account — email address and, if you provide one, display name.
  • Profile — goals, focus areas, fitness level, daily time commitment, reminder time, gender, age band, height, weight, units preference, activity level, job type, pain areas, existing conditions, dark-mode and sound preferences.
  • Profile photo — only if you add one. Your device asks before the app can open your photos, and only the picture you choose is uploaded. We crop and shrink it and remove its location and camera data before it leaves your device. It is stored privately: only you and a physiotherapist you connect with can see it. Removing it, or deleting your account, deletes it.
  • Pregnancy dates — if you tell us you are pregnant, your due date and, later, the date your baby arrived, if you choose to give them. They are used only to choose exercises that suit your stage of pregnancy or recovery after birth, and to pause reminders around the birth. You can remove them, and pregnancy, from your profile at any time.
  • Activity — session logs (date, duration, exercises completed, optional mood and notes) and per-exercise completion records.
  • Optional health logs — before/after pain ratings, sleep quality, sleep hours, and recovery scores you choose to enter.
  • Safety screening answers — if you tell us you are in pain, we ask a short set of safety questions before building you a programme. We store which of them you answered “yes” to, and when you answered. Those answers are health information and some are sensitive in their own right: they cover bladder and bowel control, numbness, weakness, unexplained weight loss, whether you have ever been treated for cancer, fever, night pain, and long-term steroid use or a diagnosis of osteoporosis. They are used for one purpose — deciding whether to give you exercises or tell you to see a clinician — and they are never sent to the AI provider.
  • Care context — whether you are waiting for a health appointment, already under a clinician, or managing on your own, and, if you choose to give it, the date you were referred.
  • Wearable & health data — if you connect a device or import metrics, we may store steps, active minutes, resting heart rate, average heart rate, sleep hours, sleep quality, calories burned, and workout count.
  • AI coach messages — the messages you send and receive through the recovery coach so we can generate replies and keep your conversation history.
  • Form-check photos and clips — if you use form check, the photos or short clip of you doing an exercise that you choose to upload. They are kept only while they are being reviewed (see sections 7 and 11); the written feedback is kept.
  • Therapist link & consent choices — whether you are connected to a clinician, how you connected, and your per-category consent choices (pain data, check-in/sleep data, wearable data, mental health/coach messages).
  • Shared report tokens — when you generate a shareable report, we create a random link and store the snapshot of data it points to.
  • Payments — Stripe customer ID, subscription ID, price/product IDs, status, and current period dates. We do not store card numbers.
  • Technical — minimal error and request logs needed to keep the service running, plus anonymised analytics events.
We do not collect your precise location, contacts, advertising identifiers, or biometric data beyond what you import from a wearable.

3. How we use your data

  • Personalise your daily plan, exercise library, and "Next 7 days" recommendations.
  • Show your streaks, weekly activity, pain trends, and achievements on the Progress page.
  • Power the AI recovery coach and keep your conversation context.
  • Generate the reports you choose to share with a clinician or trusted person.
  • Send the daily reminder you've configured, if you turn it on, as a notification on your device and in the app, at your local time. We store your timezone for this.
  • Process payments and manage your subscription or team plan.
  • Detect crisis-risk language in coach messages and, where appropriate, show emergency resources or alert a linked clinician.
  • Diagnose and fix bugs.
We do not sell your data and we do not use it for advertising.

5. Who we share data with

  • Payment processor — Stripe handles billing. They receive your email and subscription status, not your health logs.
  • Authentication provider — used for sign-in, including Google sign-in if you choose it.
  • AI providers — personalised exercise suggestions and coach replies are generated by Google Gemini models, reached through the Lovable AI gateway, which processes the request on our behalf. Your name and email are never sent. What is sent is described in section 7.
  • YouTube — embedded exercise videos load from YouTube when you open an exercise page; their privacy policy applies to that frame.
  • Daily (daily.co) — runs video calls between you and a clinician you are connected to. Calls pass through Daily's servers; Kinehub does not record them.
  • Cloudflare — sits in front of the website to keep it fast and protect it from attacks. It sees your IP address and sets one security cookie.
  • Google Fonts — the site's two typefaces load from Google, which receives your IP address when they do.
  • PostHog and Sentry — analytics and error reports, described in section 15.
  • Clinicians you connect with — only what you explicitly consent to share, and only while the link is active.

6. Therapist access and consent

You can connect to a physiotherapist or other clinician by accepting an email invite or entering a connection code. Before any health data is shared, you choose which categories the clinician may see: pain data, check-in/sleep data, wearable data, and mental health/coach messages. Each category is off by default and can be revoked at any time from the Care Team or consent settings. The clinician sees only the data you have consented to, and only while the link is active.

Whatever you choose, a connected clinician can see your name, email, avatar, goals and focus areas. Your existing conditions, current pain level and age are shown to them only if you share pain data. Your answers to the safety screening questions are never shown to a clinician. Disconnecting withdraws all of your consent choices; if you reconnect, you are asked again.

Each time a clinician opens your record, or a report you shared with them, it is logged (at most once an hour) and you can see the list in your Privacy centre. The log is kept for two years. If you share data with a clinician or turn on AI personalisation, we remind you every six months to check that your choices are still what you want.

7. AI coach and crisis detection

Three features send data to an AI provider: the recovery coach, personalised exercise generation, and form check.

The coach receives the messages you send and enough recent conversation to keep context.

Personalised exercise generation receives a profile summary so the suggestions are safe for you: your age, biological sex, height, weight, activity level, occupation type, goals and focus areas, any existing conditions you have told us about, your current pain level, and your recent pain trend including average pain before and after sessions. Your name, email and message history are not included. This is health data, and is treated as special category data under UK GDPR. We do not collect or process data about your ethnicity.

You can turn personalised generation off at any time in your profile settings, and the profile summary above then stops being sent.

Form check receives the photos, or still frames from the short clip, that you choose to upload, together with that exercise's written instructions. The images are stored privately while they are reviewed and deleted as soon as the review comes back, whether it succeeds or not. Only the written feedback is kept.

Crisis detection. We scan coach messages for phrases that may indicate self-harm, suicidal ideation or other severe distress. When one matches we store the matched phrase and a short excerpt of the message so the event can be reviewed and acknowledged, show an in-app Crisis Card with emergency resources, and — only if you have connected a clinician and consented to share mental health data with them — may notify that clinician. This is not a substitute for emergency services: if you or someone else is in immediate danger, call your local emergency number.

8. Wearables and health data

Connecting Apple Health, a fitness watch, or importing metrics manually is optional. We store the metrics you choose to sync so you can see trends alongside your sessions. This data is treated as health data: it is never shared with a clinician without your explicit consent, never used for advertising, and never sold.

9. Cookies and local storage

We use the cookies and local storage required to keep you signed in and remember your preferences (theme, sound, language). Cloudflare sets one security cookie. We also use PostHog for product analytics and Sentry for error monitoring, described in section 15; PostHog is set up to use no cookies or device storage at all. We do not run advertising cookies, we do not sell your data, and we do not use it for advertising or profiling unrelated to your recovery.

10. Your rights

  • Access your data from the in-app profile screen.
  • Update or correct your goals, focus areas, and reminders anytime.
  • Withdraw consent for wearable imports, AI coach, or therapist data sharing.
  • Revoke a share link from the Reports screen at any time.
  • Delete your account and all related data from the profile panel — this is immediate and irreversible.
  • Data portability — download a copy of your data yourself with "Download my data" in the profile panel, or email dikkojunaid21@gmail.com and we will send it.

11. Retention

We keep your data while your account is active so you can access your history, streaks, and progress. Deleting your account removes your personal and health data immediately — sessions, exercise logs, pain and sleep entries, coach conversations, generated exercises, achievements and any clinician messages — except where we are legally required to keep something (for example, billing records held by our payment processor). Shared report links expire automatically 30 days after they are created, and the snapshot is deleted when you revoke the link or when it expires.

Some things are deleted sooner, even while your account is open: form-check photos and clips as soon as their review comes back; coach conversations after 12 months with no activity; the message excerpt stored with a crisis alert after 12 months; and the record of clinicians viewing your data after two years.

12. Security

Your data is stored on Lovable Cloud, a managed backend that hosts our database, authentication, and serverless functions. Data is encrypted in transit (HTTPS/TLS) and at rest. What you type to the AI coach, and the excerpt stored with a crisis alert, are also encrypted by Kinehub itself (AES-256) before they are stored, with a key kept separately from the database, so database access alone does not reveal them. Row-level security ensures one account can never read another account's data, and therapist access is limited by your consent choices. Anyone can turn on two-step sign-in with an authenticator app from their profile, and it is required for Kinehub administrators, who can see therapists' verification documents.

13. Where you are, and what that means

Kinehub is run from the England and Wales and is available to people elsewhere. Whoever you are and wherever you live, the commitments in this policy apply to you in full: the same data, the same purposes, the same rights to access, export and delete.

Which law sits behind those commitments depends on where you are. If you are in the UK, that is UK GDPR, and the ICO is your supervisory authority. If you are in the EEA or Ireland, that is EU GDPR, and you may complain to your national data protection authority. If you are outside both — in the United States or Australia, for example — your data is still handled to the standard this policy sets, and is processed in the UK and EU, but your local privacy law may give you additional or different rights that this policy does not yet describe. If you want to exercise a right you believe you have, email us and we will tell you honestly whether we can do it.

Lovable Cloud and our other providers may host data outside your country of residence. Where data is transferred from the UK or EEA, we rely on appropriate safeguards such as Standard Contractual Clauses.

13a. Emergency information by region

Some parts of Kinehub show you an emergency number, a crisis line, or the name of your local health service. Those are chosen by the country set on your account, which you can change at any time in your profile. We guess it to begin with, from your device's time zone and, where that doesn't settle it, from the country your connection comes from; that guess isn't stored. If the country is wrong, the numbers shown will be wrong too — so it is worth checking, and it is the one setting we would ask you to correct straight away if we got it wrong. If we can't tell which country you are in, or it is one Kinehub isn't set up for yet, we show no phone numbers at all and say “call your local emergency number”.

14. Children

Kinehub is intended for people aged 16 and over. We don't knowingly collect data from anyone younger. If we learn we have collected data from an under-16, we will delete it promptly.

15. Analytics and error monitoring

To keep Kinehub fast and reliable we use PostHog for product analytics and Sentry for crash and error reports.

PostHog receives your user id, the pages you visit, and a fixed list of named events such as starting a session or sharing a report. Events carry no health values: no pain scores and no answers to safety questions. Automatic capture of whatever you click is switched off, specifically so that things like pain scores and symptom labels are not recorded, and session recording is disabled. PostHog uses no cookies or device storage, and processes this data in the United States under Standard Contractual Clauses.

Sentry receives error reports. Session replay runs only when an error occurs, with all text masked and media blocked, so the replay shows the shape of the screen rather than its contents.

Neither tool receives your pain scores, pain notes, coach messages or clinician correspondence. You can opt out by contacting us.

16. Changes to this policy

If we make material changes we'll update the effective date and, where appropriate, notify you in-app the next time you sign in.

17. Contact

Questions, data requests, or complaints: dikkojunaid21@gmail.com. General support: dikkojunaid21@gmail.com.