CALPACE

Privacy policy

wentianzh.apps@outlook.com

Updated October 16, 2026. Developer: ZHANG WENTIAN.

On-device data

Meals, templates, plans, body information, drafts, conversations and assistant preferences stay on your device. No CalPace account is required. The app does not provide meal cloud sync, sell personal information or use it for advertising tracking.

Your API keys are stored in the system Keychain, outside meal and conversation files, and do not migrate through device backup. When using your own service, the key is sent only to that service to authenticate requests, not to a CalPace server. The provider may also process connection and usage metadata. Remove keys separately in assistant settings and never email them.

AI and sending permission

Apple PCC is the default; you may connect your own Google (Gemini API) or OpenAI (API) service. Before sending to each service for the first time, a separate confirmation shows the recipient, data and purpose and requests your explicit permission. Opening a conversation, adding a photo or switching services sends no assistant data. Permission can be revoked in Settings → Privacy policy. New data scope requires new permission; an unavailable service does not trigger forwarding to another provider.

Your submitted text, selected photos and relevant conversation context. For the task, the assistant may also read and send related meals and nutrients, templates, targets, saved body and activity information (including sex, age, height and weight), and dietary preferences.

To understand your request, estimate nutrition and carry out the record operations you request.

PCC has no web search. Services supporting search may use it for a task and process queries and related context. Packaged-food lookup sends only the product barcode to Open Food Facts, not photos.

Providers and data protection

Apple PCC: Apple says PCC uses data only to fulfill your request, without storing it or making it accessible to Apple. These protections apply to PCC, not to other providers.

Google (Gemini API): To use Gemini in CalPace, connect an API project with billing enabled. Google processes submitted data under its terms of service and may retain content for security checks.

OpenAI (API): OpenAI API content is not used for training by default unless you opt in. Safety logs may retain content, normally up to 30 days, with legal or safety exceptions. CalPace disables response storage; this does not mean zero retention.

CalPace sends requests directly to the service you select. It does not operate an AI request server or use submitted content for advertising tracking. Provider data protection and security rules apply to their processing as described above; your API account settings may affect retention or any sharing you choose to enable. When web search is used, Google may retain grounding prompts, context and outputs for 30 days for that feature. CalPace does not request provider-side response storage, but this does not eliminate provider safety logs or feature-specific retention.

Photos

Camera permission is requested when you take a photo; the photo picker reads only selected photos. Adding an attachment does not send it. Images are reprocessed before submission to remove metadata such as location.

Unsent or retryable attachments stay on the device. When photo retention is enabled, photos from the current and previous conversation are retained. Disabling it removes processed photos. Clearing conversations removes associated attachments.

Food lookup and sources

Offline food lookup does not send search terms. Reference data comes from USDA, Japan’s MEXT, Taiwan’s TFDA, ANSES Ciqual and UK CoFID. CalPace also provides labeled reference recipe estimates. The app displays sources, licenses, processing states and original nutrient definitions. Translated names do not alter nutrient values.

When the assistant looks up a packaged product, that lookup sends only its barcode to Open Food Facts; images are not submitted to that lookup endpoint.

Apple Health

With permission, meal nutrients are written to Apple Health, including later edits or deletion. Height and weight are read only when requested and authorized, and retained only when saved. Saved height or weight, including values obtained from Apple Health, may be sent to the selected AI service for a relevant request after its sending permission is granted. The app does not automatically upload your complete Health history. Turning off sync keeps Health data; cleanup removes only the samples CalPace wrote.

Purchases and deletion

Apple handles purchases and payment. CalPace verifies transactions and the original trial time locally to determine access. Restoration does not recover local meals or restart the trial.

In Settings → Privacy policy, you can revoke all assistant sending permission. This stops active requests; entries and saved API keys remain. Each service must request permission again before sending. Revoking permission or deleting local data cannot erase content already received by a provider; use the provider’s privacy contacts or account controls for retention and deletion requests. Settings also let you clear conversations or delete local data. Deletion cannot be undone; its scope is shown beforehand. Remove the selected provider’s key in AI assistant settings, or all saved assistant keys in Settings → Data management. These controls remain available in view-only mode.

Feedback and website

Contact details and information you voluntarily send by email are used only to reply and troubleshoot, then deleted when no longer needed or on request. Never send keys or passwords. Apple processes TestFlight build, session, crash and submitted feedback information under its rules.

GitHub Pages hosts the website and GitHub may process access logs such as IP addresses. This site uses no advertising, analytics scripts or tracking cookies. Changes to this policy or expanded AI submissions are explained where applicable, with consent requested for new submission scope.

Gemini API terms · OpenAI data controls · Apple privacy · TestFlight · GitHub privacy