LiftWise Privacy Policy
Last updated:
We connect your account through our SSO with your LiftWise workouts, training history and preferences. This policy explains device storage, cloud services and diagnostics.
We operate LiftWise. This policy explains the information we handle through the app. Read it together with our company Privacy Policy, which explains our general privacy practices and rights request process.
Our legal identity and contact details
- Registered operator
- CHEFU TECHNOLOGIES (Pty) Ltd., a private company registered in South Africa
- Registration number
- 2026/139936/07
- Business and legal notices
- 145 Ka-Dinga, Malamulele, Limpopo, 0982, South Africa
- Information Officer / privacy requests
- privacy@chefu.co.za
- Legal enquiries
- legal@chefu.co.za
- Support
- hello@chefu.co.za · +27 60 603 1205
- Website
- chefu.co.za
1. Sources of information and purposes at a glance
We receive information from you, our SSO and the app's operation. Your account identifier links saved records to you; it is not anonymous merely because it is not your name.
| Source | Information | Purpose |
|---|---|---|
| Our SSO | Account ID, contact and profile information, tokens | Authenticate you and identify your records |
| Onboarding answers | Goal, experience, gender, units and reminders | Set up your profile and preferences |
| Workout entries | Exercises, sets, repetitions, loads and times | Save training and calculate history and statistics |
| Selected photo | The cover image you choose | Store and display a workout cover through Cloudinary |
| App operation | Errors, logs, technical context and sampled replays | Investigate failures through Sentry |
| Support report | Description, account contact, version and platform | Investigate and handle your report |
Workout details and free-text entries can reveal fitness or health information. Avoid adding diagnoses, medical documents, identity numbers or private information about someone else unless necessary for a request you deliberately make. Such information can have additional legal protections.
2. Your account and fitness profile
We use our SSO for LiftWise registration and sign-in. Through it, we receive your account identifier, email address, name, profile photo, account roles and gender where available. Sign-in tokens keep your session authenticated.
We store your training goal, experience level, preferred weight unit and reminder settings with your account. Gender is part of your shared profile with us: LiftWise can reuse an existing answer, and an answer first supplied during LiftWise onboarding is saved to that shared profile. Our other services using that profile may reuse it.
We use this information to authenticate you, keep your records associated with your account, display your profile and apply your training and reminder preferences.
3. Workouts and progress
We receive and store your saved workouts and completed sessions so you can retrieve them through your account. These records include:
- Workout names, descriptions, selected exercises, exercise order and workout cover images.
- Sets, repetitions, rest settings and the weights you enter for exercises.
- Session start and completion times, duration, completed sets and the workout details recorded with each session.
- Saved exercise bookmarks, training preferences and reminder schedules.
We use these records to provide your workouts, training history, activity calendar, streaks and progress statistics. Exercise search terms are sent to our backend to find matching exercises. The weights you enter are exercise loads; LiftWise does not require a body-weight measurement for its current onboarding.
4. Cover photos and support reports
If you choose a workout cover, LiftWise requests photo-library access and uploads the image you select through our backend to Cloudinary. It does not upload your entire photo library. Covers are delivered through an image URL that can be accessed by anyone who has that URL, so choose images you are comfortable using this way.
When you submit an in-app problem report, we store your description, account identifier, email address, app version, platform, report status and submission time to investigate and respond. Do not put passwords or unnecessary sensitive information in your report.
5. Device storage and reminders
LiftWise caches workout and exercise information on your device and stores in-progress workout drafts and completed sessions waiting to sync. Pending sessions are sent to our backend when the app can successfully sync them. Device storage also remembers settings such as haptics and keeping the screen awake during a workout.
On mobile, sign-in credentials are stored using the operating system's secure storage. The web version stores its session in browser local storage. Workout caches and drafts use app storage rather than the secure credential store.
Workout reminders and rest alerts are scheduled locally on your device using your saved settings. LiftWise requests notification permission and uses Android alarm scheduling where available. You can change reminder preferences in the app and manage notifications and alarm permissions in device settings.
Signing out clears the active session and the persisted query cache, but locally saved workout drafts and pending completions can remain for your account. Clearing app storage can remove unsynced progress. Uninstalling the app does not delete records already saved on our servers.
6. Diagnostics and session replay
Production versions of LiftWise use Sentry to investigate errors and understand failures. Sentry can receive error details, logs, device and operating-system information, app version, interaction breadcrumbs and network metadata. The app enables Sentry's default personal-information collection, which can include your IP address and personal information present in diagnostic context.
Session replay is enabled for a sample of ordinary sessions and for sessions in which errors occur. A replay reconstructs activity within LiftWise, including screen changes and interactions, to help us reproduce problems. It is not a recording of everything you do on your device.
The mobile replay integration uses Sentry's default text and image masking. Masking does not make all diagnostic information anonymous. Read Sentry's replay privacy documentation for more information. LiftWise does not currently provide an in-app switch for diagnostics or replay.
7. Service providers and exercise guidance
- Our SSO and backend: we provide sign-in, profile management, synchronisation and support handling. We use Google Firebase services, including Firestore, for account authentication and application records.
- Cloudinary: stores and delivers the workout cover images you upload.
- Sentry: processes diagnostics and session replay as described above.
- Expo: delivers app updates. Update checks send technical app and network information needed to request and download a compatible update.
- Google Gemini: when AI exercise guidance is enabled on our backend, it can generate instructions from the exercise catalogue's name, description and source guidance. The request does not include your account profile, workout history or recorded exercise weights. Catalogue instructions are used when AI guidance is unavailable.
These services may process information outside South Africa. Their own privacy notices describe their processing: Google, Cloudinary, Sentry and Expo.
LiftWise does not include an advertising SDK or use your workout records for targeted advertising.
8. Lawful grounds and required versus optional information
We process account and workout information to provide the tracking service you request, and support communications to resolve your enquiry. For ordinary personal information, relevant grounds can include performance of our agreement, legitimate interests in maintaining a secure and functioning service and resolving faults, compliance with a specific legal duty, or consent where required.
Legitimate interests must be balanced against your rights and reasonable expectations. They are not permission to use information for any purpose. Additional legal conditions can apply to children's or health-related information. Agreeing to our terms does not itself satisfy those conditions or consent to optional session replay.
Sign-in and information identifying your account are necessary for account-linked features. The current app requires onboarding answers before entry to its main experience. Workout entries are needed for the corresponding records. A cover photo, support report and notification permission are optional. Declining photo access prevents choosing a cover; declining notifications prevents reminders but does not itself prevent workout tracking.
The current app starts production diagnostics and replay without a separate in-app opt-out. That absence does not remove any right to object or any requirement for consent. Contact our Information Officer to ask about a particular processing activity or exercise an applicable right.
9. How long we keep information
We keep account-linked workout records, history, preferences and cover images as needed to provide the service. Support reports are kept as needed to investigate the issue and handle related support. Diagnostics and replay information are kept as needed to investigate errors and maintain the app.
We delete or de-identify personal information when it is no longer needed for these purposes or when a verified deletion request is handled, except for records that must be kept for a specific legal obligation or legal claim. Any such retention is limited to the relevant records and the period needed for that obligation or claim.
Deleting app data is a separate request from deleting a workout template or removing your shared sign-in. Send app-data deletion requests to privacy@chefu.co.za. We do not promise that signing out, uninstalling the app or deleting your sign-in automatically removes copies held by our service providers.
Retention is assessed by record type and purpose: workout history supports tracking, support records support the issue being handled, and diagnostics support fault investigation. A possible future legal need does not automatically justify keeping everything indefinitely. A legal hold concerns the relevant records and is reassessed when its reason ends.
Local caches, drafts and queued completions have different lifecycles from server records. Cache expiry does not mean account history has been deleted. Specify server records, uploaded covers or local-device guidance when making a request so that we can explain what each action affects.
10. Children and parental permission
Children may use LiftWise with a parent or legal guardian's permission. A parent or guardian must authorise a child's use of the account and online features and the associated processing of personal information before the child uses them.
This includes the shared account profile, fitness preferences, workout records, uploaded images and diagnostics described in this policy. A parent or guardian may contact privacy@chefu.co.za to ask about that information, withdraw permission or request deletion. LiftWise does not currently include an in-app process for verifying parental permission.
For children: your workouts are connected to your account and saved online. A cover picture can be opened by anyone who has its link. Ask a parent or guardian before signing up or uploading a picture. Do not include your school, address or private medical details in workout names or support messages.
For parents: where law requires verified authorisation, that must happen before the relevant collection or disclosure. You can ask to review information we hold about your child, correct or delete it, or refuse further consent-based collection or sharing. A permission statement on this page does not replace verification.
Age thresholds vary internationally. US rules can require verifiable parental consent for covered online collection from children under 13; EU rules on a child's own consent to online services depend on the country. Downloading the app does not itself satisfy those rules.
11. Calculated statistics and AI guidance
Totals, workout volume, activity dates and streaks are calculated from saved records. They are app features, not a clinical evaluation. The AI Coach requests instructions using exercise catalogue information; it does not send your personal workout history or account profile as a prompt to Gemini.
We do not use these calculations or the AI Coach to make decisions about credit, insurance, employment, access to healthcare or another similarly significant matter. If a calculated feature appears inaccurate, identify the affected entry or calculation so that we can investigate.
12. Deleting workouts and your account
You can delete a workout from its options in LiftWise. This removes the saved workout template; completed sessions keep a snapshot of the workout for your history. Deleting a template does not automatically delete its cover image or completed sessions.
You can delete your shared sign-in in our SSO's Security settings, with identity verification. Deleting that shared sign-in affects access to our other apps as well as LiftWise. It does not automatically erase every LiftWise workout record, uploaded cover or support report. To request deletion of those records, email privacy@chefu.co.za and identify LiftWise and the account concerned.
13. Our responsibility and the scope of this notice
For personal information we receive and decide how to use, we act as the responsible party under South Africa's Protection of Personal Information Act (POPIA), or the controller under other applicable data-protection law. Our legal identity and contact details appear above. Information stored only on your device and never sent to us is different from information held in our systems.
This notice covers LiftWise. Our company Privacy Policy also explains website enquiries and other company services. Visiting this website is separate from using the app: website cookies and optional website analytics are covered by our Cookie Policy and the website's cookie preferences.
Third-party services can also have responsibilities for requests they receive directly. Their notices do not replace our responsibility for information we disclose or the providers we engage.
14. Disclosures and legal requests
The app-specific sections identify the services involved in ordinary use and the information sent to them. Staff or providers handling a support or privacy request may need the information relevant to that request. This does not give us access to files that remain only on your device.
We may disclose relevant information where required by a valid legal obligation or enforceable request, or where lawfully necessary to protect rights, investigate abuse or address a security incident. A disclosure must have a lawful purpose and be limited to relevant information; someone claiming authority is not, by itself, permission to release your information.
If the app changes operator through a business transfer, any transfer of personal information remains subject to applicable law and the purposes described here. A material change in use requires the notice or permission required by law.
15. Security and incident questions
Security depends on the app, the providers involved and your device. Our website and published account API use HTTPS. This does not mean every local file, backup or item of diagnostic information is encrypted by the app. The app-specific sections explain device storage and publicly accessible image URLs.
Keep your device updated, protect access to shared devices, and do not send passwords, sign-in codes or unnecessary sensitive files. If you suspect information handled by us has been exposed, email privacy@chefu.co.za with the app name and a description. We may ask for relevant details through an appropriate channel.
No service can promise absolute security. If an incident triggers a legal notification duty, we must notify the relevant authority and affected people as applicable law requires. Publishing this notice does not remove those duties.
16. Your rights and how to make a request
Depending on applicable law, you can ask whether we hold information about you, request access, correct inaccurate information, request deletion, object to processing or ask for it to be restricted. Where applicable, you can request a portable copy of information you supplied. These rights can have conditions and exceptions.
For LiftWise, email privacy@chefu.co.za and tell us:
- Which app and feature your request concerns.
- Your account email, if you use an account, or the address used for earlier correspondence.
- Whether you want access, correction, deletion, an explanation, an objection considered or consent withdrawn.
- Whether you act for a child or someone else, and your authority to act.
We may verify identity or authority before releasing or deleting information. Verification should be proportionate; do not attach identity documents unless we explain why they are needed and how to provide them. We cannot retrieve information that never left your device.
We will handle requests within the applicable legal time limit and explain a lawful extension, refusal or restriction and the available complaint route. Where a law permits an access fee, we will explain it before charging. If particular records must be retained for a legal obligation or legal claim, we will explain why.
17. Withdrawing permission and changing choices
Where processing relies on consent, you can withdraw it without affecting the lawfulness of earlier processing. Contact our privacy address and identify the feature or information concerned. An authorised parent or guardian can act for a child.
Changing device permissions can stop a feature, but it does not automatically delete information already received by us or a third party. Deletion is a separate request. Some information may still be needed for another lawful purpose, such as a legal claim.
Agreeing to terms, granting device access and consenting to an optional use of personal information are different decisions. This notice does not treat reading the page or continuing to use the app as blanket consent.
18. International users and overseas processing
We operate from South Africa and intend the apps for international distribution. Information sent to us can be processed in South Africa and countries where the providers described above operate. A provider's privacy notice alone does not establish that every transfer meets all legal requirements.
Where a transfer requires a safeguard, it must have an applicable lawful basis and safeguard, such as an adequacy decision or appropriate contractual protection. Additional restrictions can apply to children's and sensitive information. Contact us to ask about the recipients, locations and safeguards relevant to your information.
If EU, EEA or UK data-protection law applies, its mandatory protections remain available, including applicable access, correction, erasure, restriction, portability, objection and complaint rights. Regional law can require specific parental authorisation or another condition for children's or health-related information. This notice does not assert that a regional representative or consent-verification process is already in place.
19. Questions and privacy complaints
Contact privacy@chefu.co.za with the app name, what happened and the outcome you seek. You do not need to send private workout details or audio files merely to raise a concern.
You can complain to South Africa's Information Regulator through its official contact and complaints page or POPIAComplaints@inforegulator.org.za. Its published office address is Woodmead North Office Park, 54 Maxwell Drive, Woodmead, Johannesburg, 2191.
Where another authority has jurisdiction, you can use its complaint process, including the competent authority in your EU/EEA country or the UK Information Commissioner where applicable. Contacting us does not waive your right to complain or seek a legal remedy.
20. Changes to this policy
We will update this page and its date when LiftWise's information practices change. Changes in collection, purpose, providers or privacy choices may require an updated notice. You can save or print this page for your records.
Where required, we will give additional notice or obtain permission before a new use. An updated page does not retrospectively authorise processing that required consent or another legal condition when it occurred.