Tsinginc · LabelCue
Privacy Policy
Effective date: September 29, 2026
1. Who we are
LabelCue is developed and operated by Tsinginc. For privacy questions or requests, contact support@tsinginc.com.
LabelCue is in development for iPhone and is not yet publicly available on the App Store. This policy describes this website and the current development-build data handling. We will update it as the app and its service providers are finalized for public release.
2. Website visits and support
This website has no analysis upload form, advertising trackers, analytics trackers or third-party font requests. It does not set application cookies or use browser storage to track visitors. Our hosting infrastructure processes normal request information, which can include your IP address, browser information, requested URL and request time, to serve pages, maintain security and investigate problems.
Contact links open your email application. If you email us, we receive your email address, message and any attachments you choose to include. We use them to respond to your request; our email providers also process those communications. Send only information needed to explain the issue. Do not include passwords, installation credentials or unrelated health information.
Support correspondence is kept for handling the request and necessary follow-up. Hosting logs and backup retention are being reviewed for the public-release policy. The analysis-retention periods below do not apply to support emails, hosting logs or backups. You can contact us to ask about or request deletion of information you have sent.
3. Scans, preferences and AI analysis
The app stores preferences, scan history, saved results and associated images on your device. Preferences may include dietary choices, nutrition goals, allergies, health conditions and information you enter yourself.
Online analysis sends selected label images, relevant preferences, language and task information to our service. Our service sends prepared images, label information and relevant preferences to a third-party AI service to read and explain the label. Avoid including faces, personal documents or information unrelated to the food label.
The current development service uses a Qwen-compatible third-party gateway at maas.qianwenaiapi.com. A model name does not identify the company operating that gateway. Its operator identity, processing locations, retention and model-training terms are still being verified for public release. The retention periods for our service do not describe that provider’s copies, and we do not currently make a no-training or no-retention promise for that provider.
We use an installation identifier, credential hashes, task identifiers, usage counters and limited technical records to protect access, recover tasks, apply service limits and investigate failures. Registration limits use a keyed hash of the network address. These records are not anonymous simply because a value is hashed.
4. Barcodes and other services
Barcode lookup uses Open Food Facts. The app or our server sends a product barcode to that service and may download public label images. Direct requests from your device also expose normal network information, including your IP address, to that service. The barcode lookup itself does not send your dietary preference profile. Downloaded labels may later be submitted for AI analysis together with relevant preferences.
Open Food Facts provides its own privacy information. Product database entries can be incomplete or describe a different packaging version. If you share a result or send an email, the service you choose processes the information you send under its own policies.
5. App configuration and advertising attribution
We are preparing the following integrations for the iPhone app. Whether an integration runs depends on the app version, build configuration and, for advertising attribution, your permission. These SDKs do not run on this website. The current integration does not run them in the Windows preview or Unity Editor.
GameAnalytics Remote Config
App builds with this service enabled can contact GameAnalytics to retrieve configuration values. The current configuration is a reserved, inactive paywall setting; it does not enable a purchase or change access to scanning. We disable advertising-identifier collection, analytics-event submission, automatic error-log reporting and optional performance/hardware telemetry for this integration.
Fetching configuration still requires a network request. GameAnalytics can process app and SDK identifiers, app/version and platform information, an SDK installation identifier and normal connection information such as your IP address. Disabling analytics events does not mean that no information is transmitted. This configuration service is separate from advertising attribution and does not depend on granting tracking permission. See the GameAnalytics privacy and data-protection information and its privacy notice.
Meta (Facebook) and Kochava
In iPhone builds with these integrations enabled, we use Meta for basic app activation measurement and Kochava for install and session attribution, to understand which advertising brings people to LabelCue. We do not initialize these advertising SDKs before iOS reports that you have allowed tracking through App Tracking Transparency. If you decline, are restricted or have not made a choice, they remain inactive. Your choice does not prevent you from scanning labels or using the app.
After authorization, these providers may process the advertising identifier (IDFA), SDK or device identifiers, app identity and version, install/open/session times, attribution or campaign information, limited technical information and network information such as your IP address. Meta may associate information it receives with information held under its own policies. Our current integration disables Meta automatic app-event logging and does not send custom scan, purchase or subscription events. Kochava uses a restricted collection configuration; it is not given custom user identities or a precise location by LabelCue.
LabelCue does not send label photos, ingredients, dietary preferences, allergies, health conditions, AI prompts or analysis text to GameAnalytics, Meta or Kochava. These services are separate from the AI analysis provider described above.
You can change tracking permission in iOS Settings > Privacy & Security > Tracking. LabelCue rechecks the system permission and stops its advertising collection when permission is withdrawn. Withdrawal does not by itself erase information a provider has already received. For provider handling and privacy choices, see Meta’s Privacy Policy, Kochava’s privacy information, its SDK data-privacy guidance and privacy request and opt-out instructions.
Provider retention periods, processing locations and rights procedures are governed by the applicable provider arrangements and policies. The analysis-service retention periods below do not apply to SDK provider records. We are reviewing the final service configuration and release disclosures before public launch; contact us if you need help with a request.
6. How long information is kept
The current analysis service uses the following retention rules. Scheduled removal depends on maintenance running successfully; it is not a guarantee of immediate or secure physical erasure.
| Information | Current handling |
|---|---|
| Uploaded label photos | We attempt removal after the app confirms it saved a completed result. Without that confirmation, uploaded photos are scheduled for removal approximately 24 hours after the task finishes. |
| Finished-task results and submitted preferences | Expire approximately 72 hours after the task finishes. Short-lived analysis caches may remain for up to 72 hours. |
| Limited provider-call records and rate-limit counters | Retained for approximately 30 days. |
| Minimum installation and duplicate-prevention records | Identifiers, timestamps, ownership and input fingerprints currently have no automatic expiry. They help avoid processing the same submission again after its full result expires. |
| Public label images from barcode databases | Some downloaded public images and related prepared files can remain outside the uploaded-photo cleanup. This cleanup is under review. |
These periods do not apply to active tasks, copies on your device or third-party providers. Removing a scan from the current app’s history removes its visible entry; associated image files and local recovery copies may remain. Device backups may also retain app data according to your platform and settings.
7. Your choices and requests
- Change your dietary preferences in the app.
- Use iOS settings to control camera and notification permissions. The photo picker supplies the image you select without requiring access to your whole photo library.
- Decline or withdraw advertising tracking permission in iOS Settings > Privacy & Security > Tracking.
- Avoid further online analysis by not submitting photos or starting barcode analysis.
- Contact us about access, correction or deletion, or any other data rights available where you live.
Send requests to support@tsinginc.com. Include an approximate analysis time and a task reference if available, but never send passwords or installation credentials. We may need information to locate the relevant records and verify your request. Some rights depend on applicable law and may be subject to lawful limitations.
8. Security and changes
Connections to our public website and analysis service use HTTPS. Access controls and installation-scoped tasks help limit unauthorized access, but no internet service can guarantee absolute security. We are reviewing provider terms, infrastructure retention, backup handling and the final iPhone release before public availability.
We will publish changes on this page and update the effective date. For questions about this policy or its current limits, please contact support.