Fitle · Legal
Privacy Policy
At a glance
- We use account, profile and workout information to provide your requested fitness features. Optional Apple Health access has separate controls.
- Account-linked profiles and workouts are stored in the cloud, including in the United States. Raw Apple Health readings are queried on your device.
- We do not sell personal information, use it for targeted advertising, or provide health information to advertising partners.
- You can withdraw health-data consent or request deletion. Provider recovery copies and limited legally retained records may remain for the periods below. Deleting an account does not cancel an Apple subscription.
1. Who we are and what this policy covers
Andrii Kuts Mobile Inc., a Canadian corporation ("Fitle," "we," or "us"), is responsible for the information described here and acts as its controller where that concept applies. This policy covers the Fitle iOS app, getfitle.com, website forms and communications with our team. The website does not access your Apple Health database or app workout history.
Contact our Privacy Officer at support@getfitle.com for privacy questions, complaints or requests. Company and contact details are on Contact Fitle. This summary highlights key points; the sections below explain the full practices, including retention and deletion limits.
2. Information you provide
- Account: your account identifier, email, registration details, sign-in method and authentication information. Firebase Authentication handles email/password sign-in. Apple or Google sign-in supplies the account information you authorize; Apple may provide a relay email. We do not receive your Apple or Google password.
- Profile: your name and information you enter about age, gender, height, current or desired weight, activity, experience, goals, equipment and workout environment. Injuries, limitations and health conditions you provide can reveal sensitive health information.
- Workouts: generated plans, exercise selections, favorites, workout dates, completed or skipped activity, sets, repetitions, weights, exertion and feedback. We calculate progress and estimates such as workload, fatigue and readiness for personalization; they are not medical assessments.
- Profile photo: the image you select and save. Selecting it does not give us general access to your photo library.
- Communications: your contact details, message and attachments you email us. Website contact forms collect email, message, optional name and submission time; they do not accept attachments. Send only necessary information, not passwords, full payment details or unnecessary medical records.
Some setup answers are saved on your device so you can resume onboarding. Account-linked profiles and supported workout history are stored in our cloud database. Skipping optional details can limit personalization. Account information is needed for account-based features; paid features also require purchase authorization. You can correct supported profile details in the app.
3. Apple Health and HealthKit
Apple Health access is optional and requires Apple’s system permission. The current integration requests steps, active energy, move and stand time, body mass, BMI, body fat percentage, lean body mass, heart rate, resting heart rate, heart-rate variability and sleep analysis. We use supported, authorized readings to display metrics and inform fitness and recovery suggestions. Availability depends on your device, permissions and enabled features.
Raw HealthKit readings are queried on your device. Profile information you enter, workout plans and history are separately stored and uploaded for account features; plans can reflect recommendations influenced by those readings. With write permission, Fitle can save completed strength workouts and supported energy estimates to Apple Health, but not diagnoses or clinical records.
We do not sell HealthKit information, provide it to data brokers, or use it for advertising, advertising profiles or marketing. We use it for the health and fitness features you request. Any additional disclosure requiring permission will be explained beforehand.
Change permissions through Apple Health or iOS Settings. Revocation stops future authorized access but does not delete previously saved information. Deleting a Fitle account does not delete your Apple Health database; you can separately remove Fitle-created records there.
4. Technical information and website forms
Our infrastructure providers process IP addresses, device and operating-system information, installation identifiers, request times and service logs for sign-in, configuration, content delivery, reliability and abuse prevention. Network data can indicate approximate location; these features do not request precise GPS location. Firebase Remote Config uses an installation identifier; App Check uses device/app verification and temporary tokens to protect access.
General Firebase Analytics, automatic screen reporting, advertising identifier collection and automatic Crashlytics collection are disabled in this app version. Workout history and progress records remain part of the requested fitness service. Disabling collection does not erase historical records. The app displays no third-party advertising, and we do not sell personal information or share it for cross-context behavioral advertising.
Cloudflare delivers the website and processes request information, including IP address, URL, browser and request time. Technical logs and spam controls support security and troubleshooting. This website version loads no application-level analytics scripts or advertising cookies. Cloudflare may use necessary security/challenge cookies. Browser controls can restrict cookies, although blocking security cookies may affect access. An App Store campaign label, if present, is not your email or form contents.
Launch signup collects your email, source, submission time and confirmation of adult eligibility to send one launch email, not an ongoing newsletter. Support inquiries do not subscribe you to marketing. Withdraw a launch request by contacting the address above from your signup email when possible. Later ongoing marketing requires an appropriate separate choice. Website submissions are delivered through Resend to our Google Workspace mailbox; there is no separate submissions database, but both providers can retain copies.
5. Why we process information
- Create and secure accounts; store profiles and workout records; authenticate sign-in and handle account requests.
- Provide your profile assessment, personalize and adjust workouts, show activity and progress, deliver exercise media and schedule reminders you enable.
- Verify subscriptions and restore eligible paid access; keep account and privacy controls available without a subscription.
- Operate the website, deliver your requested launch notification, answer support/privacy requests and maintain service reliability.
- Prevent abuse, respond to security incidents and comply with applicable legal duties.
Personalization uses your answers, recorded activity and available health signals. Suggestions can be wrong; you may reject or modify them. They do not determine eligibility for insurance, employment, credit or medical care. Some health information can be sensitive: unauthorized disclosure could affect your privacy or expose information about your condition. Provide only information you want used for the requested features.
6. Consent and sensitive information
We explain our purposes and obtain consent required by applicable Canadian and US law. Health-data consent is separate from accepting Terms, and Apple Health has its own permission. Neither action authorizes unrelated advertising or every later use or disclosure. Where required, collection and sharing need separate consent. We may process limited information without consent when law permits or requires it, such as a valid legal demand.
Withdraw health-data consent in Profile → Privacy choices. Health features pause, while deletion remains available. Withdrawal stops the affected future processing; it does not itself erase existing records. An offline withdrawal must reach the server to affect other devices. Optional permissions can be declined, although a feature may require information necessary to operate. Our separate Consumer Health Data Privacy Policy explains applicable health-data rights.
7. Who receives information
- Google/Firebase: authentication, account-linked profile/workout storage, profile photos, app-integrity checks and configuration.
- Apple: chosen Apple sign-in, HealthKit services under your control, App Store purchases and subscription status. Chosen Google sign-in also operates under Google’s account policies. These platform services have their own responsibilities and terms.
- Cloudflare: website hosting, security, requests and associated technical logs, including processing form submissions.
- Resend (Plus Five Five, Inc.): delivery of website submissions, including submitted contact details, message/source and submission time. Google Workspace: receiving mail and support/privacy correspondence, including attachments you email.
- Professional advisers, authorities or a business successor: only where necessary and lawful, with applicable confidentiality, notice and consent protections. These are not blanket exceptions to health-data restrictions.
Each provider receives information needed for its role, not every category of your data. We require providers acting for us to protect information and use it within that role. Company access is restricted to authorized purposes. Provider policies explain their processing but do not replace our responsibility for Fitle’s practices.
8. International processing
Account-linked database records and stored profile photos are hosted in the United States. Authentication, website, delivery, security and mailbox providers may process information in the US and other countries where they or authorized subprocessors operate. Laws and lawful government access can differ from your location; we do not promise Canadian-only storage. Contact our Privacy Officer for applicable safeguards and, where available by law, a copy with confidential information protected.
9. Retention
We keep information only while needed for the stated purpose or a specific legal obligation. Account, profile and workout records support the account and saved history until deletion is requested or required. Guest setup drafts stay on your device outside cloud sync and app-managed device backups. They expire seven days after their last update and are removed when next read, or earlier through the relevant setup, withdrawal and deletion flows. Removing the app removes its local application data, not cloud records or device backups you control.
- Ordinary support correspondence: 12 months after the inquiry closes.
- Launch-notification requests: until the requested notification, then 30 days; removed earlier if you withdraw. Only limited evidence or a suppression record needed for a documented lawful purpose is retained afterward.
- Minimal consent evidence: three years after account closure. Minimal privacy-request records: three years after the request closes. These records do not include full health profiles or identity-document copies.
- Specific legal preservation: only the relevant information, with restricted use and review; removed when that reason ends. A possible future dispute does not justify keeping an entire health profile indefinitely.
Deletion from active services is separate from provider recovery copies. Deleted profile-photo objects remain recoverable for seven days before becoming eligible for permanent deletion. Google describes removal of deleted authentication data and data associated with a deleted installation identifier from live and backup systems within 180 days after the relevant deletion is initiated. Authentication IP logs are retained for a few weeks. Applicable legal deadlines still govern our handling of requests; provider defaults do not replace those duties.
Email delivery logs, received messages, technical logs and provider recovery copies have separate retention. Removing a delivery record does not erase our mailbox copy, and mailbox deletion may leave recovery copies. The schedule above is our policy, not a promise of automatic mailbox expiration. We apply it through our retention procedures. Contact us for service-specific retention relevant to your request. Information held independently by Apple or another account provider follows its own retention rules.
10. Your choices and deletion
Request account deletion in Profile → Delete account, or contact our Privacy Officer if you cannot use the app. A connection and recent sign-in may be required. Deletion removes the cloud profile/photo and account workout records, together with this device’s account-scoped workout records and pending changes. The authentication account is removed after account cleanup and the current device’s identifier-deletion request succeed. If a step fails, the app reports it so you can retry.
A limited record prevents older clients or pending uploads from recreating deleted data. Other devices must receive the deletion information to clear their account records. An offline device, or one unable to authenticate before receiving it, cannot be remotely erased by this flow. That cleanup does not cover all local copies left by older app versions or device backups. Recovery periods and limited legal retention are described above.
Signing out or uninstalling does not delete the cloud account. Account deletion does not cancel an App Store subscription: cancel separately through Apple. HealthKit access and Apple Health record deletion have separate controls. Website emails are also separate; identify any launch signup or contact message you want removed so we can locate mailbox and delivery records. No app account is needed for a website privacy request.
Depending on applicable law, you may request access, a copy or portability, correction or deletion; withdraw consent; or complain to a privacy regulator. Contact our Privacy Officer without sending your password. We may verify identity or a representative’s authority proportionately, respond within applicable deadlines, and explain any lawful refusal or extension. We do not penalize privacy requests, although features can require information necessary to provide them.
You can update supported profile details in Fitle, manage HealthKit and notification permissions in Apple Health/iOS Settings, and manage subscriptions in your Apple Account. Reminders use local notifications you enable. Canadian complaint routes include the Office of the Privacy Commissioner of Canada, BC Information and Privacy Commissioner and Quebec Commission d’accès à l’information, as applicable.
11. Additional regional rights
Where a US state privacy law applies, additional rights may include information about recipients, correction, opting out of sale, targeted advertising or certain profiling, limiting sensitive-data uses and appealing a decision. Contact our Privacy Officer with “Privacy appeal” where applicable. We explain the outcome and available complaint options. The separate health-data policy describes applicable Washington and Nevada rights and deadlines.
12. Adults-only eligibility
Fitle is for people in Canada and the US who are at least 18 and have reached their local age of majority, if higher. Parental permission does not create eligibility. The app uses an age check and local-majority declaration; its eligibility record contains an adult age band, confirmation, policy version and time, rather than the date of birth used for that check. This is self-declaration, not identity verification. Health-data consent and Apple Health permission remain separate choices.
Website forms require adult confirmation before input and submission, without asking for date of birth. Anyone, including an ineligible person or their parent/guardian, may email our Privacy Officer without using those forms. If ineligible information was collected, we stop that processing and take appropriate deletion steps, subject to limited legally necessary records. Before disclosing someone’s information, we verify the requester’s identity and authority and respect that person’s own rights.
13. Security
We use safeguards against unauthorized access, loss and misuse, but no transmission or storage method is completely secure. Protect your device and credentials and report suspected unauthorized access to us. When an incident triggers notification duties, we notify affected people and authorities as required. An incident can include unauthorized disclosure, not only malicious intrusion.
14. Changes to this policy
We publish updates with an effective date and provide appropriate notice of material changes. A new purpose requiring consent is explained before processing begins; continued use alone does not replace required consent. Reading this policy does not waive rights or authorize processing, and accepting Terms does not replace separate privacy permissions.