TotalTrain app privacy policy
Data used by TotalTrain on Android, iOS and the web, its purposes, permissions, recipients, retention and the rights of clients and trainers.
Documentation approved for the forthcoming service opening. Version 2026-11-12 of the app documents was published on 16 November 2026. TotalTrain remains closed to the public. The app will display the applicable texts before acceptance; previous acceptances are not changed.
1. Controller and scope
The platform's data controller is Jose Christian Cazorla Vallejo, a self-employed professional operating under the TotalTrain brand. Public administrative and contact address: Calle Alejandro Dumas, 17, 29004 Málaga, España. Privacy contact: soporte@totaltrainapp.com.
This policy describes Client and Trainer accounts and app features on mobile and the web, including support and security administration. The service is intended for people aged 18 or over. TotalTrain provides planning and tracking tools; it does not provide medical care or emergency services.
Visits to the commercial website have separate privacy information. Visiting these information pages does not sign you into the app or create an account or subscription.
2. Data we receive and its sources
- Account and profile: name, email, sign-in credentials, date of birth and contact details, country, language and preferences you provide at registration and in your profile. Trainer accounts also include the professional and presentation information you choose to provide.
- Use of the service: Client–Trainer relationships, requests and invitations, training or nutrition plans and assignments, activity and food logs, calendar, goals and progress. You or the professional in an authorised relationship provide this information; data is also generated when actions are recorded and summaries calculated.
- Optional sensitive data: body measurements, health information, allergies or limitations and progress photos. The separate choices described below apply.
- Communications and assistance: messages and conversation information, notices, support enquiries, rights requests, reports, responses and evidence supplied in a case.
- Subscription: plan, store, purchase identifiers and status, renewals, cancellations and verification information received from Google Play or the App Store. TotalTrain does not ask you to enter your full card number.
- Security and device: IP address and technical connection data, sessions, access and consent events, app version, platform and installation and notification data where relevant.
3. Purposes and legal bases
Required information is marked in the relevant form. Without the data necessary for registration or a requested feature, that process cannot be completed. You can leave sensitive options disabled; features requiring those data will be limited. We do not use these data for sale or personalised advertising.
The private copy of a delivered plan may contain ordinary professional data about its author that cannot be separated from its content without losing its usefulness. Limited retention pursues the legitimate interest of allowing the recipient Client to continue using what they received, with restricted access, without advertising or reuse for third parties, and respecting applicable rights to object, erasure or restriction. The author profile and separate identifying label are removed when their account deletion is executed. This interest does not itself authorise processing a person's health data or other special categories; those situations require their own justification and review.
- Providing the requested service: creating and maintaining your account, enabling logs and plans, professional relationships, calendar and communications, and managing subscription access rights. The basis is performance of the contract or steps you request before entering it.
- Optional measurements, health and photo features: your specific consent. Where information is health data, explicit consent is required for that purpose; agreeing to general terms does not replace it.
- Security, fraud and abuse prevention and general enquiries: our legitimate interest in protecting accounts and the service and responding to people who contact us. You may object where applicable. Responding to a contract-related request may also be necessary to perform that contract.
- Legal obligations and claims: meeting applicable duties, responding to authorities and establishing, exercising or defending claims, on the basis applicable to each case.
- Professional presentation: displaying the professional information you publish in Marketplace under the service requirements. Publication does not make your clients' records public.
4. Measurements, health and photos: separate choices
Clients make separate choices about body measurements, health information and progress photos. These options start disabled for new accounts, and you can continue without authorising them. Your choices and changes are recorded so they can be respected and evidenced.
You can change or withdraw these permissions in Privacy. Withdrawal prevents new contributions and the corresponding professional access; it does not by itself erase earlier history or affect the lawfulness of previous processing. You can view and request erasure of your data or exercise the rights described in this policy.
Consent to store these data, permission to share an area with a trainer and operating system permissions are different choices. A camera permission or professional relationship does not replace sensitive-data consent.
5. Sharing with a trainer and public information
Professional access requires an active relationship, the relevant sharing permission and, where applicable, sensitive-data consent. Each area has its own rules: training and measurement data do not necessarily have the same historical scope as photos. Authorising photos can make photos taken before the relationship began available.
When the relationship ends, professional access to your personal data ends. Minimum relationship history and content belonging to each participant are retained where applicable. Withdrawing access cannot retrieve files already downloaded; temporary links already issued can remain usable until they expire.
Your profile photo follows your chosen visibility. If you are a Trainer whose profile is actually published in Marketplace, the photo and published professional details can be seen by other users; once the profile is no longer published, your selected photo visibility applies again. Clients' private data and progress photos are not made public for that reason.
Each trainer is responsible for their professional decisions and any use of data on their own behalf. They must explain such uses and their legal basis where relevant and respect confidentiality and access limits. Contact TotalTrain about the platform and the professional about their own activities.
6. Support, administration and authorities
Authorised personnel manage accounts, incidents, rights, reports, appeals, subscriptions and security according to their role. Administrative tools do not provide general access to your chats, health information, progress photos or private plans. A case may include messages or evidence you or its submitter supply.
Technical operations can require limited data access to resolve a fault, maintain infrastructure or meet an obligation. Access must be limited to the necessary purpose and subject to confidentiality and controls. Data will be disclosed to authorities where there is a valid obligation or request.
7. Photos, files and device permissions
Progress photos are stored privately and accessed using access controls and temporary links. Profile photos follow the visibility rules described above. You can select the images you provide using your device's available options; operating system permission does not by itself authorise a trainer to view them.
The comparison tool's posture alignment uses ML Kit on the device. Images are processed locally for that analysis and are not sent to an AI provider for alignment. This is separate from storing them in your account. The SDK can exchange technical operational and update information with Google under its terms.
Review permissions in Android, iOS or browser settings. Refusing permission can make the feature requiring it unavailable. You do not need to grant photo or notification permissions to read this policy or contact us about privacy.
8. Notices, email and mobile notifications
Account and service notices can appear in the internal inbox and, depending on their type and your preferences, be sent by email or mobile notification. Necessary sign-in, security or account-management messages serve an operational purpose; they do not subscribe you to advertising.
On Android and iOS, installation identifier, notification token, platform, system permission, app version, language and time zone can be processed to register the device and route notices. Technical installation registration can exist even if you have not enabled the account's notification preference. You can review that preference and system permission separately.
Firebase Cloud Messaging and, on Apple devices, Apple's delivery services take part in delivery. The provider receives the necessary destination information and the notice content being sent. Depending on your settings, titles and text may appear on your lock screen. The current web version does not register push notifications.
Unlinking the device from an account does not automatically delete the technical installation identifier maintained by Firebase. Firebase retains that identifier until deletion is requested through its API; removal from live and backup systems can then take up to 180 days. This is separate from TotalTrain account deletion and pending-notification delivery expiry.
9. Service providers involved
Providers receive data according to their role. They act on TotalTrain's behalf for processing entrusted to them and can also have their own purposes, such as a store handling your purchase. The following links provide their information; they do not replace your rights against TotalTrain.
- Supabase: accounts and authentication, database, file storage, service functions and data updates.
- Cloudflare: web delivery and protection and Turnstile security checks where applicable. It also takes part in receiving and processing incoming email. Technical connection information and the message data needed for these functions are processed.
- Amazon Web Services, through Amazon SES and associated email services: sending messages and handling delivery incidents. Email addresses, content and metadata can be involved.
- Google/Firebase and Apple: mobile notification registration and delivery and the technical services of the SDKs used. Their involvement does not mean Google Analytics or advertising has been added to the app.
- Google Play and the App Store: app distribution, payment, subscription verification and management. Each store also processes its own account and payment-method data under its terms.
- YouTube and, for compatible links, Vimeo: external video playback. Opening an external player can send connection data to its provider and involve cookies or other technologies under its service and your settings. These videos have different conditions from TotalTrain's own hosted files.
10. Processing outside the European Economic Area
Some providers and their subprocessors operate internationally. Primary hosting in one region does not guarantee that technical support, delivery, notifications or all metadata are processed only there.
Safeguards depend on the service and recipient. Supabase, Cloudflare and Firebase processing agreements include standard contractual clauses or other applicable mechanisms; Cloudflare's agreement also addresses the Data Privacy Framework where covered. The specific safeguard must correspond to the transfer made, rather than a general statement about all providers.
You can request information about recipients and a copy of the applicable safeguards at soporte@totaltrainapp.com, subject to the limits needed to protect confidential information and third-party rights.
11. Data on your device and web browsing
The app can retain session data, language, appearance and region preferences, training or nutrition drafts and notification choices. It also uses temporary files and a cache of its own hosted videos. Some of this information stays on the device; use its lock and protect access if you share it.
Browser access retains necessary session data and preferences in browser storage. Security checks and external players can use cookies or other technologies under their service and your settings. You can review those providers' terms in the previous section.
Commercial website audience measurement through Cloudflare Web Analytics is explained separately, including its opt-out link. That system has not been incorporated as analytics of personal app records.
12. Retention and expiry
Accounts, plans, logs and communications are retained while necessary for the service or legal relationship. Ending a trainer relationship does not delete your account or every participant's history. Once processing is no longer needed, erasure or restriction must follow the applicable purpose and obligations.
Case content needed to handle the matter, its attachments and the minimum proof of its resolution are distinguished. The following periods have been defined for TotalTrain. Their operation must be completed and checked before this revision takes effect; they are not presented as automatic erasures already performed.
The period starts with the definitive closure or response communicated as specified for each case. Viewing or administratively saving a case does not restart it. If a case is genuinely reopened, the information necessary to handle it is retained and the new communicated closure starts the applicable period.
- Ordinary notices: a thirty-day criterion. Removal from the inbox depends on service cleanup; a notice disappearing does not prove erasure of every record of the underlying event.
- Pending mobile push delivery: no more than twenty-four hours from creation of the original notice, or earlier if the notice expires first. Retrying or sending to another device does not restart the limit. This delivery expiry does not reduce information available when opening the app or recall messages already accepted by the provider under another configuration.
- New recovery copies under our control: no more than thirty days from creation, without restarting the period on viewing, replication or a restore drill. Earlier copies are reviewed after a new recovery has been verified, to avoid removing the only useful copy. The primary accounting archive and preserved legal evidence retain their own purpose and period; provider-managed copies and logs follow their service cycles.
- Portable copy: the export package expires seven days after becoming available. Download expiry and physical file removal are different operations.
- Minimum proof of the contractual relationship after account deletion: five years as a baseline for minimum identification, dates and accepted terms. The starting date depends on when the relevant obligation becomes enforceable; account deletion or viewing a record does not restart that period. The proof is kept separately from ordinary use, with restricted access. A claim, interruption or special limitation period requires a documented review; this criterion does not extend retention of chats, health information, photos or all account data by default.
- Minimum proof of consent: while the relevant processing continues, the choice must remain demonstrable. Afterwards, three years as a baseline from the evidenced effective cessation of each purpose. The proof is kept separately from ordinary use with restricted access, covering minimum identification, choices and withdrawals, dates and available verifiable notice evidence; it does not include the measurements, health information or photographs. Capture, viewing or later account deletion does not restart the period. A specific obligation, claim or interruption requires relevant preservation and a documented review. This period is independent of contractual proof; unproven historical dates or notices are not invented.
- Ordinary support: twelve months from the communicated closure, to allow follow-up of the enquiry and the necessary actions taken.
- Rights requests: three years from the definitive response communicated, for minimum proof of handling: right requested, dates, identity verification performed, actions, response and evidence of delivery. This does not require retaining an identity document or the full export by default.
- Report evidence: twelve months from the final resolution communicated, once appeals have been resolved or their deadline has expired. Only evidence and context necessary for the case are retained.
- Decisions and appeals: two years from the definitive closure communicated, for the reduced reason, rule applied, dates, outcome and notification. While a measure remains in force, the minimum necessary to apply it is also retained; this does not by itself extend retention of all its evidence.
- Ordinary support attachments: thirty days after resolution or closure, except for reopening or a specific documented need. Their expiry is separate from the case period and must be accompanied by the appropriate physical removal.
- Preservation for an obligation or claim: only relevant information, with a documented reason, restricted access and expiry or review. That information is no longer available for ordinary use; the exception does not allow indefinite retention of the entire case.
- Progress photos of Clients without coverage: removal after one year is planned, with one-month and seven-day notices. This lack-of-coverage removal is not enabled. You can manage your photos and request erasure without waiting for that process.
- Accounting and tax supporting documents: six years from the last entry in the corresponding accounting books, subject to review of legal obligations or claims requiring a longer period. The archive is private, separate from ordinary app use, encrypted and access-restricted, and limited to the documents and data relevant to evidencing transactions, fees, taxes, refunds and payments. Account deletion does not restart the period. Unproven start dates require classification and review. This period does not apply to the account's complete history or all technical purchase data.
- Minimum proof of payments and the service after account deletion: five years as a baseline from the evidenced date when the relevant obligation can be claimed, kept separately from ordinary use with restricted access. Account deletion or viewing does not restart the period. A specific claim, interruption or obligation requires review and preservation of relevant evidence only; an unproven start requires classification, a responsible person and a next review. This does not include chats, photos, health data or complete store responses. Operational identifiers are removed when their evidenced need ends; they do not receive this period by default. This criterion is independent of the accounting archive and proof of contractual terms.
- Purchases, claims, security and legal obligations: limited information may need to be retained for applicable periods or while a claim or legal hold exists. Backups and provider logs have their own cycles; removal is not promised to coincide with an action on screen.
- Ordinary Website Support and Sales enquiries and email copies stored in TotalTrain: twelve months from evidenced closure of the matter. Archiving, changing status or a sending result does not itself prove closure. Genuinely outstanding matters and historical records without evidenced closure require review; an actual reopening invalidates expiry of the previous cycle. Removal does not delete messages from the sender's or owner's personal mailbox.
- Ordinary technical detail held by TotalTrain to investigate failures, suspicious access and sending results: ninety days from each event. Detail that is no longer needed is removed; minimum evidence of an obligation, incident, measure or claim and minimum identifiers still needed to prevent duplicate purchases, repeat sends or a second commercial trial are classified by purpose and kept separately. This period is not automatically applied to a record whose purpose or starting event cannot be evidenced.
- Calendar after account deletion: the other participant retains only the date, time and modality of past appointments, with a neutral label, while their own account exists. Notes, comments, instructions, location and links are removed from that history. Other active people's appointments and participation are respected; shared text that cannot be selectively removed requires review before removal is completed.
- When a Client's account deletion is executed, their Trainer's tasks and notes about them outside delivered plans are removed from ordinary use, respecting other Clients' data. Evidence relevant to an obligation or claim is preserved separately. The Client's own notes and records are removed with their account. Delivered plans retain their complete-content retention rule.
13. Requesting and cancelling account deletion
Clients and Trainers can manage deletion from profile Security or a browser without installing the mobile app. Both use the same account and request: changing device does not restart the period. Requesting or cancelling deletion requires authentication and password confirmation.
The account remains usable during a seven-day grace period. The date and status come from the server. You can cancel while the request is pending and execution has not started; cancellation is unavailable once execution starts. The seventh day makes the process eligible to start and does not mean every system is erased simultaneously.
Execution deletes account-exclusive data. The complete chats you participate in are removed from ordinary use for both participants. Only relevant evidence needed to handle a case, an obligation or a claim may be kept separately, with restricted access and for the corresponding period; the entire chat is not kept by default. Identifiers in the rest of shared history are removed or reduced, and necessary purchase, security, request or claim records can remain. That history requires specific handling; not everything retained is described as anonymous.
If a Trainer deletes their account, their Clients retain the plans already received with their complete content, including instructions, recipes and personalised photographs and videos. Access remains limited to the recipient Client under their permissions. Removal of the profile and its structured contact details is handled separately, without reducing the delivered content. If that content identifies its author, it remains personal information and is not considered anonymous. This functional copy is distinct from evidence kept separately for obligations or claims and does not authorise general administrative access. Applicable data and content rights remain in place; account deletion does not by itself resolve a specific request concerning those rights.
Received plans are retained while the recipient Client's account exists, under their history-access permissions. When that Client's account deletion is also executed, their copy is deleted. Other recipients' plans and files still needed for them are respected; only relevant evidence for a specific obligation or claim is kept separately, with restricted access and its own retention period. Removal of copies and files must be verified and does not necessarily occur simultaneously across all systems.
If you need a copy, request it through Legal and privacy or Support before deletion. Deletion can be postponed to prepare the copy and preserve its seven-day download period. The portable copy has a defined scope: it does not distribute routine or diet content, and some records are provided as a timeline. If an access or portability request requires further information, state this in the case for review.
Deleting the account does not itself cancel a store subscription renewal. Manage that renewal in Google Play or the App Store; the app will indicate whether cancellation is required first. If you cannot sign in, use password recovery or contact soporte@totaltrainapp.com to verify your identity. Do not send passwords or codes.
The deleted Trainer's professional name or alias is not retained as a separate historical label: a neutral deleted-account label is used. This does not rewrite signatures, credits, instructions or media included in delivered content, or establish that its remaining identifiers are anonymous. Internal references necessary for permissions, provenance and file removal remain restricted and subject to their purpose.
14. Your rights and how to exercise them
You can request access, rectification, erasure, restriction, objection and portability where applicable, and withdraw consent without retroactive effect. Use the rights channel in Legal and privacy or write to soporte@totaltrainapp.com. Explain your request; extra identity information will only be sought where necessary and proportionate.
We will respond within the legal deadline, generally one month after receipt. If complexity or the number of requests allows an extension, we will tell you the reason and extension within that first month. Exercising rights is free except in cases provided for by law.
You can complain to the Spanish Data Protection Agency or the competent supervisory authority without giving up other remedies.
15. Security and decisions
We apply authentication, session controls, account and relationship permissions, private file access and traceability of sensitive actions. No system guarantees the absence of all incidents. Protect your credentials and report unrecognised access to support.
Activity calculations and summaries support tracking and do not replace professional assessment. Significant moderation and privacy decisions are human and can be reviewed through the relevant channels. Decisions producing legal or similarly significant effects on you are not made solely by automated processing.
New moderation decisions may be appealed for six calendar months from their communication. The notice identifies the decision, deadline and review channel. An appeal submitted within the time limit is not automatically closed when a suspension ends. We do not apply a retroactive deadline to earlier decisions without an evidenced communication date.
16. Changes and versions
The review date and document identifier distinguish this revision from others. Significant changes to purposes, recipients or controls will be communicated before they apply; any necessary additional consent will be sought specifically.
The Spanish and English versions describe the same processing. Spanish is the legal reference without limiting your mandatory rights. For questions or to request this information in another format, write to soporte@totaltrainapp.com.
