Privacy policy

Information we handle

Virtueve is a nutrition, cooking and meal-planning app. The information it handles depends on the features you use.

• Account information: email address, authentication credentials or Google/Apple identity information, account identifiers and sign-in sessions. Passwords are supplied to Supabase Auth; Virtueve’s app code does not store them. Sign-in providers may supply account profile metadata.
• Food and health profile: biological sex, age, height, weight, activity level, nutrition goals, calculated calorie and nutrient targets, dietary preferences, allergies, intolerances, and foods you like or dislike.
• Food and cooking activity: meal logs, portions, calories and nutrients, nutrition goal history, favourites, saved recipes, cooking history, ratings, taste tags and feedback.
• Planning and shopping: meal plans, dates, priorities, notes, kitchen inventory, quantities, shopping lists and related status information.
• Searches and requests: food search terms, barcodes, recipe instructions, adaptation requests, cuisine selections and recommendation history.
• Images and contributions: photos of plates, nutrition labels, receipts, products and finished dishes; extracted information; product contributions; and public community ratings and reviews.
• Technical information: identifiers, timestamps, job status and error details. Hosting and other providers may receive IP addresses and HTTP request information when delivering their services.

How information is used

Virtueve uses this information to manage accounts and recovery, synchronise account data, calculate nutrition targets, track meals, organise recipes and kitchen items, create meal plans and shopping lists, and personalise recipes and recommendations.

Image features use recognition and text extraction to interpret food, labels, receipts and product evidence. Community features publish contributions you choose to share and assess photo quality and relevance. Technical records support service delivery, debugging and recovery of unfinished requests.

Services that receive information

Information is transmitted to the following services as needed for the features you use:

Supabase

Authentication, private account synchronisation and image storage. It receives account and sign-in information, your synchronised account data and stored public images.

Railway

Hosts Virtueve’s backend and database. Requests can include food profile details, recipe and meal-plan instructions, kitchen context, images and community submissions.

OpenAI

Processes selected text, food profile constraints, kitchen context and images sent through Virtueve’s backend for AI generation, recognition and extraction. Submitted community photos and recipe context are also processed to score photo quality and relevance. Provider retention and training settings have not been verified for this policy.

USDA FoodData Central

Receives food search queries for nutrition lookup.

Open Food Facts

Receives barcodes for product lookup and related request metadata. Your device may also request product images from external image addresses returned by this service.

Google and Apple

Process authentication and identity information when you choose their sign-in options through Supabase. The exact profile metadata retained depends on provider configuration.

Providers’ operational logs and retention periods have not been established by the source audit. This policy does not promise a particular provider retention period or contractual processing classification.

What becomes public

When you choose to share a community cook, your rating, review, finished-dish photo and cook timestamp become public. Public responses include contribution identifiers and timestamps, but do not include your email address, account identifier or display name.

Community photos are stored as public images. Their storage addresses can contain a stable account identifier, even though normal community responses omit that identifier. Community photos are converted to optimised JPEGs with image metadata removed before durable storage.

Confirmed product contributions, including product information and front-of-package images, become shared product assets. Shared recipes and product assets remain after account deletion.

Device access and your choices

Camera and photo-library access are used when you initiate image features, such as scanning food or barcodes, importing a receipt, or sharing a dish photo. You can manage these permissions through your device settings.

Food profile fields, food logging, images and community contributions are feature-driven and mostly optional. Authentication information is needed for account-backed features.

The audited app contains no implementation for advertising, analytics SDKs, crash-reporting SDKs, location, contacts, microphone access, push notifications, advertising identifiers or payment collection. This does not rule out operational logging by hosting and other service providers.

Storage and retention

Virtueve stores food profile information, meal logs, saved recipes, cooking activity, plans, kitchen and shopping data, preferences and session information on your device. For signed-in users, an account-state snapshot is synchronised to Supabase. Local copies of community photos are stored in the app’s private files.

The backend stores shared recipes and products, community contributions, generation requests and results, and cached recipe requests. Public community and product images are stored in Supabase.

There is no verified general retention schedule. Non-image generation requests and results, and cached recipe requests, have no explicit expiry in the audited implementation. They can contain dietary, health, personalisation and free-text information.

Plate and nutrition-label scan jobs replace their raw image payload with a hash when the job finishes. Stale jobs of those types are failed and compacted after one hour; derived results remain. This behaviour is not a promise that all image types, provider copies or logs are deleted within one hour.

Shared recommendation history is limited by record count rather than time. Account-deletion recovery tokens expire after one hour, but their stored hashes, account identifiers and related records have no verified purge schedule. Provider log and backup retention periods have not been verified.

Account deletion and its limits

You can permanently delete your account in the app: Settings → Account → Delete account, then follow the confirmation steps. You can also request account deletion by emailing hello@virtueveapp.com from the email address associated with your Virtueve account. See Delete your Virtueve account for the steps and retention limits. The implemented deletion flow removes:

• Your Supabase authentication account and private synchronised account-state record.
• Your account-owned local app data, local sign-in session and local community-photo directory.
• Your owned community contributions and their stored public photos and media records.

Device-only preferences, such as measurement settings, may remain. The audit did not establish deletion behaviour for providers’ logs or backups.

There is currently no separate in-app delete or unpublish control for an individual community contribution. You can overwrite the same cook contribution, or remove your owned community contributions through account deletion.

Contact

For privacy questions or questions about your data and deletion, contact hello@virtueveapp.com.