Who operates this service
DT Software, operated by Duc Ta Minh in Vietnam, provides this service. For support, privacy requests or legal enquiries, email contact@dtsoft.dev. The main studio website is dtsoft.dev.
Local records and optional cloud sync
Workouts, exercise sets, food logs, bodyweight, body measurements, targets, custom entries and preferences are stored on your device: in this browser for the web app, and on your iPhone for the iPhone app. Guest records stay on the device unless you export them or choose to copy them to an account. Signing in with Google or Apple uses Google Firebase Authentication, which processes account identifiers and basic profile information such as name, email and profile image. Records in an active account are sent to the FitArchive sync server (api.fitarchive.app) and stored in its database so they can be restored on your devices; the web app and the iPhone app sync the same account. Fitness and nutrition entries can reveal health-related information; enter only what you want the app to store. Water logs sync with your account like other records. On Android, you can also sign in with email and password through Firebase Authentication. This is sign-in only for accounts we create; the app does not offer email account registration. Food searches may send the words you type to our food search server to find more foods, without an account token or device identifier. The search service does not write query or IP-address logs. It uses temporary, salted hashes of connection addresses in memory to limit requests. Hosting providers still process ordinary connection information as described below.
Why we process information
We use records to provide the log, calculate your summaries and run the sync you request. We process support messages to answer you and connection information to operate and secure the service. Where applicable, these purposes rely on providing the requested service, legitimate interests in support and security, or legal obligations. Optional analytics relies on your consent. Where health-data processing requires separate explicit consent under applicable law, that permission must be obtained separately; this notice is not itself consent.
The iPhone app
The FitArchive iPhone app keeps the same kinds of records as the web app on your iPhone and syncs them only while you are signed in. It has no advertising and does not track you across other companies’ apps or websites; its privacy manifest declares no tracking. It sends usage analytics only if you allow them, as described under “Optional usage analytics”. Apple distributes the app through the App Store. If you allow sharing with app developers under Analytics & Improvements in your iPhone settings, Apple may give us crash reports and aggregated statistics; these do not contain your FitArchive records.
Sign in with Apple
If you use Sign in with Apple, Apple confirms your identity and shares an account identifier and the email address you choose, which may be a private relay address that forwards to your real address. If Apple provides your name, it is saved once as your account’s display name. Apple processes this information under its own privacy policy. When you delete your FitArchive account, we also revoke FitArchive’s Sign in with Apple authorization. Stopping Sign in with Apple for FitArchive in your Apple Account settings does not delete your FitArchive account or synced records; use Delete account for that.
Apple Health
On iPhone, you can choose to connect FitArchive to Apple Health. Each kind of data has its own switch, all off by default, and iOS asks for your permission when you turn one on. FitArchive can write your finished strength workouts with their start and end times (without calorie estimates), your bodyweight, your waist measurement, and the food you log as nutrition entries with energy, protein, carbohydrates and fat. With bodyweight on, it also reads bodyweight saved by other apps or devices to fill days without a FitArchive weigh-in. With body fat or lean mass on, it reads those readings from other apps or devices, such as a smart scale, and adds them to that day’s weigh-in; only if you also choose to, it writes the body fat and lean mass you type to Health. Health data is used only to provide these features. It is never used for advertising or marketing and never sold. Raw Health readings are never sent to our server or shared with third parties. Only FitArchive’s own records sync as normal app data; for example, a weigh-in imported from Health becomes a FitArchive weigh-in and syncs with your account when you are signed in. If you separately allow Pro reports, a report’s minimized weight trend can include those weigh-ins, as described under Optional Plus and Pro AI features. Turn each kind off under More → Apple Health, or revoke access in Settings › Privacy & Security › Health › FitArchive. You can review or delete data FitArchive wrote to Health in the Health app. With your permission, FitArchive also reads sleep from Apple Health; it stays on your device and is not synced.
Progress photos
Progress photos stay on the device where you add them: in browser storage for the web app, or on your iPhone for the iPhone app. They are never uploaded or synced and are not included in JSON backups. On iPhone, FitArchive uses the camera or your photo library only when you choose to add a photo. Removing a photo, clearing browser data or deleting the iPhone app removes photos from that device.
Reminders and notifications
The iPhone app can remind you about training days, logging food, a weekly weigh-in, a training streak at risk and the end of a rest. Each reminder is off until you turn it on. Reminders are local notifications: they are scheduled on your iPhone and not sent from a server, and their settings stay on that iPhone. Change them under More → Reminders, or turn notifications off in Settings › Notifications › FitArchive. The web app does not send notifications.
Optional usage analytics
Public pages use Cloudflare Web Analytics for traffic measurements. With your separate permission, the Google Analytics browser tag counts visits to public pages and the private web app. On the home page, it also records which App Store, Google Play, web app, demo or Plus-interest button you click, with the page language and the device type (iPhone or iPad, Android, or desktop). Public page views may include page URLs, referrers, analytics cookies and device or connection data. Private-app visits use only a generic /app/ page address and title; workout, food, account and screen details are excluded. The demo is excluded. Change this choice in the public-page footer or under More in the web app. Optional app feature events are sent to Google Analytics through our server only after you separately opt in under More → Help improve FitArchive, if that feature is configured. In the web app, those events use a temporary random session identifier. In the iPhone app, nothing is sent until you choose Allow on the “Help improve FitArchive” card or turn on More → Help improve FitArchive; this choice is separate from Apple Health permissions and stays on that iPhone. The iPhone app then sends the same kinds of feature events, plus a tap on “Notify me about Plus”, with a random identifier that is replaced every week and whenever you turn sharing off. App feature events do not contain account IDs, names, body measurements, targets, food or exercise details, photos, notes, URLs or referrers. Turning sharing off stops new events at once.
Service providers and international processing
Hosting and security providers process connection information such as IP address, browser details, request time and requested resources to deliver and protect the service. Cloudflare provides the public website infrastructure. Google Firebase Authentication handles account sign-in. Google Analytics receives the optional visit counts and usage events described above. Apple distributes the iPhone app and verifies your sign-in when you use Sign in with Apple. When enabled, RevenueCat, Inc. (United States) processes pseudonymous store purchase records for subscription revenue and retention statistics as described below. If you contact us, email providers process your address and message. Providers may process information outside your country under their applicable terms and safeguards. We do not sell your personal data. Information may also be disclosed where required by law or necessary to protect legal rights and service security.
Export, deletion and retention
Use More → Your data to export a backup or CSV, or to restore a backup; on iPhone, backups are saved to and opened from Files. You can edit records in the app. To remove guest data, export what you need and clear FitArchive site data in the browser, or delete the iPhone app. For a synced account, use the Delete account control under More on the web or in the iPhone app; signing out, clearing browser data or deleting the app alone does not remove server records. Deleting an account first saves a backup to your device, then deletes your synced log from the server, deletes your sign-in account, revokes FitArchive’s Sign in with Apple authorization if Apple is linked, and removes the account’s records from that device. Individual record deletions may retain deletion markers for sync. A one-way account-identifier hash remains to prevent deleted accounts from being recreated by stale devices. Copies may remain in rotating backups until those backups expire. If part of the sign-in cleanup fails, the app displays a warning; contact us for help. Files you exported, data already written to Apple Health and copies on other devices need to be removed separately.
How long information is kept
Information stored only on your device remains until you delete it, clear site or extension data, delete the iPhone app, or your browser removes it. Downloaded files remain wherever you save them. Support correspondence is kept for as long as needed to handle your request and related legal obligations. Hosting and analytics records follow the provider and service retention settings; withdrawing analytics consent stops future collection but does not automatically erase earlier events. Contact us about information we hold.
Your choices and requests
Depending on the law that applies to you, you may ask to access, correct, export or delete personal data, restrict or object to processing, or withdraw consent. Email contact@dtsoft.dev and identify the service and request; do not send passwords or sensitive records. We may need proportionate identity verification. You may complain to the data-protection authority with jurisdiction over your situation.
Children and security
The service is not designed specifically for children. If you believe a child has sent us personal information that should be removed, contact us. We use access controls and security measures appropriate to the service, but no storage or transmission method can be guaranteed completely secure.
Optional Plus and Pro AI features
Plus and Pro are optional subscriptions offered in supported versions of the iPhone and Android apps. After separate permission and an explicit request, FitArchive sends your meal description and relevant food-catalogue context, a selected resized meal photo and optional portion hint, or minimized report aggregates and a selected report topic to Anthropic for processing. Report weight trends can include weigh-ins imported from Apple Health. Report question text is sent to FitArchive to check its scope; it is not stored or forwarded to the AI provider. AI custom foods made from a description or photo use the same processing and consent as AI meals. Plus voice meal input uses the phone’s system speech-recognition screen on Android. FitArchive receives only the resulting text, never audio. On iPhone, Apple’s speech recognition runs on the device where supported; otherwise audio goes to Apple’s servers after a one-time notice. FitArchive does not store audio or receive it on its servers. The resulting text is handled like a typed meal description. The AI plan builder in Plus and Pro requires separate plan consent (version 2026-10-29-pro-plan). Only after that consent, it sends typed plan text or your chosen profile to Anthropic. The profile includes experience, goal, days per week, session length, equipment and any notes, plus a short summary of your last 4 weeks of training: up to 6 best lifts (estimated one-rep max) and your 3 least-trained muscles. FitArchive does not store the builder’s input or reply on its server. Plans you save sync like other plans. If a plan or Pro answer is lost in transit, retrying the same request within 15 minutes of success re-runs it once without storing its text on our server. Requests explicitly use US-only inference. Our Anthropic organization has 30-day default input/output retention, with applicable safety and legal exceptions; we do not claim zero retention. Do not include private information unrelated to your meal, report or plan. Photo location and camera metadata are removed on your iPhone and again on our server. Progress photos remain local and are never used for AI. You can withdraw AI permission in Settings, which stops future requests. Unconfirmed meal text, images and validated drafts stay in protected local storage for up to 24 hours, excluded from backup and sync, and are removed on confirmation, discard, expiry, account exit or withdrawal. Confirmed meals become ordinary records. FitArchive stores consent and request/usage metadata, including quota device identifiers, model, token counts, cost and status, but not raw meal/photo prompts or model responses on its server. So that a meal estimate isn't lost when your connection drops, the server keeps the validated draft only (food names, amounts and nutrition) for up to 24 hours, and deletes it when you save the meal, after 24 hours, or with your account. Saved Pro reports contain checked summaries, remain readable after subscription expiry and can be removed through account deletion. Authored report questions are not stored as raw prompts. These estimates and explanations require your review; they are not medical advice or qualified nutrition/training approval.
Subscription analytics
When enabled, our server sends RevenueCat, Inc. (United States) the App Store or Google Play record of each Plus or Pro purchase, renewal or restore — product, price, store and dates — under a pseudonymous ID derived from your account. RevenueCat processes it only to give us subscription revenue and retention statistics. In the iPhone and Android apps, RevenueCat's software (SDK) also runs once you are signed in. It sends store purchase records under the same pseudonymous ID. On iPhone, technical data includes app version and build, device model, operating system, language and region, and Apple's identifier for vendors (IDFV). On Android, it sends Google Play purchase tokens and product identifiers, with app version and package name, device model and brand, Android version, language and region, storefront and SDK versions, and whether the app is in the foreground or background. We disable Android attribution identifier collection and do not ask the SDK to collect an advertising ID or Android ID. RevenueCat also receives your IP address when either app connects. The SDK is configured only after sign-in and is not used for advertising or cross-app tracking. Signing out or deleting your account stops our app's purchase reporting and requests SDK logout; the already configured SDK may still send lifecycle or store-purchase updates under its cached ID, or a random anonymous ID after SDK logout, until the app process exits. We never send your email, name, workouts, food, body or health data to RevenueCat.
AI assistant connections
You can choose to connect FitArchive to an AI assistant such as Claude (Anthropic, PBC, United States) or ChatGPT (OpenAI, L.L.C., United States). This is a transfer you direct: after you sign in and approve on our consent page, the assistant can read the categories you allow (workouts, sets and plans; food log, macros and targets; body weight and profile, including weigh-ins imported from Apple Health or Health Connect) and, on paid plans, add food logs, workouts and plans to your account. Body fat and lean mass imported from Apple Health or Health Connect are shared only if you turn that option on, and progress photos are never shared. The assistant's provider processes what it reads under its own terms and privacy policy. Each connection uses tokens that we store only in hashed form. You can end a connection at any time on fitarchive.app/connect, in the assistant, or by withdrawing AI permission in the FitArchive app; withdrawing AI permission or deleting your account ends every connection at once.
Ask AI
Ask AI answers general questions about training, food and how to use FitArchive, using only FitArchive's own guides. It requires separate consent (version 2026-10-29-ask-ai). When you tap Ask, only the question you type is sent to Anthropic, with US-only processing, together with the relevant FitArchive guide text. Your workouts, food, body data, photos and account details are not sent. Don't type health or personal details. Questions about pain, injuries or medical topics are refused on our server and never sent. Anthropic retains inputs and outputs for 30 days by default, with safety and legal exceptions. FitArchive doesn't store your questions or answers; it keeps only the usual request metadata (time, model, token counts, cost and status) to apply the daily question limit. Answers stay on screen and are cleared when you leave. You can withdraw in More, which also removes this consent.
Changes and questions
The date on this page identifies this version. We will publish changes here and provide additional notice of material changes where required. Contact us first so we can try to resolve a concern. Applicable mandatory laws and your right to seek remedies through competent authorities remain unaffected.
Android app and Health Connect
The Android app supports the same local log and optional account sync. Health Connect sharing is optional: scale weight, body fat and lean mass can be imported, and weight, finished workouts and nutrition can be exported only with the permissions you choose. Foreground access checks current permissions. Progress photo bytes and private adaptive screening do not enter Health Connect or account sync. Local reminders do not require account sync. Device-only AI drafts, images, descriptions and screening are held outside backup storage; only meals you approve become diary records. Google Play purchase verification and Play Integrity protect activated paid features. Android public paid and adaptive activation requires separate product, privacy and qualified nutrition approval. Optional anonymous Android feature events require device consent and a separately enabled release configuration; they contain no records or account identifiers. Optional Pro reports require separate report permission before minimized training, nutrition and weight aggregates are sent to the provider. Report questions are checked by FitArchive without forwarding the authored text; the provider receives only the selected topic and checked report metrics. Checked saved reports and user-selected recommendation changes may sync with your account. Private screening and progress photo bytes remain on the device. Withdraw report permission in the app to stop new report requests; saved reads and safe Undo remain available. With your permission, FitArchive also reads sleep from Health Connect; it stays on your device and is not synced.