Last updated: October 17, 2026
SnapCal is provided by NEXUS TECH, INC. (developer: Wei Wenxin). This policy describes the data used for food records, AI analysis, accounts, subscriptions and optional cloud backup. AI estimates are informational and are not a medical diagnosis.
Food photos, meal names, nutrients, dates and goals are used to maintain your records and provide the features you choose. Records are kept on your device. If you sign in and have cloud entitlement, records, photos and your profile may also be synchronized to private Firebase storage through our backend. Anonymous or signed-in account identifiers, quota counters and security records are processed on our server to authenticate requests and prevent misuse. Signing in may provide your email address, display name and profile photo through Firebase Authentication. Apple processes purchases; our server processes transaction and entitlement information to verify subscriptions and handle refunds.
Before an AI request, the app asks for permission on this device. The selected feature sends the necessary food photos, meal names, nutrition history and goals through our Google Cloud Run backend to OpenRouter and OpenAI. If Apple Health integration is enabled, AI advice may also include calorie-burn totals and steps. You can decline and continue manual records, or withdraw permission in Settings → AI data sharing. Withdrawal stops future AI requests on this device; it does not undo earlier processing. We request provider routes that do not use submitted data for training and support zero data retention. Provider security and legal obligations remain governed by their own policies.
With your Apple Health authorization, SnapCal reads active and basal energy, dietary energy, steps and exercise to show progress. It can write saved dietary energy, protein, fat, carbohydrates and fiber to Apple Health. AI advice may include the limited totals described above only after AI sharing permission. Health information is not used for advertising. You can revoke individual Health permissions in Apple Health or iOS Settings. Data already written to Apple Health is managed separately there.
The free tier uses Google AdMob. Google may process advertising identifiers and device information according to your tracking permissions and its policies. Reward verification uses a short-lived opaque ticket rather than sending your raw account identifier to Google. Google/Firebase provides authentication, application attestation, hosting and private storage. OpenRouter and OpenAI process AI inputs; Apple provides purchases, sign-in and Health. These providers may process information outside your country.
Transfers use HTTPS. Server APIs check authentication and app attestation, and private cloud data is accessible through controlled backend routes. Provider keys stay on the server. AI request images are processed in memory; photos selected for cloud backup are stored separately. Local records remain until removed from the app or device. Cloud records remain until deleted or the account is deleted. Account deletion is available in the app and removes account data and starts any required continuing cleanup. Minimal accounting, abuse-prevention and deletion-status records may be retained for service integrity or legal obligations. Cloud Storage soft-deleted copies may remain recoverable for seven days before provider removal. Deleting an account does not cancel an Apple subscription; manage it in Apple subscription settings.
You can review or delete meal records, delete your account in the app, withdraw AI permission, revoke Apple Health access, and change tracking permission in iOS Settings. Signing out does not by itself delete server records. Contact nexuswei.dev@gmail.com for access, correction or deletion questions. The app is not intended for children under 13 or the applicable local consent age. Policy changes appear here with a new date; a material change to AI sharing requires a renewed in-app permission.
SnapCal · NEXUS TECH, INC.
nexuswei.dev@gmail.com