iOS privacy policy

Scope and account separation

Veyrazo is a fitness and wellness app from Sloth Bloom. This notice describes the iPhone and Apple Watch experience. Features may differ by release. A shared sign-in identity, profile photo or friendship can be used across platforms, while iOS fitness records and onboarding remain separate from Android. Deleting the shared account is not limited to one platform.

Information you provide

• Account identifiers, email or Apple relay email, username, display name, date of birth, sign-in provider and optional profile photo.
• Fitness goals, experience, equipment, workout schedule, limitations, height and weight when provided.
• Workout and exercise logs, hydration, weight entries, recovery check-ins, routines, challenge activity and preferences.
• Support messages, exercise suggestions and social actions you choose to submit.

These data support account access, personalized exercise selection, saved progress, sync, optional social features and support. Account access uses Firebase Authentication; Apple and Google sign-in are also handled by their respective providers.

Apple Health and Apple Watch

Apple Health access is optional and subject to system permissions. The iPhone app can read available steps, active energy and walking/running distance, and can save supported workouts when permitted. Connecting Health does not mean every reading is available or every permission was granted.

Connected iPhone Health summaries are not necessarily device-only. While signed in, available activity summaries can be saved to the iOS account through Firebase for iPhone-to-iPhone sync. Turning off a permission prevents future access but does not itself delete previously saved cloud data.

The current standalone Watch flow saves walking or strength workouts to Apple Health. Live readings can include heart rate, active energy and walking distance. If you explicitly link a workout to the iPhone account, a completed summary and account/session identifiers are kept on Watch. A manual send transfers that summary to local Watch workout history on the matching iPhone account. This separate Watch history is not currently uploaded to Firebase or added to plan/challenge totals. Its transfer summary excludes heart-rate samples and route coordinates.

Health data is used for the app's health and fitness features, not as advertising targeting input. Removing an entry from local Veyrazo Watch history does not delete the corresponding Apple Health workout.

Outdoor routes and weather

When you start outdoor tracking and grant permission, the app processes location, route, distance, time and available activity readings. Tracking may continue while the screen is locked when the feature and permission are enabled. Saved outdoor routes can sync to Firebase while signed in. Choosing to share a route exposes the exported location information to your selected recipient or service.

Weather uses Open-Meteo. Place searches and forecast coordinates are sent to its services, along with ordinary network information such as your IP address. See Open-Meteo's terms and privacy information.

Cloud, security and sharing

Firebase services provide authentication, database/storage features and app-verification protection, including App Check/App Attest where configured. While signed in, iOS profile, fitness records, saved routes and available iPhone Health summaries may sync to the account. Local-only data is not a cloud backup; uninstalling the app or losing the device can remove it.

Optional social features may disclose profile information and selected information to other users. Sharing a routine or participating in a friend challenge requires an explicit action in supported builds. Recipients may retain independent copies of routines already imported. Do not include sensitive details in names or content you share.

Service providers process the information needed to deliver these functions. See Firebase privacy and security information and Google's privacy policy.

Advertising and privacy choices

The phone app integrates Google AdMob and Google's consent-management tools. Advertising services may process device/app identifiers, IP address, ad interactions and diagnostic information under the applicable consent settings and platform permissions. Manage available choices through Settings → Privacy & advertising and your device settings. Do not assume all ads are non-personalized merely because the app is fitness-related.

Veyrazo's fitness records and HealthKit readings are not supplied as ad-targeting parameters. See Google advertising information. Final release consent configuration and the App Store privacy disclosures must be checked against the shipped build before this draft becomes effective.

Coach explanations and external content

Routine selection and ordinary coaching can use on-device rules and recorded preferences. The generative exercise-explanation feature is currently disabled in release configuration. In enabled testing builds, each request requires permission and sends exercise-guide content and the chosen explanation topic to Google's AI service through Firebase AI Logic. It is not a general health diagnosis service. This notice must be updated if the production feature or transmitted fields change.

YouTube thumbnails may load from Google's servers when suggestions are shown. Opening a video or exercise example sends you to YouTube or another provider, where its privacy terms apply. The external request can reveal network information and the selected video or search query.

Notifications, purchases and local preferences

Reminder settings and system notification permission control workout, hydration, weight and other supported reminders. Turning reminders off does not delete the underlying fitness records. If you use Apple-managed purchases, Apple processes payment and transaction information under its terms; Veyrazo does not receive your full payment-card details.

Theme, units, onboarding state, session checkpoints and other preferences are also stored locally to operate the app.

Retention and deletion

Account-linked records remain available for the account's functions until removed through supported controls or account deletion. Device-local copies can remain on other installations or watches; deleting cloud records does not remotely erase Apple Health or every offline device. Minimal identifiers can remain locally after removing a Watch summary to prevent a delayed transfer from restoring it.

Backups, service logs, support correspondence and legally required records may have different retention rules. The publisher must confirm exact schedules and exceptions before publication; this draft does not promise immediate erasure from every system. See iOS account and data deletion.

Your choices and questions

You can manage system permissions, advertising choices, notifications and available in-app data controls. Contact the address below to request access, correction, deletion or help with other privacy rights applicable where you live. We may need to verify ownership without requesting your password.

The final audience/minimum-age policy, legal operator details, international-processing disclosures and retention schedule require publisher review. Fitness suggestions are not medical advice. Material changes to the effective policy should be dated and explained here.