Your email address, account identifier and authentication information are processed to create and secure your account. Profile and goal information you enter, including age, sex, height and weight, supports nutrition and activity calculations.
Food and meal diaries, water and weight entries, activity and workout records, saved meals, favorites and settings are stored on your device and synchronized with your account for app functionality.
02
Searches, photos & Community
Food searches and barcodes are sent to food lookup services. Camera access is requested for scanning or capturing a product image. Images, product descriptions and submission details you choose to submit are transmitted for review; approved contributions may become part of the public food catalog.
Do not include personal or health information in public product contributions. Community posts and interactions you submit are processed to provide Community features; published content is visible to its intended audience.
03
Permissions & service providers
Android camera and notification permissions are requested when needed. Phone notifications require permission and an active subscription. When enabled, Firebase Cloud Messaging processes an installation/device identifier and push token; the notification service stores registration and delivery status. You can turn off phone notifications while keeping eligible in-app Bell notifications. General Community phone delivery is not represented as enabled by this policy.
Supabase provides authentication, account data and file storage. Firebase/Google provides mobile messaging. The configured authentication email provider handles account email. VEZVO food services process searches and product submissions. Providers receive the data needed for their functions and network metadata such as IP addresses.
This Android release does not integrate an advertising SDK or Firebase Analytics and does not use health records for ad targeting. It requests no clinical health-record, contacts, microphone or location permission.
04
Security & your choices
Release connections use HTTPS. Account access controls protect cloud records, and authentication credentials use secure device storage. Local records remain until removed by the app or its data is cleared. Device security remains important; no system can guarantee absolute security.
You can edit supported records in the app, choose whether to submit images or public content, and revoke Android permissions. VEZVO is not a substitute for medical advice, diagnosis or treatment.
Account-linked data is retained while the account is active unless removed through available controls. Request deletion in More → Delete account or on the account deletion page, without installing the app. Verify ownership with your password or the available email verification method and confirm deletion.
An accepted request blocks the account while personal records, account-linked files, notification registrations, authored Community content and the Auth identity are removed. Failed cleanup remains pending and can be resumed; an incomplete request is not presented as complete.
Other current-version installations clear local account data when they next connect and detect deletion. Offline devices cannot be remotely erased. Unlinked public food catalog contributions and records held independently by other providers may remain.
After completion, the random deletion receipt no longer contains the account identifier and becomes eligible for cleanup after 30 days. Separate provider logs and isolated backups are outside the account deletion API; deleting an account does not by itself erase those copies.
