Sub-processors
Last updated 16 November 2026. These are the outside companies that receive personal data when someone uses the listed features, what each one receives, where it goes and the safeguard we rely on. The list is made from the app's own code. We will update it before any change takes effect.
Service providers that process data for us
They act only on our instructions, under data processing terms.
| Company | What it does for us | What it receives | Country | Safeguard |
|---|---|---|---|---|
| Cloudflare, Inc. | Hosting, databases, file storage and network security | Everything stored in the app, and your IP address and request details | United States, and Cloudflare's worldwide network | EU-US Data Privacy Framework, its UK extension and the Swiss-US Data Privacy Framework; Standard Contractual Clauses as a fallback |
| Anthropic, PBC | AI reading of a lab report you upload, if you turn it on, and, where available to your account, of the label photos of a food you add and of a photo of the front of its package (to read the brand and product name), through Anthropic's commercial API; and finding the product a food you type in is, through an automated task on our own Claude account | The files or photos you ask it to read, and the values or names it returns. To find the product a food you typed in is: that food's name, brand, barcode and label numbers, without your account or any date. A front-of-pack photo is read and not stored by us. Anthropic's commercial terms do not allow it to train its models on the files and photos, and the Claude account that runs our food classifier is set so that Anthropic does not train on what it receives either; its published training and retention policies explain how long it keeps it and the exceptions. | United States | Standard Contractual Clauses in Anthropic's data processing addendum, with the UK addendum and Swiss terms |
| Google LLC (Gemini API) | AI reading of a photo of a meal you take to log it, if you turn it on, through Google's paid Gemini API | The meal photo, the names of foods you have logged recently (at most 60, so it can use the same names), and the foods and weights it returns. The photo is read and not stored by us. Google's terms for its paid API do not allow it to use the photos to improve its products; it keeps them for a limited time only to detect misuse, as its API terms explain. | United States, and other countries where Google has facilities | EU-US Data Privacy Framework, its UK extension and the Swiss-US Data Privacy Framework; Standard Contractual Clauses in Google's data processing terms as a fallback |
| Google LLC (Google Workspace) | Our email at admin@vufro.app | The emails you send us and our replies | United States | EU-US Data Privacy Framework, its UK extension and the Swiss-US Data Privacy Framework |
| OpenMeteo GmbH | The UV index, while UV exposure tracking is on | A position rounded to a 0.1-degree grid (about 11 km) and the date, sent from our servers; not your IP address and nothing about your account | Switzerland | None needed: Switzerland is recognised as giving adequate protection by the EU and the UK |
| Apple Inc. (Apple Weather) | The UV index, while UV exposure tracking is on, for accounts other than the app's original one | A position rounded to a 0.1-degree grid (about 11 km) and the date, sent from our servers; not your IP address and nothing about your account | United States | None needed: the rounded position and date we send are not linked to you or your account |
Separate companies acting under their own privacy policies
Your browser or iPhone talks to these companies directly when you use the feature. They decide how they handle that data themselves.
| Company | Feature | What it receives | Country |
|---|---|---|---|
| Apple Inc. | Sign in with Apple; the maps and place names shown in the app (MapKit); naming the country you are in, if you turn on location; browser Web Push on Apple devices, if enabled | Your sign-in identity; for maps, your IP address, the area of the map you view and the position of a place being named; for the country, the approximate position your iPhone asks Apple to name; for Web Push, an empty wake-up signal and delivery metadata, with no notification text | United States |
| Google LLC | Sign in with Google; browser Web Push in Chrome and on Android, if enabled | Your sign-in identity; for Web Push, an empty wake-up signal and delivery metadata, with no notification text | United States |
| Your browser's push service (for example Mozilla for Firefox or Microsoft for Edge) | Browser Web Push, if enabled | An empty wake-up signal and delivery metadata, with no notification text | Depends on the browser |
| Your browser's speech service (for example Apple for Safari or Google for Chrome) | Journal dictation in a web browser, if you use it (the iPhone app's Journal does not offer it) | Your voice while you dictate, and the text it returns | Depends on the browser |
Apple Health runs on your iPhone; the app reads from it there, and Apple does not receive your health data from us.
Other users see only what you choose to make visible: foods you publish to the shared food catalogue, pages you share by link, and your Cycle page, for a signed-in partner you give a partner code to. Cycle records stay with our existing hosting provider, Cloudflare; they are not sent to Anthropic, an analytics company or an advertising company. Hosting encryption is managed by the provider and the Service, not end-to-end encryption.
We download public food data, including Open Food Facts and USDA FoodData Central, into our own databases, and food and barcode lookups read those databases. No personal data is sent to these sources. Their licences and attribution are on the data sources page.
The Service sends no automatic email, and we do not use any analytics, advertising or crash-reporting company.
Questions: email admin@vufro.app or use the privacy request form.