Vitescope Privacy Policy
Last updated: May 26, 2026
This Privacy Policy explains how Vitescope Team handles information in the Vitescope iOS app. Vitescope helps users track day quality, health-related routines, nutrition, activity, sleep, water, weight, and related goals.
1. Data Controller
Vitescope Team is the data controller for app-level data processing described on this page.
2. Accounts
Vitescope currently does not provide user account registration or login.
3. Permissions Used by the App
- Health (Apple Health read/write): to read health metrics and write selected entries.
- Camera: to capture meal photos and scan barcodes.
- Photo Library: to attach food photos to logs.
Vitescope uses Apple Health data only to provide health and fitness features inside the app. Vitescope does not use Apple Health data for advertising, marketing, data-broker sharing, or sale.
4. Third-Party Services
- Firebase Analytics: product analytics events and screen interaction metrics.
- Firebase Crashlytics: crash reporting and diagnostic stability data.
- Firebase Remote Config: runtime configuration delivery.
- OpenFoodFacts API: food search and barcode nutrition lookup.
- NCBI/PubMed API: biomedical literature search for evidence-backed health answers.
- User-selected MCP clients: optional local-network access, if you enable MCP access in app settings.
- OpenAI API: optional AI features, if you enable AI Agent and select OpenAI as your provider.
- Anthropic API: optional AI features, if you enable AI Agent and select Anthropic as your provider.
5. Data Categories Processed
- Product interaction events (analytics).
- Device-level identifiers used by analytics/crash systems.
- Crash and other diagnostic data for app reliability.
- Search terms and barcode queries sent to OpenFoodFacts for app functionality.
- PubMed search queries and returned paper metadata used for evidence-backed health answers.
- Health and fitness records handled in app flows connected to Apple Health.
- Meal photos, food names, ingredient hints, and nutrition estimates used for food logging.
- Chat messages and attachments you send to Chat with Agent.
- AI plan context such as health metrics, goals, nutrition totals, activity, sleep, water, and weight.
- API tokens you enter for OpenAI or Anthropic, stored locally on your device.
- MCP bearer tokens and MCP tool requests, if you enable MCP access.
6. Optional AI Features
AI Agent is optional and disabled unless you configure it. Before using AI features, Vitescope shows an AI data sharing notice and asks for your agreement. If you do not agree, AI Agent remains disabled.
When AI Agent is enabled, Vitescope sends only the information needed for the AI action you request to the provider you select, OpenAI or Anthropic. This may include chat messages, selected attachments, meal photos, food details, ingredient hints, health metrics, goals, generated plan context, local tool results, saved or logged record summaries, barcode lookup results, and PubMed search results.
When Chat with Agent uses lookup tools, barcode or product queries may be sent to OpenFoodFacts, and biomedical literature search queries may be sent to NCBI/PubMed. The returned lookup results may be included in AI requests to your selected AI provider so the agent can answer your request.
Vitescope uses this information to generate AI Plans, answer Chat with Agent, and recognize food from photos. OpenAI or Anthropic processes the submitted information under its own terms and privacy policy. Review their policies here: OpenAI Privacy Policy and Anthropic Privacy Policy.
You can withdraw AI consent at any time by turning off AI Agent in Settings. Turning off AI Agent stops Vitescope from sending AI requests to OpenAI or Anthropic. You can also remove or replace your API token from Agent settings.
7. Optional MCP Access
MCP access is optional and disabled unless you enable it in settings. When enabled, Vitescope starts a local-network MCP server so MCP-compatible clients that you control can connect to the app.
MCP access requires a bearer token by default. Vitescope shows setup instructions in the app, lets you regenerate the MCP token, and uses per-tool permissions or confirmations for sensitive actions.
MCP clients may request app functionality that reads or changes local Vitescope data, depending on the tools you allow. Tool requests may include or return health and fitness context, goals, nutrition data, food details, chat-related context, lookup results, and other app records needed to complete the tool call. Data is shared with the MCP client you connect to Vitescope.
You can disable MCP access, regenerate the MCP token, or change tool permissions at any time in MCP settings.
8. Tracking and Advertising
Vitescope does not use collected data for cross-app advertising tracking, ad retargeting, or data-broker sharing. Vitescope does not include third-party advertising.
9. Data Retention
Local app records are stored on-device unless transmitted to enabled third-party services for analytics, diagnostics, runtime configuration, food lookup requests, optional AI requests, or optional MCP tool requests to a client you connect.
OpenAI and Anthropic API tokens and MCP bearer tokens are stored on your device. Vitescope does not operate a Vitescope account server for these tokens. Chat history, saved food logs, photos, health records, and AI plan results are stored locally in the app unless a feature explicitly sends selected data to a third-party service or connected MCP client as described in this policy.
Third-party providers may keep submitted data according to their own retention policies. If you want to delete data stored by OpenAI, Anthropic, Firebase, or another third-party provider, you may need to use that provider's account controls or contact that provider directly.
10. User Controls
- You can uninstall the app at any time.
- You can clear/reset local sync and personalization data from app settings.
- You can turn off AI Agent in Agent settings to stop AI requests.
- You can remove or replace your OpenAI or Anthropic API token in Agent settings.
- You can turn off MCP access, regenerate the MCP token, or change MCP tool permissions in MCP settings.
- You can clear local app records from app settings where the app provides reset controls.
- You can contact support for privacy-related requests.
11. Contact
For privacy questions, contact: support@vitescope.app