Last Updated: January 2025
We believe you shouldn't need a law degree to understand where your intimate data goes.
Vitality 74 utilizes a Local-First Architecture.
All user-generated content, including but not limited to:
...is stored locally on your device. This data is not synchronized to any cloud service owned or operated by Vitality 74.
Our "Bio-Analytics" features use Edge Computing.
When the app analyzes correlations (e.g., comparing Zinc intake to recovery trends), this calculation is performed by your phone's CPU using local JavaScript libraries.
No data is transmitted to third-party AI APIs (such as OpenAI or Google Cloud) for analysis. All intelligence runs in your pocket.
We minimize third-party integrations to the absolute essentials required for app functionality:
Purpose: Used to process subscriptions and the "Lifetime Unlock" purchase.
Data Shared: An anonymous App User ID (random string) and purchase status.
Why: To verify you have paid for the Pro features.
Purpose: Used for the actual financial transaction.
Data Shared: Financial data is handled entirely by Apple/Google. We never see your payment method, credit card details, or billing address.
You have the absolute right to erasure. Because your data is local, you do not need to request us to delete it. You can destroy it instantly:
Go to Settings > Storage > Tap "Nuke All Data"
This overwrites the database and deletes the encryption key from your SecureStore.
Uninstalling the app from your operating system permanently removes the local database file.
This action cannot be undone.
Because we do not sync your data, we cannot restore your data if you lose your phone.
If you use Apple iCloud Backup or Google Drive Backup for your entire device, your encrypted database file may be included in that backup. This is managed by your OS settings, not by Vitality 74.
The backup file remains encrypted and requires your device's Secure Enclave key to decrypt.
Vitality 74 is intended for users 18 years of age and older.
We do not knowingly collect information from children under 18. Since all data is stored locally on the user's device, we have no mechanism to identify or access data from any user, regardless of age.
For users in the European Economic Area (EEA), we comply with GDPR requirements by design through our local-only data storage approach.
Since we do not possess user data, we cannot comply with subpoenas for user records.