Effective date: October 6, 2026
This policy applies to the Android and iOS versions of Daily Meal Tracker (bundle/package ID com.cygnusx.dailymealplanner) and its food-analysis API. It describes the implementation currently used by Cygnus X Enterprises LLC.
Information kept on your device
The app keeps your meal history, nutrition settings, calorie goals, and any height or weight imported from Health Connect or HealthKit in the app’s local device storage. You can remove that device-side data by using the app’s controls, clearing the app’s storage in Android Settings, or uninstalling the app. Android backup or device-transfer features may separately copy local data according to your Android and Google Account settings.
Health Connect (Android) and HealthKit (iOS) height and weight imports are optional. When enabled, they are used only on the device to calculate a calorie target. They are not sent to the food-analysis service, Nutritionix, OpenAI, Google Play Integrity, or App Attest.
Food text and meal-photo analysis
Food analysis is optional. If you submit food text, the text is sent to the Cygnus X food-analysis API over HTTPS. The API sends it to one of the following nutrition processors: Nutritionix, using its Natural Language for Nutrients API when that service is configured; otherwise OpenAI, using the Chat Completions API with the gpt-4o-mini model. The active processor is selected by server configuration, so the app does not send the same text to both processors for one request.
If you submit a meal photo, the image is received by the Cygnus X API, checked and, when needed, resized in temporary/in-memory processing. The iOS app resizes a meal photo to at most 1024 pixels on its longest side before upload; the API also checks and, when needed, resizes oversized uploads. The image is then sent to OpenAI through the Chat Completions API using the gpt-4o model to identify food and estimate calories. The API does not store the original or resized photo in its application database or an application upload folder. PHP’s temporary upload file is used only to process the request and is removed at the end of request processing.
The current Android and iOS versions call only the food-analysis endpoints for this feature. When you confirm an analyzed meal, its history is stored locally on your device; these versions do not submit that confirmed meal history to the server. Separately, the server’s POST v1/foods endpoint can store nutrition entries submitted by other clients in its daily_nutrition database table. That table has no automatic retention or purge job in the reviewed implementation; a submitted entry remains until deleted through the API’s available delete action or removed by an administrator. The table schema does not associate these rows with an app account, an IP address, or a supplied device identifier.
The reviewed implementation does not define a separate application-backup retention period for those database records. Provider-side request logs and backups are controlled by Nutritionix or OpenAI under the applicable provider account and terms; the Cygnus X implementation does not set, expose, or verify a fixed provider retention period. Do not submit information you would not want processed by the selected food-analysis provider.
Optional microphone, camera, and photo input
Microphone or speech input is optional. Speech recognition, if you choose to use it, is handled by Android or the speech service selected in your device settings on Android, and by Apple Speech recognition on iOS; the Cygnus X API receives only the food text that you choose to submit for analysis. Camera and photo-library access are also optional and are used only when you choose a meal photo for analysis. You may deny or revoke these permissions in Android Settings or iPhone Settings.
Security, IP addresses, and tokens
Our web server’s standard access logs record the IP address, date and time, requested URL, HTTP status, referring page, and user-agent information for API requests. These logs are rotated daily and retained for up to 15 days (the current log plus up to 14 daily archives), then removed by server log rotation. They are used for security, reliability, and troubleshooting, not advertising.
The Android app obtains a Google Play Integrity token to protect the API from abuse. The raw token is sent to Google Play Integrity for validation and is passed through the Cygnus X server only for that validation. The server stores only a SHA-256 hash of the Integrity token and a SHA-256 hash of the request hash for five minutes to detect replay attempts; the raw Integrity token is not stored in the application database. Google’s processing of the token is governed by Google’s terms and policies.
The iOS app uses Apple App Attest to protect API access. When an iOS device registers an App Attest key, the API stores a device-level App Attest key record containing the key ID, public key, assertion counter, receipt metadata, attestation metadata, app identifier, and creation, last-use, and (if applicable) revocation timestamps. The API uses this record to verify that requests come from the genuine app, validate App Attest assertions, prevent assertion replay, and issue iOS sessions; the assertion counter and last-use timestamp are updated after a successful assertion. The reviewed implementation has no automatic retention or purge job for registered App Attest key records; its scheduled cleanup deletes expired App Attest challenges only, not registered keys. App Attest is separate from Google Play Integrity and is not used by the Android app.
The API issues a signed bearer session token that expires after 15 minutes. The server validates the token cryptographically and does not keep a server-side session-token database. The API does not collect an Android advertising ID or a hardware device identifier. Its Android session subject is derived from the app package name and a one-time request hash, not a stored device identifier.
Advertising, sales, and sharing
The reviewed Daily Meal Tracker API has no advertising SDK, advertising integration, data-broker integration, or sale of user data. Cygnus X does not use food text, meal photos, Health Connect or HealthKit height or weight, or local meal data for advertising. We share food text or photos only with the applicable processor described above to provide the analysis you request, and share Integrity tokens with Google to validate Android app integrity.
Changes and contact
We may update this policy when the app, API, processors, or data practices change. We will post the revised policy at this URL and update the effective date. For questions or requests about this policy, contact support@cygnusx.com.