Privacy Policy

Effective date: 1 November 2026
Last updated: 1 November 2026

1. Who we are and what this policy covers

FIGHTA is operated by YOKUDU Pty Ltd. (“FIGHTA”, “we”, “us” or “our”).

We determine why and how personal information is used to provide FIGHTA. We are the responsible party under South Africa’s Protection of Personal Information Act, 2013 (POPIA), and the controller where the EU General Data Protection Regulation (GDPR) or UK GDPR applies.

This policy covers the FIGHTA app, getfighta.com, the account-action website at account.getfighta.com, and related support and account emails. The main website is a marketing website, not an online shop or a full web version of the training app.

For privacy enquiries, rights requests or questions for our Information Officer, use our contact form. Please identify your request as a privacy request. Do not send your password or an account verification/reset link.

2. The short version

  • We use your details to provide your account, record your training, show progress and synchronise supported information between your devices.
  • Your account-linked workouts, weight entries, routes, heart-rate recordings and selected workout photos can be stored in our cloud service when cloud sync is enabled. They are not automatically posted publicly.
  • Optional location, Bluetooth, photo and notification features need the relevant choices or device permissions. Permission to use a device feature is not, by itself, permission for unrelated uses of your information.
  • We do not sell your personal information or use your health, fitness or route information for targeted advertising. The current app has no advertising or cross-app tracking SDK.
  • You can request access, correction and deletion. Account deletion is available in the app. Copies you have shared with another service are subject to that service’s practices.

3. Information we handle

Account and profile

When you create an account, we handle your email address, chosen display name, password authentication information, account identifier, verification status and account/security timestamps. Passwords are transmitted for authentication and password changes; the authentication service stores a password hash rather than a readable password. We do not maintain a separate plaintext password record.

Depending on the information you provide and the features you use, your profile can include your bio, date of birth, gender selection, height, gym name/membership answer, training experience, training frequency, activities, goals, motivations or barriers, equipment, stance, units and appearance preferences. Profile and account details are separate from the weight log.

Workouts, plans and progress

We handle workouts you log, record or complete: activity and training type, title, dates and times, duration, distance, perceived intensity, notes, location text and sport-specific details. Guided/interval sessions can include reached rounds, scheduled combinations and strikes, timing, settings and replay information. These are not independent measurements of punches or kicks actually performed.

Plans include your selected plan, schedule and time zone, session dates, completion links, progress, and pause, resume, skip or end actions. Saved workout setups and relevant preferences help you reuse settings.

We calculate summaries such as training load, fitness trends, consistency, pace and estimated calories. These are estimates derived from available inputs, not medical measurements or diagnoses.

Weight and heart rate

If you log weight, we handle the weight, entry date and related entry metadata. If you connect a compatible Bluetooth heart-rate monitor during training, we can handle heart-rate samples and summary values, such as average and maximum heart rate, and use relevant inputs for calorie estimates.

The app can remember the selected sensor’s identifier and name locally and keep a bounded local connection/reading diagnostic history to help troubleshoot the connection. These device-connection records are different from heart-rate samples attached to a saved workout. The current app does not read or write Apple Health/HealthKit records.

GPS routes

If you enable GPS for a supported workout and grant permission, the app can record precise coordinates and timestamps, accuracy, altitude and related route information to calculate distance, speed, pace and elevation and display your route. Recording can continue during the workout while the phone is locked or another app is in use, subject to your permissions and device settings. It is not intended as continuous location tracking outside your workout.

Saved routes may reveal your home, workplace, gym or routine. You can use non-GPS/manual features without granting location access. Revoking permission stops future permitted collection; it does not automatically erase routes already saved or shared.

Photos, notes and shared artwork

We handle photos you choose to attach to a workout and the text you enter. We copy selected photos into the app’s managed storage; cloud sync can upload those photos to private account-linked storage. This does not give us your entire photo library. The current app does not request camera or microphone recording access.

Original photo files may contain embedded metadata, including location information. Do not assume FIGHTA removes it. Avoid including other people or their personal information without appropriate permission.

When you choose to share a workout image, the app generates artwork from your selected photo, route, statistics or heart-rate graph and opens your device’s sharing tools. Copying a sticker places a generated image on the device clipboard. Other apps you select, and operating-system clipboard features, may receive the copied/shared information. We cannot recall their copies.

Contact forms and support

Our WordPress contact form uses Contact Form 7. It asks for your name, email address and subject; the message is optional. We receive and use the submission to respond and keep relevant correspondence. Website hosting, email delivery, mailbox and any configured security/form integrations may process the submission and connection metadata. Contact Form 7 is software running on our website; using it does not itself mean its author receives your message.

Please do not include passwords, authentication links, detailed health records or another person’s confidential information in a general enquiry. We may ask you to provide the minimum information needed to resolve a particular support request using an appropriate channel.

Technical information and local settings

When the app or website contacts our providers, their systems receive connection information such as IP address, request time and browser/app information. Operational, authentication, delivery and security logs may retain relevant metadata. This is distinct from an in-app behavioural advertising profile.

The app also stores local settings, reminder/inbox state, active-workout recovery information, account-scoped cached records and sync metadata needed for reliable saves, retries and conflict review. Not every setting or unfinished session synchronises to another device. Notification permission and Bluetooth pairing choices remain device-specific.

4. Why we use information and our legal grounds

We limit processing to relevant purposes and the applicable lawful grounds:

PurposeTypical informationBasis where GDPR applies
Create, authenticate, secure and administer your accountName, email, account ID, authentication informationPerforming our agreement for ordinary account administration; legitimate interests in preventing abuse and protecting accounts; legal obligations where applicable
Provide the training records, synchronisation and progress features you chooseWorkout, plan, weight, profile, route and sensor informationConsent for optional sensitive processing; explicit consent where information is health data; the separate health-data condition below also applies
Tailor training suggestions/settings and display your progressSelected activities, goals, history and preferencesConsent where sensitive information is involved; otherwise performance of the requested service where necessary
Answer an enquiry and resolve problemsContact details, message and relevant troubleshooting informationSteps requested before an agreement, performing our agreement, or legitimate interests in responding and supporting users; separate consent/condition if sensitive information is necessary
Operate and protect the app, website and account pagesEssential storage, limited connection/security metadataLegitimate interests in a secure, functioning service, subject to your rights; legal obligations where applicable
Send optional promotional messages or use non-essential website technologies, if offeredSubscription/contact preference and applicable website informationSeparate consent where required; not permission inferred from a general enquiry or acceptance of these Terms
Meet legal duties and handle legal claimsOnly the information necessary for that duty or claimApplicable legal obligations or legitimate interests; a separate lawful exception is required for health information

Weight, heart rate and some fitness/profile information can be health or special-category information. Where we rely on consent, the proposed basis is GDPR Article 6(1)(a) together with explicit consent under Article 9(2)(a), and the applicable POPIA consent/authorisation requirements for special personal information. Ordinary contractual necessity or legitimate interests alone do not authorise sensitive health processing.

You can withdraw consent by contacting us. You can also stop using the relevant feature and revoke device permissions for future collection. Withdrawing a device permission does not itself withdraw every processing consent or delete existing records; tell us if you also want processing restricted or information erased. Withdrawal does not invalidate processing that was lawful before withdrawal. If necessary consent is withdrawn, we may be unable to provide the feature that requires it, but do not use that as permission for unrelated processing.

For information about children, additional safeguards and competent-person/guardian authorisation apply as described in section 11. We do not rely on a child merely accepting the Terms to establish valid parental or sensitive-data consent.

Providing account credentials and the minimum information for a requested feature is necessary to provide that feature. You do not have to browse our marketing website through an app account. Optional permissions or profile answers can be declined where the feature offers that choice. If you do not provide a required contact-form field, we cannot process that form, but you can use our contact page instead. We do not collect workout information because a law generally requires you to exercise or keep a fitness record.

5. Recommendations, advertising and automated processing

FIGHTA uses calculations and rules to display progress, suggest workouts and support your selected plan. This does not involve a decision intended to produce legal or similarly significant effects, such as an insurance, employment or credit decision. Do not use a fitness score or calorie estimate as a clinical assessment.

We do not sell, rent or share your health or fitness information for advertising or brokered profiling. The reviewed app does not send your private workouts or photos to a third-party AI service for model training. If we introduce materially different processing, we will update the notice and obtain any required permission before it begins.

6. Who receives information

We disclose information only as needed for the described service, your instructions, or a lawful obligation:

  • Supabase provides authentication, database, private file storage and server functions. Account-linked profile, workout, weight, plan, route, heart-rate and photo information can be processed there when the relevant cloud features are enabled.
  • Resend delivers account verification, recovery, email-change and related service emails. It processes recipient details, message content containing necessary account-action links, and delivery information. It does not receive your full workout history merely to send an account email.
  • Hostinger and our business email providers host the marketing/account websites, deliver website resources and handle relevant website or support email processing. The WordPress installation includes Hostinger Reach; use of any optional subscription/marketing features must follow your separate choices.
  • Apple provides iOS services, Apple Maps/map content, App Store distribution and, for beta testers, TestFlight. Map rendering can involve map-area and connection requests to Apple; a route drawn in FIGHTA is not a promise of offline-only mapping. Apple’s independent processing is described in its privacy information and Maps notice.
  • People/apps you choose receive information when you share images, copy/paste stickers, send an export or provide support material. No automatic public friends feed is provided by the current account-sync implementation.
  • Authorised staff and advisers may access the minimum necessary information for support, security, legal or operational work, under appropriate restrictions. Private cloud storage is not a claim that an authorised administrator can never access data.
  • Authorities or transaction parties may receive information when disclosure is legally required or necessary to protect rights or safety. A genuine business transfer would be subject to confidentiality, lawful safeguards and any required notice; it does not permit a new incompatible use of health information without a lawful basis.

We require service providers processing information for us to be bound by appropriate confidentiality, security, purpose-limitation and data-protection obligations. Those arrangements must provide the protection required by applicable law and our commitments; a provider’s own privacy page is not a substitute for those arrangements. Providers may have separate responsibilities for their own platform/security administration.

The current build does not offer Apple/Google account sign-in or live subscription billing. If purchases become available, we will describe the actual billing providers and transaction/entitlement information before that processing starts. The marketing website currently has no checkout.

7. Where information is processed

YOKUDU operates in South Africa. Our hosting, authentication, email and infrastructure providers may process information in other countries, including through support or infrastructure outside a selected database region. Selecting an EU database region does not mean every provider operation takes place only in the EU.

Resend’s published information describes primary processing in the United States; Supabase’s arrangements include relevant international support/operational processing.

Before a restricted international transfer, we must establish an applicable transfer mechanism and safeguards. These may include an adequacy decision, applicable standard contractual clauses and any necessary supplementary measures or UK transfer addendum. Transfers from South Africa must also meet POPIA’s requirements, including section 72 where applicable. We do not treat your general acceptance of this policy as blanket consent to an otherwise unlawful transfer.

You can contact us for information about relevant safeguards or a copy of applicable contractual protections, subject to proportionate redaction of confidential information.

8. Storage, retention and deletion

We keep information for the purpose for which it is needed, not simply because indefinite storage is convenient:

InformationRetention approach
Active account, profile, saved workouts, weight entries, plans and linked private filesWhile needed to provide your account/history and until you delete the relevant information or account, subject to lawful, limited exceptions
Synchronisation receipts, tombstones and conflict/recovery versionsOnly as necessary to reconcile devices, prevent deleted records reappearing and handle review/recovery; some prior versions can remain after an edit.
Account-action website contextsAuthorisation lasts at most ten minutes. Expired encrypted contexts are scheduled for cleanup; actual removal depends on successful cleanup, and is monitored rather than guaranteed at the precise expiry second
Support/contact correspondenceFor resolving and reasonably following up the enquiry and any necessary legal record.
Infrastructure, email delivery and security logsA limited period appropriate to operation, security and legal duties.
Provider backups and residual copiesRestricted recovery copies until their applicable expiry/deletion cycle.

In the app, go to Settings → Manage Account → Delete account to request deletion. You may need to re-enter your password to verify the request. You can also contact us for assistance or exercise a legal erasure right without being required to retain access to an old device.

Successful account deletion removes the active authentication account and associated cloud records through the deletion process. Removal of private file bytes uses a separate cleanup process and is not necessarily instantaneous. A pending or failed request is not treated as proof that every copy has been erased. We must also deal with relevant recovery copies and any legally retained information, tell you about applicable exceptions and complete rights requests within the legally required period.

Uninstalling the app or signing out is not an account-deletion request. Account-scoped local data may remain on a device for offline use or later sign-in. An offline device or an independently created device backup cannot be guaranteed to erase remotely at the instant you delete an account elsewhere. Remove local copies from devices you control where needed, and contact us if you need help. We cannot delete files you exported, pasted or shared to another party’s system.

We may retain a limited record where required by law or necessary for a valid legal claim, with access and use restricted to that reason. Where law permits or requires delayed erasure from recovery backups, those copies must not be used as live data and deleted information must not be reintroduced into the live service by a restore.

9. Security

Measures include encrypted network connections, authenticated account access, account-scoped storage, private cloud file access and verification of file integrity. Authentication sessions on iOS use Keychain-based secure storage. Some temporary account-web authorisation material is encrypted server-side.

This is not an end-to-end encrypted service. Local workout databases, photos and JSON exports are not separately encrypted by FIGHTA as a portable encrypted vault; their protection also depends on your device, operating system and how you store or share them. Secure your device, account and exported files.

No system is completely secure. If a personal-information security incident occurs, we will assess it and notify the relevant regulator and affected people where and as required by law. Contact us promptly if you believe someone has accessed your account without permission.

10. Your choices and legal rights

Depending on the law that applies, you may request confirmation/access, a copy, correction, erasure, restriction of processing, a portable copy of eligible information, or object to particular processing, including processing based on legitimate interests. Where processing relies on consent, you may withdraw it. You can object to direct marketing at any time and use an unsubscribe mechanism in any marketing message.

Edit available details in the app or use our contact page. Where export tools are available, their output may not include every separately stored photo, original file or provider record. You can ask us for a fuller access/portability response rather than relying only on a local JSON backup.

We may need proportionate information to verify your identity and authority before disclosing or changing data. We do not ask for your password by email. Rights have legal conditions and exceptions; if we cannot comply, we will explain the reason and available complaint route. Requests are normally free, subject to any narrow fee/other exceptions the applicable law permits.

For GDPR requests, we normally respond within one month; if a lawful extension is needed, we explain it within that initial period. For POPIA/PAIA requests, we follow the applicable procedure and reasonable/statutory time limits rather than assuming all requests have the same deadline.

You can complain directly to South Africa’s Information Regulator, including through its eServices complaints portal. Where GDPR or UK GDPR applies, you can complain to the relevant supervisory authority, including the authority in your habitual residence, workplace or place of the alleged infringement, or the UK ICO. You do not have to complain to us first.

11. Younger users

FIGHTA accounts and training features are intended for people aged 13 or older. They are not intended for children under 13. If you believe a child under 13 has supplied information, contact us so we can investigate and take appropriate steps.

If you are 13–17, involve your parent or legal guardian before creating an account or supplying health, weight, heart-rate or location information. Being 13 does not automatically mean you can consent to every use of personal information. Under POPIA, processing children’s information generally needs prior authorisation from a competent person or another valid statutory exception. Where GDPR consent rules apply, the online-consent threshold varies by country between 13 and 16, and sensitive-data and contractual-capacity rules also matter.

Where guardian authorisation is required, it must be obtained and appropriately verified before the relevant processing. A guardian or young user can contact us to ask questions or exercise applicable rights; we will verify authority and respect the young person’s own rights under applicable law. We do not use children’s health information for behavioural advertising. Do not post or share a child’s route, photo or private information without appropriate authority and consideration of their safety.

12. Website storage, cookies and communications

Our account-action pages use a short-lived, per-tab browser-session handle so you can complete an email action. It is not an advertising identifier or a general web login, and the current account pages do not contain third-party advertising/analytics scripts.

The WordPress marketing website and configured hosting/security services can use storage or request metadata necessary for site operation. Browser controls may disable storage, although that can prevent some functions from working. We request any consent required for non-essential cookies or similar technology before it is used; essential processing is explained rather than bundled into marketing consent.

Account/security emails and local workout/plan reminders are different from marketing. The current app schedules local device notifications rather than uploading a remote push token for a push-marketing service. You can change reminder settings and iOS notification permission; lock-screen previews can reveal workout information to someone who can see your device.

Submitting a support enquiry does not itself subscribe you to promotional emails. Optional marketing, if offered, requires the relevant lawful permission and an easy way to stop it. External websites/apps have their own notices for their independent processing; that does not remove our obligations for providers acting on our behalf.

13. Changes to this policy

We will update this policy when relevant processing or requirements change and show the new date. For a significant change we will give an appropriate notice, and seek fresh permission before new processing where required. Merely posting an updated policy or treating continued use as consent does not replace a legally required consent.

Contact form · Terms