Coach Maximus Privacy Policy

Effective November 8, 2026

Coach Maximus is a fitness planning, logging, and nutrition-estimate app provided by Leart Hiseni in North Macedonia. You do not need a Coach Maximus account, name, or email to use it. This policy covers the mobile app and explains the separate processing needed for optional cloud AI and web research, exercise media, app updates, advertising, analytics, purchases, and crash reporting. Features and controls can vary by app version. Privacy questions and requests can be sent to thecoachmaximus@gmail.com.

What stays on the device

Your training profile, plans, workout and set history, coach conversations, preferences, and progress photos are stored on your device. Basic planning and logging work offline. We do not upload your full workout database or progress-photo files to a Coach Maximus cloud account. Limited AI context and technical usage events are described below. We do not integrate with Apple Health or Health Connect, request GPS location, or request location permission. Network and advertising providers can receive your IP address and may derive approximate location from it.

Nutrition measurements

If you use Nutrition, the app stores your entered height, body weight, and activity level in local preferences. It uses these values with your selected gender and fitness goal to calculate calorie and macronutrient estimates on the device. Supported JSON backups include these saved measurements. They are not automatically attached to cloud AI requests; information you type into a coach message is sent with that message.

Optional Premium AI Coach

Before a cloud AI request, the app asks for permission and remembers your choice for the local profile. Your message and limited context are sent over HTTPS through our AWS-hosted API and Vercel AI Gateway to an inference provider. The configured primary model is DeepSeek V4.1 Flash; the inference provider selected by the gateway may vary.

Context can include your language, goal, experience, equipment, training restrictions, exercise preferences, current plan or plan draft, exercise prescriptions including sets, reps and weights, recovery estimates, a summary of recent workouts and progression, and excerpts or summaries of recent coach messages. This may contain fitness or health information you entered. We do not attach progress photos, body measurements, a full database export, purchase receipts, or advertising identifiers to the model prompt. Information you type yourself is included in your message, so avoid unnecessary sensitive details.

During ordinary generation, our API logs technical metadata such as model, timing, token usage, and error status, rather than prompt or reply content. Conversations and cached answers are saved locally. Vercel describes separate retention rules for its gateway and inference providers: its gateway does not retain prompts and outputs after completion, but provider retention and training controls are separate. Coach Maximus does not promise provider-level zero retention or that all providers exclude inputs from training. Not using cloud AI prevents new AI requests; local coaching remains available.

Web research and cited sources

For some questions about training methods or coaches, nutrition, supplements, or evidence and safety, cloud AI Coach may also use web research. Our API sends your current message through Vercel AI Gateway to the configured model to formulate a query for Perplexity Search. We do not attach your full training-context summary, progress photos, or saved nutrition measurements to that research request. Personal details you type in your message may nevertheless be included in a generated search query. Selected search results can be included in the model’s answer and displayed as source links; opening a link sends a request to that website under its own privacy practices.

Search processing and retention are separate from model inference. We do not promise zero retention or exclusion from product improvement for search requests. Vercel explains the separate treatment of search tools; Perplexity’s Search terms describe its search-data practices. Avoid including identifying or sensitive personal details in questions that may trigger web research.

If you confirm “Report response,” the selected reply and a report reason are sent to our API for safety review. The original prompt and training-context fields are not attached, but the reported reply itself may contain information from your conversation. Reports are stored in restricted application logs configured for a seven-day retention period.

Photos and notifications

Camera and photo-library access is used only when you add a progress check-in. Progress photos are stored on your device and marked to be excluded from cloud backups. Device transfers and your own exports may copy them. You can save or share a requested photo-comparison image separately; progress-photo image files are not included in the JSON backup. Depending on your operating-system and backup settings, other local app data may be copied by device backup or transfer services. This is separate from a Coach Maximus cloud account or sync service.

If you enable reminders, alerts are scheduled on the device. We do not send marketing push campaigns. Camera, photo, notification, and tracking permissions can be managed in your device settings.

Services that receive data

Exercise media and API hosting

AWS services, including Lambda, DynamoDB, S3, and CloudFront, provide our API, exercise media, and catalog updates. Requests can reveal your IP address, requested exercise, media file, or catalog language/version, selected media variant, and technical app/request information. Protected requests use an installation credential or review-access token, and purchase entitlement checks use RevenueCat identifiers. We use hashed identifiers and short-lived counters to prevent abuse and duplicate requests. These requests do not upload your local workout database or photo library. See AWS’s privacy notice.

Expo app updates

The app uses Expo’s EAS Update service to check for and download compatible app updates automatically. These requests can disclose an installation identifier, IP address, platform/runtime and update information, and applicable launch-failure information, including error text. This supports update delivery and recovery. Launch-error text may contain details of a failure and is processed separately from the Firebase Analytics and Crashlytics data described below.

The app has no separate update-data opt-out, and advertising choices do not disable update requests. Expo describes the data processed by EAS Update, including a three-day raw-request-log period for launch-error text; that period does not apply to all update records. See Expo’s privacy policy for its broader practices.

Google AdMob

The free app can show interstitial ads at natural breaks, such as leaving a completed workout or returning from exercise videos, and optional banners. AdMob may receive IP addresses and approximate location, advertising or app/device identifiers, ad interactions, and diagnostics for advertising, measurement, and fraud prevention. Advertising personalization depends on applicable consent and tracking choices. On iOS, the app requests App Tracking Transparency permission where appropriate. We do not send workout records, photos, body measurements, or coach conversations to AdMob. See Google’s privacy policy and Mobile Ads data disclosures.

Google Analytics (Firebase)

Firebase Analytics receives app and installation identifiers, device/app information, and usage events such as screens opened, a workout starting or finishing, a set being logged, a photo being added, video playback, and purchase success or failure. Event names can show which features you used; we do not attach workout weights, photos, chat text, training restrictions, or full fitness records. These events are associated with app-instance identifiers and are not described as anonymous. Analytics collection is enabled automatically in configured builds; the current app has no separate analytics opt-out. Advertising choices do not disable Firebase Analytics. See Google’s privacy policy.

Firebase Crashlytics

Crash reporting is enabled automatically in configured production builds. Firebase Crashlytics receives installation/session identifiers, device and operating-system information, app/runtime/update identifiers, and crash stack traces. Our JavaScript error reporter removes original error messages and avoids attaching requests, screenshots, conversations, profiles, or workout contents; native crashes are handled by the Firebase SDK. The app has no separate crash-reporting opt-out. Firebase describes its data and retention practices, including 90-day retention for Crashlytics traces and associated identifiers before removal begins.

App Store, Google Play, and RevenueCat

Apple or Google handles payment details. RevenueCat receives store receipts or purchase tokens, an app customer/installation identifier, and related purchase, entitlement, and device/app information to verify, restore, and manage Pro. We do not receive your payment-card number. Deleting local app data does not erase store or RevenueCat purchase records. See RevenueCat’s privacy policy, Apple’s privacy policy, and Google’s privacy policy.

Retention, deletion, and your choices

Local training records generally remain until you remove them or reset local data, subject to automatic housekeeping. Coach messages older than 90 days may be removed during maintenance. The app retains up to 26 progress photos and removes the oldest when that limit is exceeded. Temporary caches and unused inactive plans may also be cleared. These limits do not impose a 90-day deletion period on workout history.

Backups, imports, and sharing

Open Profile → Account → Backup & Restore to export or import a supported JSON backup. Backups include supported profile data, preferences, custom exercises, plans, and workout/set records, including saved nutrition measurements and training limitations. They exclude progress-photo files, coach conversations, downloaded videos and other media caches, and purchase state. The file is readable JSON rather than an app-encrypted archive.

Import replaces the corresponding local profile data, preferences, custom exercises, plans, and workout records rather than merging them. Photos and coach conversations are not restored from the JSON file; existing ones remain on the device. Purchase restoration is handled separately through your store account. You choose where to save or share backups, workout recaps, and photo comparisons using system file or sharing controls. Copies may remain in a selected folder, cloud-storage provider, or recipient app after local app data is deleted.

Use Profile → Account → Data → Delete local data to remove the local profile, plans, workouts, messages, preferences, and progress-photo files. We cannot retrieve local-only records from your device or recover them from a Coach Maximus cloud account.

Application logs, including confirmed AI reports, have a configured seven-day retention period. Abuse-prevention records are set to expire within up to three days; database expiry processing may take additional time. Providers retain advertising, analytics, purchase, and infrastructure data according to their service settings, linked policies, and applicable billing, security, or legal requirements. Deleting local data does not cancel a subscription, withdraw a previously sent report, or automatically erase data already processed by providers.

You can decline cloud AI permission and stop new AI and research requests by not using cloud coaching. Deleting local app data resets the saved cloud AI permission, along with your local records. Where required, ad privacy choices are available from Profile’s Privacy control; iOS tracking choices are also available in device settings. Ad and tracking choices do not turn off the separate analytics, crash, or update services described above.

Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing and withdraw consent where processing relies on it. Email thecoachmaximus@gmail.com for a privacy request, including a request to withdraw consent. We may need an app or purchase identifier to locate provider-held records; we cannot retrieve local-only records from your device. Do not email payment-card details or unnecessary health information. You may also contact your local data-protection authority.

We do not sell your workout database, photos, or coach conversations. Advertising partners receive the technical information described above and may use it for personalized advertising where your choices and applicable rules permit.

International processing

Our service providers may process data outside your country, including in the United States and other locations used by AWS, Google, Apple, RevenueCat, Vercel, Perplexity, Expo, and the selected AI inference provider. Their linked privacy and data-processing terms describe applicable safeguards. We do not promise that optional AI or web-research requests remain in a particular country.

Children

Coach Maximus is intended for adults aged 18 and over. We do not knowingly collect personal data from children. If you believe a child has provided data to our services, contact us so we can address it.

This website and policy updates

The public website is hosted on GitHub Pages; the host receives technical request information when you visit. Website-specific cookies and analytics are described in the Cookie Policy. We update this policy when our practices change and show the effective date above. In-app summary text remains available from Profile → About if this page cannot open.

Support | Terms of use