Privacy Policy
This app helps users plan meals, manage household nutrition targets, and generate shopping lists.
What data the app uses
- Account information — email address and authentication identifiers used for sign-in. Email addresses are verified by a one-time link sent to the user on registration and again on any sign-in where the email is not yet verified.
- Profile information — name, age, sex, height, weight, activity level, diet, allergies, intolerances, cuisines, and nutrition targets.
- Planning data — selected meals, weekly plan preferences, household members, custom meals, meal templates, daily intake history, and shopping-list related data.
- Optional media permissions — camera and photo-library access when the user chooses to scan or attach meal-related images.
How data is stored
- Account credentials are handled by Firebase Authentication. Passwords are never seen or stored by the app — Firebase Authentication manages them on Google’s infrastructure. A minimum password length of 8 characters is required at registration.
- Profile, planning, household, custom meals, meal templates, and intake-history data are stored in Cloud Firestore (Google) under a document path scoped to the signed-in user. Firestore security rules restrict every read and write to the document owner.
- Some app data may be cached locally on the device for performance and offline use.
- Authentication tokens are stored using the device’s secure storage (Keychain on iOS, EncryptedSharedPreferences on Android via
expo-secure-store), with a non-sensitive AsyncStorage fallback only when the secure-storage API is unavailable.
How data is used
- To sign users in, verify their email, and maintain their session.
- To calculate nutrition targets and tailor meal recommendations.
- To build weekly plans, optimise portions, and generate shopping lists.
- To support app features that require camera or photo-library access only when the user invokes them.
Subprocessors and data sharing
- The app does not include third-party advertising or ad tracking.
- The app uses the following subprocessors:
- Google Firebase (Authentication, Cloud Firestore) — stores account credentials, profile, and planning data.
- RevenueCat — manages subscription entitlements. The app sends the Firebase user ID to RevenueCat to associate a subscription with the account; the email address is not shared.
- The app does not call any third-party recipe APIs; recipe content is bundled with the app.
User controls
- Users can sign out at any time from the People screen.
- Users can delete their account from within the app. Deletion re-prompts for the password, then removes the user’s profile, household, custom meals, meal templates, and intake history from Firestore, and finally deletes the Firebase Auth user record.
- Users can deny camera or photo-library permissions and continue using the rest of the app.
Retention
Data is retained for as long as the user keeps an account. When the user deletes their account from within the app, profile and planning data are removed from Firestore and the Firebase Auth record is deleted in the same flow.
Children
The app is not directed at children under 13 and does not knowingly collect personal data from them.
Contact
Support email: support@snapnutritionapp.com