Who we are
RelishCue is a menu decision assistant. If you have privacy questions, email us at hello@relishcue.com.
Data we collect
- Menu images or photos you submit.
- Readable or extracted menu text.
- Food preferences you choose to provide, such as taste, dietary, allergy-related, religious, pregnancy-related, or other optional food preferences.
- Prompts, AI or model responses, generated menu analysis, scan results, and representative dish image requests or responses.
- App version, platform, locale, and a device or app identifier generated by RelishCue.
- Purchase and subscription status, product identifiers, receipts or purchase tokens, entitlement status, and anonymous app user identifiers when applicable.
- Diagnostics, crash or error logs, scan quality data, performance data, and abuse-prevention signals.
- Support emails or messages if you contact us.
- Website and server logs, such as IP address, request timestamps, browser or device information, and pages visited.
In the current app build, saved scan history, taste preferences, monthly scan counts, and Pro Preview state are stored locally on your device.
What the app sends
Persistent user settings and saved scan history stay local in the current app build. RelishCue does not currently offer account-based cloud sync.
When you analyze a menu, RelishCue may send the menu image, readable or extracted menu text, selected food preferences, app version, platform, locale, scan context, and app-generated identifier to our backend and service providers to generate results.
AI menu analysis
Menu images, readable menu text, selected food preferences, prompts, scan context, and generated results may be processed by AI, OCR, or menu analysis providers to generate RelishCue results and help operate, secure, debug, and improve the service.
AI outputs are informational and can be inaccurate. Do not upload payment cards, IDs, private documents, confidential information, or sensitive personal information.
Provider terms and settings may affect whether submitted content is temporarily retained or used to improve provider services. We configure providers to limit training or model-improvement use where available.
Subscriptions and purchase status
If you purchase through the Apple App Store, Apple and subscription or entitlement providers may process purchase details, subscription status, product identifiers, receipts, and anonymous app user identifiers.
If you purchase through Google Play, Google and subscription or entitlement providers may process purchase details, subscription status, product identifiers, order identifiers, purchase tokens, and anonymous app user identifiers.
RelishCue checks subscription status to unlock Pro features. We do not store Apple private keys, Google private keys, App Store credentials, Google Play credentials, or Google account credentials in the app.
How we use data
- Operate menu scanning and analysis.
- Generate recommendations, dish explanations, representative dish images, and staff phrases.
- Store preferences and scan history locally on your device when enabled.
- Enforce limits and unlock Pro features.
- Troubleshoot, monitor reliability, prevent abuse or fraud, improve scan quality, and improve product performance.
- Respond to support requests.
- Comply with legal and platform obligations.
What stays on your device
Saved scan history, taste preferences, monthly scan counts, and Pro Preview state are stored locally on your device in the current build. You can delete saved scans and reset preferences in app settings.
RelishCue does not currently offer account-based cloud sync and does not use location tracking in the current app build.
Service providers and sharing
RelishCue may use cloud hosting and backend infrastructure, AI and menu analysis providers, OCR providers where applicable, subscription and entitlement management providers, Apple App Store billing, Google Play billing, diagnostics, crash or error monitoring, performance monitoring, and support or email providers.
Providers process data to provide services to RelishCue, subject to their own terms and privacy or security obligations.
RelishCue does not sell personal information. RelishCue does not use menu scans, preferences, or purchase status for third-party advertising or cross-app tracking.
Retention
Local scans, preferences, monthly scan counts, and Pro Preview state remain on your device until you delete them in the app or uninstall the app.
Backend and provider logs, diagnostics, menu analysis payloads, generated responses, and related service records are kept only as long as reasonably needed to operate, debug, secure, improve, comply with legal or platform obligations, prevent abuse or fraud, and resolve support issues.
Purchase and entitlement records are kept as long as needed to verify subscription status and meet legal, accounting, platform, and fraud-prevention obligations.
Support messages are kept as long as needed to handle the request and maintain business records.
Your choices
You can delete saved scans and reset preferences in the app. You can manage or cancel Apple subscriptions in Apple subscription settings and Google Play subscriptions in Google Play.
You can email hello@relishcue.com to request access, correction, deletion, or privacy help. Because RelishCue may not use accounts, you may need to provide your app-generated identifier, purchase or entitlement identifier, or support details so we can locate records.
Deleting local scans removes them from your device, but may not delete data already processed by our backend or providers. Email us for backend or provider deletion requests where available.
Our Terms are available at https://relishcue.com/terms.
Children
RelishCue is not intended for children under 13, and we do not knowingly collect personal information from children under 13.
Security
We use reasonable safeguards to protect data. No internet service can be perfectly secure.
International processing
Data may be processed in the United States and other countries where RelishCue or its providers operate.
Food and allergy note
Menu text, photos, translations, and model responses can miss ingredients or preparation details. Ask restaurant staff to confirm ingredients, preparation, cross-contact, allergens, and suitability before ordering, especially for allergies, medical needs, pregnancy, religious restrictions, or other important dietary requirements.
Changes
We post updates on this Privacy Policy page and update the date below.
Last updated: June 6, 2026.