How FitSimp handles your data.

01

Information stored on your device

FitSimp stores your training data on your device. Optional cloud Coach and Sync use the specific data described in their sections below.

• Workout plans, exercise history, sets and reps, body weight entries, personal records, notes, exercise photos, gyms (with their equipment and locations), custom icons, theme preferences, and bug-report log files are stored in the app’s local SwiftData store and Application Support directory.
• Widgets and Live Activities use a shared container on your device. The Apple Watch companion exchanges workout state with your paired iPhone through WatchConnectivity.
• Sign in with Apple requests your email address, not your name or contacts. Advertising identifiers are collected only for the optional Meta measurement described below.

02

Optional FitSimp account

From version 1.1.2, you can create an optional account with Sign in with Apple. From version 1.1.3, you can also create one with an email address and a password. From version 1.2.0, you can also use Sign in with Google. You can continue using FitSimp without an account.

• Account: a random FitSimp account ID, your email address, the app language, and the times you created and last used the account. With Sign in with Apple or Google, we also store your verified provider user identifier. For Apple, we store your email address only when Apple provides a verified address that is not a private relay address. For Google, we store a verified Gmail or Google Workspace address as an account identity, as described below.
• Password: if you use email sign-in, we store a salted Argon2 hash of your password. We do not store the password itself.
• Device ID: when you sign in, the app sends a random device identifier that it creates and keeps in the Keychain, and a generic device name (for example, “iPhone”). The service keeps them, and the times the device was first and last used, to show the list of signed-in devices. An account can have a maximum of 3 signed-in iPhones and iPads. The paired Apple Watch does not count toward this limit.
• The device identifier is linked to your account. We use it only for app functionality. We do not use it to track you. It is not the advertising identifier that Meta can receive (see “Optional advertising measurement”).
• Sessions: sign-in tokens. A refresh token lasts a maximum of 365 days, and signing out revokes it.
• Apple authorization: the service stores an encrypted Apple refresh token so it can revoke the authorization when you delete your account.
• Purchase records: from version 1.1.5, if you have a FitSimp Pro purchase, the service keeps its App Store record with your account. “Subscriptions and payments” below describes this record.
• We use account information to operate and protect your account. We do not send your account email address or FitSimp account ID to Meta.
• Signing in alone does not upload your workout library. Cloud Coach requires an account and sends the context described below when you use it. FitSimp Pro Sync uploads supported training records only when you turn it on.

03

Sign in with Apple

Apple authenticates you. FitSimp does not receive your Apple password.

• Apple supplies your verified identity and, when provided, your email address. If you choose Hide My Email, Apple supplies a private relay address instead. The account service does not store a private relay address.
• FitSimp does not ask you to create a password or send an email verification code for Apple sign-in.
• We do not send marketing email or newsletters, and we do not add your address to a mailing list.

04

Sign in with Google

From version 1.2.0, Google can authenticate you in a web sheet. FitSimp does not receive your Google password.

• FitSimp requests only your Google account identifier and email address (openid and email). We use this information to sign you in and operate your FitSimp account, not for advertising.
• We store your verified Google account identifier. A verified Gmail or Google Workspace address is stored as an account identity and can connect you to an existing FitSimp account with the same verified address. Other verified Google account email addresses are returned to the app for display and do not automatically link accounts.
• The account service exchanges a one-time authorization code to verify your Google identity. It does not retain Google access or refresh tokens.
• Google processes your sign-in under its own privacy policy. Deleting your FitSimp account removes its stored Google identity under the retention and deletion policy below.

Read Google’s Privacy Policy

05

Sign in with email

From version 1.1.3, you can create an account with your email address and a password.

• When you create an account or reset your password, the app asks for your email address. We send a six-digit verification code to that address. The code expires after 10 minutes.
• We create the account only after you enter the code. Thus only a person who can read the email at an address can create an account with that address.
• Resend, an email delivery service, sends the code email from no-reply@noreply.nombi-sioi.com. Resend receives your email address and the email that contains the code. The verification code email is the only email that the account service sends, and it sends one only when you ask for a code.
• We keep only a hash of each verification code. If you do not complete the sign-up, the code record expires 1 hour after the code expires, and the database then deletes it.
• A password must have at least 12 characters. When you choose a new password, the service checks it against the Pwned Passwords list of breached passwords from Have I Been Pwned. The service sends only the first 5 characters of the SHA-1 hash of the password. Your password and its full hash do not leave the service.
• To stop abuse, the service accepts a maximum of 5 code requests and 5 sign-in attempts for each email address in 10 minutes. A code accepts a maximum of 5 wrong entries.
• If a code email bounces or you mark it as spam, Resend adds your address to a suppression list. We then send no more email to that address.

Read Resend’s Privacy Policy

06

Cloud Coach

From version 1.2.0, Coach can answer training questions and prepare suggestions. Cloud Coach requires a FitSimp account.

• When you use a cloud answer, the app sends your message, up to 8 earlier conversation turns, a short training-habits summary, your locale, and the app version to the FitSimp service. If a planning tool is used, it also sends the requested planning intent and the resulting workout draft or gym proposal rows.
• Amazon Bedrock on AWS processes this text and produces the answer in the United States (us-west-2). A Bedrock safety guardrail checks the same text. We use it to answer your request, not for advertising.
• The app does not attach your raw set history, HealthKit records, usual training time, or location to Coach requests. Information you choose to type into a message is included in that message. Coach does not read the Sync cloud copy.
• The FitSimp service does not store conversation content. It keeps a per-account daily turn counter that expires after 3 days, plus the operational records described under Security and service logs.
• Dictation is processed on your device. The Coach request contains the resulting text, not your audio. Answers handled entirely by an on-device model or parser do not send a Coach request to the service.
• Meta never receives your Coach messages or answers.

07

Optional Sync

From version 1.2.0, FitSimp Pro users can turn on Sync for up to 3 signed-in iPhones and iPads. Signing in does not turn it on automatically.

• Sync uploads a cloud copy of supported records: workouts with their exercises, sets, notes, effort ratings, calorie totals, recorded heart-rate samples, and session positions; workout templates; exercises; equipment; brands; muscles; gyms with their equipment and locations; and attached photos. The copy is linked to your FitSimp account and used to keep these records consistent across your devices.
• AWS stores sync records in DynamoDB and photo files in S3 in the United States (us-west-2). Coach does not read this cloud copy, and we do not send it to Meta or use it for advertising.
• Turn Off Sync deletes the cloud copy and its photos. Each device keeps its local data. Deleting a record while Sync is on propagates the deletion; deleted sync records remain in trash for 30 days. Database backups can retain deleted records for up to 35 days.
• A lapsed FitSimp Pro subscription stops syncing but does not itself delete the cloud copy. Account deletion and the inactive-account retention policy below also delete the cloud copy.
• The Apple Watch exchanges workout state with its paired iPhone and does not count toward the 3-device limit.

08

Security and service logs

The service keeps operational records to run accounts, Coach, and Sync and to stop abuse.

• The service uses your IP address to limit repeated attempts (a maximum of 5 attempts in 10 minutes). It stores only a SHA-256 hash of the IP address, and deletes that record after about 10 minutes. It does not log your IP address.
• Service logs record events such as “device removed” or “account deleted” with the account ID only. They do not contain your email address or your workout data. We keep service logs for 1 month.
• Amazon Web Services hosts the account service and processes IP addresses to deliver requests.

09

Optional advertising measurement

From version 1.1.2, FitSimp uses the Meta iOS SDK to help measure and improve advertising for FitSimp.

• After onboarding, FitSimp asks permission through Apple’s App Tracking Transparency prompt before it starts Meta measurement. You can decline and continue using every app feature.
• If you allow tracking, Meta receives device identifiers, including the advertising identifier where available, and basic device, app, and network information. Meta also receives app installation, activation, and session activity.
• The Meta SDK starts only after you allow tracking. Its privacy manifest also declares crash data and other data, such as the device and app details that each event carries. FitSimp turns off the crash and error reports of the SDK, and FitSimp’s own code sends no crash data to Meta. Because the SDK declares these data types, the FitSimp App Store privacy details list them as not linked to you and not used for tracking.
• Meta may combine this information with information from its services and other sources for advertising measurement and personalization. Meta’s Privacy Policy explains how it uses this information.
• We do not send workouts, exercise choices, weights, heart rate, HealthKit data, or workout notes to Meta. We also exclude account email addresses and FitSimp account IDs. This integration does not send purchase or subscription events.
• Change your permission in iOS Settings → Privacy & Security → Tracking. If you revoke permission, FitSimp stops subsequent advertising measurement. This does not erase information that Meta already received.
• Meta’s Privacy Policy explains its retention practices and privacy controls. The Apple Watch app, widgets, and Live Activities do not send Meta events.

Read Meta’s Privacy Policy

10

Apple HealthKit

HealthKit access is optional and controlled by you.

• With your permission, FitSimp reads heart rate, active energy burned, and workout sessions from Apple Health, and writes completed workout sessions (including pause/resume events) back to Apple Health.
• Heart rate is shown live during workouts and used to compute summary stats; active energy is used to display calorie totals; workout reads are used for the history view.
• Without Sync, HealthKit data stays on your device. From version 1.2.0, if you turn on Sync, the heart-rate samples and calorie totals stored in a workout are included in its cloud record. Only the device that recorded a workout writes it to Apple Health; receiving a synced workout does not write a duplicate. Coach does not receive HealthKit records, and Meta never receives them.
• You can review and revoke HealthKit permissions at any time in Settings → Health → Data Access & Devices → FitSimp.

11

Camera, Photos, Location, and Notifications

These permissions are requested only when you use the feature that needs them.

• Camera: used to capture photos for individual exercises in your library. Photos are stored locally inside the FitSimp app container. From version 1.2.0, photos attached to supported records are also uploaded if you turn on Sync.
• Photo Library (add-only): used when you save a workout summary image from FitSimp to your Photos library. FitSimp does not read your existing photo library.
• Location (only while you use the app): from version 1.1.5, FitSimp asks for location access when you tap “Use Current Location” for a gym. It uses the location to save your gym and suggest a nearby gym. From version 1.2.0, it also reads the location once at workout start if you already granted that permission; it does not show a new location prompt then. FitSimp never reads location in the background. The location stays on your device unless you turn on Sync, which includes gym locations and recorded session positions in the cloud copy. An exported backup includes both. FitSimp sends no position to a geocoder and does not use Wi-Fi names, Bluetooth scans, or IP lookups to determine your gym. Location is not sent to Coach or Meta.
• Notifications: used for local workout reminders that you configure. From version 1.2.0, a training-time reminder can use your usual training time, learned on your device and kept there. Reminders are scheduled on-device via the iOS notification system; no push notification server is involved.

12

Apple Watch companion

The optional FitSimpWatch app talks only to your paired iPhone.

• Workout state (start/end, current exercise, timer) is exchanged between the iPhone and Apple Watch through Apple’s WatchConnectivity framework on your devices.
• If you start a workout on Apple Watch, it can read heart rate locally through the watch’s HealthKit store. The Watch sends workout state to its paired iPhone. From version 1.2.0, that iPhone can include the workout and its heart-rate samples in the cloud copy if you turn on Sync.

13

Subscriptions and payments

Apple processes FitSimp Pro purchases. From version 1.1.5, if you sign in, the FitSimp account service also keeps a record of your purchase.

• Apple processes subscription purchases and renewals through your Apple Account. FitSimp does not receive your payment card details.
• From version 1.1.5, after each sign-in with Apple or email, and from version 1.2.0 with Google, the app sends the verified App Store transactions on your device to the FitSimp account service. The app sends them only if you have a FitSimp Pro purchase.
• The service confirms each transaction with the App Store. Then it stores the product ID, the original transaction ID, the subscription state, the expiry date, the App Store environment, and the time of the check.
• The service keeps this purchase record with your account, so the record is linked to you. We use it only to connect your FitSimp Pro purchase to your account. We do not use it for tracking or advertising, and we do not send it to Meta.
• Your access to FitSimp Pro comes from Apple’s StoreKit framework on your device. The purchase record on the service does not change your access. Product identifiers are com.nombi_sioi.fitsimp.pro.monthly and com.nombi_sioi.fitsimp.pro.annual.
• When you delete your account, we delete its purchase record. Account deletion does not cancel your subscription. You can manage or cancel your subscription at any time in Settings → Apple ID → Subscriptions.

14

Diagnostics and crash reports

FitSimp keeps its own diagnostics on your device until you decide to send them.

• In TestFlight and debug builds, FitSimp subscribes to Apple’s MetricKit framework so that crash, hang, CPU, and disk-write diagnostics from the previous launch can be saved locally under Library/Caches/Diagnostics. App Store builds do not persist these payloads.
• The optional Meta integration measures app installs and sessions as described above. FitSimp does not send its bug-report logs, workout data, or locally stored MetricKit reports to Meta. If you allow tracking, the Meta SDK can collect crash data, as “Optional advertising measurement” describes.
• If you opt in to share diagnostics with Apple at the iOS level, your device may include FitSimp in those reports under Apple’s privacy policy. This is controlled by iOS, not FitSimp.
• When you tap “Report a Bug” inside FitSimp, the app prepares an email draft to support@nombi-sioi.com that includes app version metadata and, if available, a JSONL log file plus any locally stored MetricKit diagnostics as attachments. You choose whether to send it and you can remove any attachment first.

15

Data we receive when you contact us

• If you email support@nombi-sioi.com, we receive your email address and the contents of your message so we can reply.
• We do not use that information for marketing and we do not share it with third parties.

16

Sharing and disclosure

• Amazon Web Services hosts our account service and processes cloud Coach requests through Amazon Bedrock and its safety guardrail in the United States (us-west-2). AWS DynamoDB and S3 store the optional Sync cloud copy in the same region. Apple verifies your identity when you choose Sign in with Apple. From version 1.2.0, Google verifies your identity when you choose Sign in with Google. The account service asks Apple’s App Store to confirm the FitSimp Pro transactions that the app sends. Before we delete an unused account, the service asks the App Store for the state of its subscription.
• Resend delivers verification code emails. When you choose a new password, Have I Been Pwned receives the first 5 characters of the SHA-1 hash of that password.
• If you allow tracking, we share the device and app activity information described above with Meta for advertising measurement and personalization.
• We do not share your training data, Coach messages, or Sync cloud copy with Meta. Your FitSimp account email address and account ID are not sent to Meta.
• Any data you choose to export (CSV, screenshots, share sheets) is sent through the destinations you pick at that moment.

17

Retention and deletion

• To delete your account, open Profile → Account → Delete Account in the app. FitSimp revokes its stored Apple authorization, if you have one, and deletes the server account, email address, password hash, stored provider identities (including your Google account identifier), device records, purchase records, and sessions. From version 1.2.0, account deletion also deletes the Sync cloud copy and its photos. Your local workouts and Apple Health data remain on your devices.
• Our database backups keep the records of a deleted account for up to 35 days, and then those records are gone.
• For about 10 minutes after we delete an email account, the account service keeps a SHA-256 hash of the email address, so that a sign-in that started before the deletion cannot finish.
• Until October 15, 2026, the service kept a record of each deleted account for 30 days. For an email account, that record held the email address. The database deletes the last of these records by about November 17, 2026.
• Signing out revokes the sign-in tokens of that device.
• Account deletion does not erase information already received by Meta. Use the tracking permission and Meta privacy controls described above to manage advertising measurement.
• We keep an account while it is in use. An account is in use when a device signs in to it, or when FitSimp on a signed-in device connects to the account service, for example when the app opens. We delete an account that no one has used for 24 months and that has no active FitSimp Pro subscription. If the account has a FitSimp Pro purchase record, we check the subscription with Apple before we delete it. This inactive-account deletion also removes any Sync cloud copy and photos.
• Delete the FitSimp app to remove all locally stored training data, exercise photos, logs, and diagnostics from that device. Deleting the app does not delete your account.
• You can also wipe individual sections (logs, diagnostics, workout history) from inside Profile → Data Management without uninstalling.
• Restoring an iCloud or device backup that includes FitSimp will restore the data captured in that backup. Workouts already written to Apple Health remain in Apple Health and must be removed there separately.
• Without Sync or a backup you kept, FitSimp cannot recover training data lost from your device. Sync is not a substitute for a backup: changes and deletions can propagate between devices. Deleted sync records can be restored from the 30-day trash while available; once the cloud copy and your backups are gone, we cannot restore them.

18

Children

• FitSimp is not directed at children under 13. We do not knowingly collect data from children.