Privacy Policy
Last updated 16 November 2026. This version replaces the one of 15 November 2026. If we change this policy in a way that matters, we tell you in the app before the change takes effect and, where the law requires, ask for your agreement again.
This policy explains how Vufro (the iPhone app, the website and the dashboard, together the "Service") handles personal data, and what your rights are. It applies to everyone who uses the Service, wherever they are.
1. Who we are and how to reach us
The Service is operated by Pick and Pack LLC, a Wyoming limited liability company, 30 N Gould St Ste R, Sheridan WY 82801, USA ("we", "us"). We decide how your personal data is used, which makes us its "controller" in data protection terms and the "business" under US state privacy laws.
- Email: admin@vufro.app, also the address for reporting a security problem. A person reads every message. You can write to us in English.
- The privacy request form, for requests and complaints about your data.
- Post: the address above.
Our legal notice gives the same details on one page. We have not appointed a data protection officer. We have assessed whether the law requires one and will appoint one if it does. The contacts above handle every privacy question.
We do not currently offer Vufro in the EU/EEA, the UK or Switzerland. Before we do, we will appoint representatives there and update this policy. Vufro is not offered in some other countries either; section 1 of our Terms of Service lists them.
2. The short version
- Your health data is yours. We use it to show it back to you, calculate your scores and run the features you choose. We do not sell it and we do not use it for advertising.
- Most of what we hold is health data. We ask for your explicit consent before we collect it. You can withdraw that consent and delete your account at any time on the Account page.
- A few features send data to companies that work for us, for example our AI provider when you ask it to read a lab report. They are listed on our sub-processors page.
- Another Vufro user sees your data only if you give them a Cycle partner code, and then only your Cycle page, for as long as you allow it.
- The Service is a general wellness app. It is not a medical device and it does not diagnose, treat or prevent any condition.
3. What we collect
3.1 Account data
- Your email address, from the way you sign in. New accounts are created only with Sign in with Apple, in the iPhone app. You can also sign in with Google if your Google account uses the same email address, and any account can add a password on the Account page to sign in with its email address; accounts created earlier with an email address and password keep signing in that way. For a password we store a salted hash, never the password itself. If you use Apple's "Hide My Email", we only receive the relay address.
- Your name, if you give it, or the name your Apple or Google account shares when you sign in with it.
- Your date of birth and sex, to confirm that you are 18 or older and to personalise calculations such as heart-rate zones.
- A country of residence you previously provided remains on your account. Current setup does not ask for it, and we do not infer residence from your connection or optional phone location.
- Sign-in records: for each browser or device that is signed in, how and when you signed in and the email address used; which Apple or Google account is linked to yours; and, for Sign in with Apple, a token we use to end that link at Apple when you delete your account. We do not store your IP address or device type with these records.
- A record of the consents you gave, with the date, the version of the documents, the language the app showed them in, the exact words of the boxes you ticked, and what you agreed to (the terms, your Apple Health data including cycle and sexual activity records, your food diary, and the Cycle consent if you turned Cycle on yourself), and the date you withdrew consent, if you do. Cycle partner codes and connections, and your choices to pause or remove them, also identify the accounts involved and the dates of those actions.
- Access keys you create for your own scripts or shortcuts. We store only a fingerprint (hash) of each key and the label you gave it.
The Service sends no automatic email: there is no email verification and no email password reset. We write to you only to answer a request you sent or to tell you about a decision that affects you, from admin@vufro.app. If you cannot sign in, use the privacy request form.
3.2 Health and fitness data from Apple Health (only with your permission)
The iPhone app reads only the types you allow on the Health permission screen:
- heart and vitals: heart rate, resting heart rate, walking heart rate average, heart rate variability, heart rate recovery after exercise, VO2 max, blood oxygen, breathing rate, blood pressure, blood glucose, sleeping wrist temperature, AFib history, and ECG recordings from your Apple Watch;
- sleep sessions and stages;
- activity: steps, distance, flights climbed, active and resting energy, exercise minutes, stand hours and minutes, physical effort, time in daylight and your Activity ring summaries;
- workouts: their type, times, energy, heart rate and effort scores, and measures for particular sports (running power, speed, stride length, ground contact time and vertical oscillation; cycling cadence, power and speed; swimming strokes; distances for skiing, snowboarding, paddling, rowing and skating), and the GPS route of an outdoor workout (see section 3.4);
- mobility: walking speed, step length, walking asymmetry, double support time and stair speed;
- environmental and headphone sound levels;
- body measurements: weight, body fat, lean mass, waist and height;
- cycle tracking, only when your profile says female: periods and their flow, spotting, sexual activity and whether protection was used, cycle symptoms and their severity, basal body temperature, cervical fluid, ovulation and pregnancy test results, and whether Apple Health records a pregnancy, breastfeeding or contraception. These go only into your Cycle diary (section 3.3).
Besides new readings, the app copies your past Apple Health history of the types you allow, going back as far as Apple Health keeps it, which can be many years, together with the GPS routes of past outdoor workouts. It does this in the background, a month at a time, so your charts and scores include your history. You can stop it at any time by turning off access for Vufro in the Health app. History already copied stays in your account until you delete your account, or until you ask us to delete it through the privacy request form.
With a reading we may keep the name of the device or app that recorded it (for example your Apple Watch). The app does not read nutrition or medications from Apple Health, and it does not write anything to Apple Health. It reads reproductive health and sexual activity only for Cycle, as listed above.
3.3 Data you enter or upload
- Food and drink you log, custom foods you create, and label photos you add to a food.
- Foods you send to the shared food catalogue, where that feature is available to your account (see section 7).
- Lab results you type in, lab reports (PDF or photos) you upload, and fitness test results you enter, such as a lab VO2 max test.
- Medical history entries, medications, documents and photos you add.
- Sexual activity you log outside Cycle (the date, and a time if you add one), and daily check-ins you record about how you feel.
- Cycle, which only an account whose profile says female can keep, and which is then on by default: period start and end dates, bleeding and spotting, symptoms and severity, mood, energy and sex drive, notes, sexual activity with its times, optional protection details and orgasm, pills you log (such as a birth control pill or a missed pill), fertility observations such as temperature, cervical fluid, ovulation and pregnancy test results, and the position, opening and firmness of your cervix, breast self-exam findings, weight, water and sleep you log in Cycle, skin and hair, tags you create, and relevant context you choose to enter such as contraception, pregnancy or postpartum status. We also calculate cycle summaries and uncertain date estimates from those records. Cycle reminders you turn on (for example for your period, your fertile window, a daily pill or a breast self-exam) are worked out from your own diary and scheduled as notifications on your iPhone. With discreet notifications, a reminder shows only that you have a reminder, so nothing about your cycle appears on your lock screen. With your Apple Health permission, Cycle also holds the cycle records listed in section 3.2; those entries are changed in the Health app. Cycle is optional: you can pause it or withdraw its consent at any time, which also stops reading cycle records from Apple Health.
- If you use Journal: your entries (their date and time, title, text and answers to guided prompts, such as thought records and therapy preparation), the mood, energy and stress ratings, feelings, activities and tags you choose, a place name you type, health context you choose to copy in from your own summaries (for example sleep, steps and resting heart rate), and attachments you add: photos, files, voice recordings and drawings. Earlier versions of an entry are kept so you can restore them. Drafts are also kept on your device, so changes not yet saved to your account can be recovered. Journal backups you export are files saved on your device, protected with a password if you choose one, and a Journal reminder is a calendar file you add to your own calendar.
- Notes, routines and reminders you create.
- Share links you create: a copy of the page you chose to share (see section 7).
- Messages you send through our report form. Anyone can send one without an account. We keep what the form asks for and the time. We do not store your IP address with it.
- If you turn on the AI features: the files you ask the AI to read, the values it finds, and a record of what each reading cost (see section 5).
3.4 Location (only with your permission)
Location is off until you allow it. In the app you choose Off, While using the app or Always, and your iPhone asks for the matching permission. With While using the app or Always:
- Country. The iPhone app works out which country you are in (your iPhone asks Apple's location service to name the country from its approximate position) and sends us only the country, the date and an accuracy figure, never your coordinates. We keep the list of countries and the dates you arrived, to give jet-lag and travel context on your charts.
- UV exposure tracking. This works only with location set to Always, because it has to know where you were whenever you were outside, even with the app closed. While it is on, the app records your precise position (to within about 10 metres) and the time, while you use the app and in the background, including after the app has been closed. It sends them to your account, together with your time in daylight from Apple Health and the name of the device that recorded it. We use them to match your time in daylight with local UV estimates and to draw your travel map. You can turn UV exposure tracking off in the app at any time, and choosing While using the app or Off turns it off; to stop all location, choose Off in the app or turn off location access for Vufro in your iPhone settings. To look up the UV index we send only a rounded position (on a grid of 0.1 degrees, about 11 km) to our weather provider, from our servers, without your IP address or anything about your account.
Separately:
- Workout routes. If you allow workouts on the Health permission screen, the GPS route of an outdoor workout is uploaded, with up to 5,000 points per route, each with its time, latitude, longitude and altitude, and kept with that workout until you delete your account, so we can draw it on a map.
- Maps. When a page shows a map, your browser loads it from Apple's MapKit service. Apple receives your IP address and the area you are looking at, and, when a place is named on the map, the position being named.
- We do not keep any other record of your movements.
3.5 Technical data
- Your IP address and approximate region, which our hosting provider sees on every request. We use the country to block access from sanctioned regions and to protect the Service from abuse. We do not keep a general access log: an ordinary page or request you make is not recorded.
- Short-lived abuse-prevention counters: failed sign-in attempts, counted against a fingerprint (hash) of your IP address and email for 15 minutes; report-form submissions, counted against a fingerprint of your network for 2 days; file uploads, share links, starts of a data download and sign-in starts, counted against a fingerprint of your account and of your network (or, for sign-in, of your IP address) for up to 2 days; and, where the shared food catalogue is available to your account, food submissions counted per network (the first part of your IP address, for example the first three numbers of an IPv4 address) for 2 days, and your account's monthly count of label checks for 40 days.
- Upload records for the iPhone app (when a batch of readings arrived and whether it was accepted), kept for about 90 days to find and fix sync problems.
- Sync reports from the iPhone app. After a sync fails, and otherwise at most once a day, the app sends us the record its Sync log keeps of your recent syncs: when each sync ran, the steps it took and how long they took, the status codes returned and fixed error codes (for example, that a heart rate read stopped at a size limit). A code can name the kind of Apple Health data a step was reading, never a value from it. We use these reports only to find and fix sync problems, and we keep them for 30 days. You can turn them off in the app, under Settings > Apple Health > Sync log.
- The settings and preferences you choose, so they follow you between devices.
- If you turn on notifications, the address your browser gives us for sending them.
- A key the iPhone app creates with Apple's App Attest, which lets us check that a food label photo comes from a genuine copy of the app.
We do not use advertising identifiers or tracking cookies. We use cookies to keep you signed in and protect sign-in. Depending on the features you use, Vufro also saves preferences and local copies of food, health and dashboard information on your device, including copies used for offline loading.
| What is saved | Why it is saved | How long it can remain |
|---|---|---|
| Sign-in cookie (`bh_session`) | Remembers your session using a signed reference, rather than storing your health records in the cookie. | Until 30 days after you last use it, and at most 180 days from sign-in; the server also checks expiry and can revoke the session earlier. |
| Sign-in security cookie (`bh_oauth`) | Protects an Apple or Google sign-in in progress. | Up to 10 minutes. |
| Preferences in `localStorage` | Remembers choices such as theme, units, views and nutrition targets. Some preferences also follow you through your account. | There is no single fixed expiry for all preferences. |
| Local food copies in `localStorage` | Keeps selected food days and food information, and helps prevent removed entries from reappearing from an older copy. | Saved records are limited, but an old saved timestamp does not by itself remove the copy. |
| Health and score copies in `IndexedDB` | Keeps information used to calculate and display health scores. In the iPhone app's dashboard, this can include local Apple Health information. | These copies can persist until replaced or cleared; no fixed expiry applies to every copy. |
| Offline app copies in Cache Storage | Helps load app pages, scripts and selected food files. Some page and food copies can contain health information. | The app keeps its current cache and one previous version. This is a version limit, not a number of days. |
These are all needed for the features you use, so we do not ask for separate consent for them. Closing a tab does not necessarily remove these copies. Using the normal sign-out page attempts to clear app caches and selected local records from that browser. Cleanup can fail or be blocked, and it does not clear other devices. You can use your browser's site-data controls to clear local copies, but this can also remove saved preferences, offline content and sign-in cookies. Deleting your account does not guarantee that every device copy is cleared. Apple Health and other device permissions are separate controls.
Apple and Google may set their own cookies during their sign-in pages. Their privacy information is linked from our sub-processors page.
3.6 Where your data comes from
- From you, when you type it in or upload it.
- From Apple Health and the location services on your iPhone, only for the types you allow.
- From Apple or Google when you sign in with them: your email address (or Apple's relay address), your name if the account shares it, and an account identifier.
- From our AI providers, when one reads a file, a label photo, a front-of-pack photo or a meal photo you uploaded or took and returns the values, names or foods it finds, and when our food classifier finds the product a food you typed in is.
- From your browser's speech service, if you use Journal dictation in a web browser: the text it returns.
- From another Vufro user, when that person gives you a Cycle partner code: you can view their Cycle page.
- From calculations we run on the above, such as your scores.
4. Why we use it, and our legal basis
Where a data protection law asks us to name a legal basis for each use (for example the EU or UK GDPR, if it applies to you while you are travelling there), these are ours:
| Purpose | Data | Legal basis |
|---|---|---|
| Create and secure your account, and keep you signed in | Account data, sign-in records | Our contract with you (GDPR Art. 6(1)(b)); our legitimate interest in security (Art. 6(1)(f)) |
| Confirm you are 18 or older | Date of birth | Our contract with you; our legitimate interest in keeping the Service for adults |
| Apply the rules of the country you live in, and tell you and the right authority about a breach | The country you live in | Our contract with you (GDPR Art. 6(1)(b)); our legal obligations (Art. 6(1)(c)) |
| Store your health data, including your food diary, show it, and calculate your scores and trends | Health data, your food diary, data you enter or upload | Your explicit consent (GDPR Art. 9(2)(a)) |
| Store and display optional Cycle records and work out cycle summaries and estimates | The reproductive, sexual and related data you enter, or allow Vufro to read from Apple Health | Your explicit consent: the Apple Health consent you give at sign-up, which names cycle and sexual activity records, or the Cycle consent if you turn Cycle on yourself; it is apart from the terms |
| Let a partner you give a code to view your Cycle page | Your Cycle records, including notes, your calendar, estimates and insights, and the accounts involved | Your separate, revocable choice to share, made by creating the code |
| Keep your Journal, show it to you and let you export it | Journal entries, ratings, attachments and the health context you copy in | Your explicit consent (GDPR Art. 9(2)(a)) |
| Read a lab report, a food label, the front of a food package or a meal photo with AI | The file or photo, the values, names or foods found | Your explicit consent, asked separately before the first use |
| Find the product a food you type in is | The food's name, brand, barcode and label numbers, under a random reference | Our contract with you; your explicit consent to the food diary, given when you sign up (GDPR Art. 9(2)(a)) |
| Country, UV exposure tracking, workout routes and maps | Location | Your explicit consent (GDPR Art. 9(2)(a)), given when you turn on location in the app and through the location and Health permissions on your iPhone |
| Send reminders and notifications you turn on | Notification address and settings | Your consent |
| Share a page through a link you create | The page you share | Your request (our contract with you) |
| Publish a food you send to the shared catalogue | The food's details | Our contract with you; our legitimate interest in an accurate catalogue for everyone |
| Handle reports, copyright notices and requests, and decide on reported content | Report form messages, the content reported | Our legal obligations; our legitimate interest in a safe and accurate Service |
| Find and fix sync problems in the iPhone app | Sync reports: the steps of each sync, their timings, status codes and error codes | Our legitimate interest in a Service that syncs your data reliably (GDPR Art. 6(1)(f)); you can turn the reports off in the app |
| Block sanctioned regions and prevent abuse | IP address, region, abuse counters | Our legal obligations; our legitimate interest in keeping accounts and the Service secure and stopping misuse |
| Comply with the law, answer lawful requests, and establish or defend legal claims | The data required | Our legal obligations; our legitimate interest; for health data, GDPR Art. 9(2)(f) |
To use the Service you must give an email address (through sign-in), your date of birth and your consent to health-data processing. Everything else is optional: if you do not allow a type of data, the features that need it do not work.
Where we rely on our legitimate interest, you can object, and we will stop unless we have compelling reasons or need the data for legal claims.
We do not use your health data to train AI models. Our AI providers, Anthropic and Google, process the files and photos you ask them to read only to return the result to us, and their commercial terms do not allow them to train their models on them. See section 5 and our sub-processors page.
5. AI features
- What they do. If you turn them on, AI reads a lab report file you upload and turns it into lab values. Where label reading is available to your account, AI also reads the photos of a food label you add, so we can check the food against its label, and reads the brand and product name from a photo of the front of a package you take while adding a food, so the form can fill them in. The front-of-pack photo is sent to Anthropic for that reading only and is not stored by us. If you turn it on, AI also reads a photo of a meal you take to log it: it names the foods it sees and estimates their weight, and you check every food before anything is logged. The meal photo is sent to Google, with the names of foods you have logged recently, for that reading only and is not stored by us.
- Finding the product a food you type in is. To score a food you create by typing its label, our food classifier may compare that food's name, brand, barcode and label numbers with the products in our catalogue and with manufacturers' published information. It sees the food only under a random reference and receives nothing else: not your account, your other foods, or when you ate it. If it finds the product, your food is scored with that product's checked information; what you typed stays private to you and is not published.
- Who provides them. The AI is Anthropic's Claude, except for logging a meal from a photo, which uses Google's Gemini. The features you turn on (reading a lab report, a food label or the front of a package) use Anthropic's commercial API, and logging a meal from a photo uses Google's paid Gemini API: before their first use we ask for your consent, and the consent screen names the company. The food classifier is an automated task that runs on our own Claude account at Anthropic, which is set so that Anthropic does not use what it receives to train its models. It can check any food you type in, without a separate consent screen, as part of the food diary you consent to when you sign up.
- You stay in control. Lab values the AI finds are shown to you to review, correct or discard; nothing is added to your results until you confirm it. A food you send to the shared catalogue is published only when the label check agrees with what you entered.
- It can be wrong. AI output is general information and can contain mistakes. Check important values against the original document, and do not use them for medical decisions.
- Limits. Each account can use the AI features up to a monthly allowance.
- AI does not make decisions about you that have legal or similarly significant effects.
6. What we never do
- We do not sell your personal data, and we do not share it for cross-context behavioural advertising.
- We do not use Apple Health data for advertising, marketing or data mining, and we do not disclose it to anyone except to provide the Service to you.
- We do not make decisions about you that have legal or similarly significant effects based solely on automated processing, with two exceptions: an account is refused or removed automatically if the date of birth shows its holder is under 18, and access is blocked automatically from regions under US sanctions, as the law requires. You can ask a person to review either decision through the privacy request form. Scores are for information only.
7. Who can see your data
- You. Your data is stored in your own account area. Another user can see it only through a sharing feature you explicitly choose, as described below.
- Us. The person who operates Vufro can access the data stored for your account only when needed to run, support or secure the Service, to investigate abuse, or to meet a legal obligation. We do not look through your data for any other reason, and we never use it for advertising or sell it.
- People you choose. If you create a share link, anyone with the link can see the page you shared until the link expires, 48 hours after you create it. A link cannot be withdrawn earlier, except by deleting your account, which removes your share links at once (links made before 4 October 2026 are not connected to your account and simply expire).
- A Cycle partner you choose. Cycle partner access is separate from public share links. In Cycle settings, under Partner access, you can create a partner code. It works once and expires after 24 hours. The signed-in person who enters it sees a read-only copy of your whole Cycle page: all your Cycle entries, including notes, your calendar, estimates and insights. They cannot change anything. Their access lasts until you pause or remove it, which you can do in Cycle at any time. Access you gave before partner codes keeps showing only the categories you chose then. New reads stop when you pause or remove access, but information already seen, copied or captured in a screenshot cannot be recalled. Only give a code to someone you trust to keep it private. An account whose profile does not say female cannot keep its own Cycle diary; it can only view a partner's Cycle page with a code.
- Everyone, for foods you publish. Where the shared food catalogue is available to your account and you send a food to it, the food becomes public once it passes our checks: every user can find it by searching or by scanning its barcode, and sees its name, brand, barcode, nutrition values, serving sizes, ingredients and allergen statement. Your label photos, your name and your account are not shown with it. We keep a record linking the submission to your account until you delete the food or your account. Deleting a food you created removes it, its label photos and that record (the record within a few days), but a copy already published to the catalogue stays, without anything that identifies you; if you want a published food withdrawn, ask us through the report form and we will review it.
- Our service providers, listed in section 8 and on our sub-processors page, only to run the Service and only on our instructions.
- Authorities, only when the law requires it. See our government request policy. We tell you about a request unless the law forbids it.
- A buyer or successor, if the business is sold or merged. We will tell you first, and your data stays under this policy.
8. Where your data goes (international transfers)
We are based in the United States, so your data is processed in the United States. These are the companies that receive personal data, the country it goes to, and the safeguard each relies on where the law of the place you are in asks for one:
| Company | What it does | Country | Safeguard |
|---|---|---|---|
| Cloudflare, Inc. (our service provider) | Hosting, databases, file storage and network security | 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 in Cloudflare's data processing terms |
| Anthropic, PBC (our service provider) | AI reading of files, label photos and front-of-pack photos you upload, and finding the product a food you type in is | United States | European Commission Standard Contractual Clauses in Anthropic's data processing addendum, with the UK addendum and Swiss terms (Anthropic is not certified under the Data Privacy Framework) |
| Google LLC, Gemini API (our service provider) | AI reading of meal photos you take to log a meal, with the names of foods you have logged recently | 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 service provider) | Our email at admin@vufro.app, if you write to us | United States | EU-US Data Privacy Framework, its UK extension and the Swiss-US Data Privacy Framework |
| OpenMeteo GmbH | The UV index for a rounded position (a 0.1-degree grid, about 11 km) and a date, sent from our servers without your IP address or anything 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 for a rounded position (a 0.1-degree grid, about 11 km) and a date, for accounts other than the app's original one, sent from our servers without your IP address or anything about your account | United States | None needed: the rounded position and date we send are not linked to you or your account |
| Apple Inc. (a separate company acting under its own privacy policy) | Sign in with Apple; the maps and place names your browser loads from Apple; your iPhone naming the country you are in | United States | Apple's own terms; this data goes from your browser or iPhone to Apple, not from us |
| Google LLC (a separate company acting under its own privacy policy) | Sign in with Google | United States | Google's own terms |
| Your browser's push service, if you turn on notifications | Delivering an empty wake-up signal | Depends on your browser | The push service's own terms |
| Your browser's speech service, if you use Journal dictation in a web browser (for example Apple for Safari or Google for Chrome) | Turning what you say into text | Depends on your browser | The speech service's own terms; your voice goes from your browser to it, not from us |
Other users see only what you choose to make visible: foods you publish to the shared catalogue, pages you share by link, and your Cycle page, for a partner you give a code to (see section 7). US law can allow US authorities to request data from US companies; we answer such requests only as described in our government request policy. You can ask us for a copy of the safeguards.
9. How long we keep it
- Your account, and the health data and other data in it, including minute-by-minute Apple Health readings and daily summaries: until you delete your account. We do not delete older readings automatically.
- Cycle records: until you delete them or your account. Pausing Cycle and withdrawing its separate consent stops Cycle use and partner access but does not by itself erase your records. Export and deletion remain available. Revoked sharing decisions are retained with your account so the Service can enforce that access has stopped.
- Journal entries, including entries you move to Trash and earlier versions of an entry, and Journal attachments, including ones you remove from an entry: until you delete your account. A complete Journal backup you export includes them.
- Cycle partner access: a partner code until it is used, for 24 hours at most; a partner's access until you remove it or delete your account.
- Your sharing handle and choices from the former Share your data feature, which no longer exists: no longer used, and deleted with your account if we have not removed them before.
- Precise positions recorded by UV exposure tracking, workout routes and the list of countries you were in: until you delete your account.
- Files you upload, such as lab reports and the documents and photos you add to medical history: until you delete the file or your account. Removing a medical history entry or attachment does not by itself delete the stored file.
- Label photos you add to a food: until you delete the food or your account.
- AI reading records (what was found, what it cost), including the foods and weights read from a meal photo: until you delete your account. Anthropic and Google keep the files, photos and results they handle for a limited time under their own policies, linked from our sub-processors page.
- AI spending records (the month, the feature and the amount): kept after you delete your account, but without anything that identifies you, because they count toward the monthly limit we set for all accounts together.
- Signed-in sessions: until 30 days after you last use them, and at most 180 days, or until you sign out or delete your account. The link to your Apple or Google account, and the sealed Sign in with Apple token: until you delete your account.
- Notification addresses: until you turn notifications off, the address stops working, or you delete your account.
- Upload records for the iPhone app: about 90 days.
- Sync reports from the iPhone app: 30 days.
- Daily backup copies of your food log, the foods you created and their label photos: each day's copy is kept for 30 days, so a food log entry you delete can remain in an older copy for up to 30 days. Deleting a food you created removes its copies, and those of its label photos, at the same time. The backup is stored privately in the same place as your account's data and is used only to restore it after a fault.
- Encrypted daily backups of every account: each night we copy the data stored for every account, yours included, seal the copy with a key that only our backup job and the operator hold, and keep each night's copy for 35 days (removing an expired copy can take up to a day longer). Something you delete can therefore remain in an older copy for up to 35 days. Deleting a food you created removes its copies, and those of its label photos, from these backups within about a day. The backups are stored privately with the same provider as your account's data, apart from it, and are used only to restore data after a fault. Sign-in sessions, sync reports, temporary counters and caches are not copied.
- Abuse-prevention counters: 15 minutes to 2 days; the monthly count of label checks: 40 days.
- Security event records: 90 days. These record a small set of events only, never ordinary use: a failed or blocked sign-in, a refused request, a download of your data being started, an account being deleted or suspended, and the operator's own use of administrative access. Each record holds the kind of event, the date and time, the part of the Service involved, the country and network operator (the number Cloudflare reports, not your IP address) and, where the event concerns an account, that account's internal identifier. They never hold an IP address, an email address or a name, and are used only to detect and investigate misuse.
- When our food classifier looks for the product a food you typed in is: the copy of that food's name, brand, barcode and label numbers it reads, 2 days; the random reference that lets us link your food once it decides, 7 days or until you delete your account; and a note that it has already looked at that food, until you edit the food or delete your account.
- Messages sent through the report form, and our decisions on reported content and on suspending accounts: about 13 months. The marker that keeps a food hidden, or an account suspended, after such a decision stays until we lift it.
- Contributors you block: until you unblock them or delete your account. The list holds only the food you blocked someone from and an identifier that means something to your account alone, never who they are.
- An account that was opened but never finished setting up (it never accepted these terms and gave the consents on the welcome screen): deleted automatically 30 days after it was opened, with anything stored for it, in the same way as Delete now on the Account page. We keep a minimal record that this was done, holding only the account's internal identifier and dates.
- When you delete your account, we first hold it for 30 days in case the deletion was a mistake or you change your mind. At once we sign you out on every other device, remove your share links, stop the iPhone app's uploads and stop using your data, but we keep the data itself unchanged. Until the date we show you, you can restore your account exactly as it was by signing in again and choosing Restore. You can instead choose Delete now, which skips the 30 days. When the 30 days are up (normally within a day after the date shown), or at once if you choose Delete now, we remove your account, the data in it, your sign-ins and your share links from our live systems, and we remove your identity from your AI spending records. AI readings already sent to Anthropic are kept by Anthropic only for the limited time its retention policy allows. A background job then removes, normally within a few days, the link between your account and the foods and label checks you sent to the shared catalogue. Foods you chose to publish stay published, as you agreed when you sent them, without anything that identifies you. We keep a minimal record that this clean-up was done, holding only your account's internal identifier. If deletion cannot finish, we tell you and keep you signed in so you can try again; some data may already have been removed. Your backup copies, including your copies in the encrypted backups of every account, are removed within about a day. If an unusual number of accounts are deleted on the same day, we check before removing their backup copies, which can take a few days longer.
10. Your rights
Depending on where you live, you have the right to:
- know what data we hold about you and get a copy;
- have it corrected;
- have it deleted. You can delete your account yourself on the Account page, which removes your data as described in section 9 and, if you used Sign in with Apple, asks Apple to end this app's access;
- restrict how we use it, or object to uses based on our legitimate interest;
- receive it in a portable form. The Download my data button on the Account page saves your records as one file, with a link to download each file you uploaded. For anything the file does not include, such as your sign-in records, ask us through the privacy request form;
- withdraw your consent at any time, without affecting what we did before. Withdraw my consent on the Account page stops all collection and use of your health data at once: the iPhone app stops uploading and the dashboard stays closed until you agree again. Your stored data stays in your account until you delete it with Delete account, or until you agree again; if you want it deleted, use Delete account or tell us through the privacy request form. To stop only new Apple Health data, turn off access for Vufro in the Health app on your iPhone; to stop location, turn off location access for Vufro in your iPhone settings;
- withdraw only your Cycle consent through Cycle. This pauses Cycle processing, including reading cycle records from Apple Health, and partner access without withdrawing the consents for unrelated features; export and deletion remain available. Cycle never turns itself back on; re-enabling it requires agreeing to its consent again;
- not be subject to decisions based solely on automated processing that have legal or similarly significant effects (see section 6);
- appeal our decision on your request, in US states that provide this.
Send requests through the privacy request form, by email to admin@vufro.app, or by post. We reply within one month (30 days), which we may extend by two further months for complex requests, telling you why; where US state law gives us 45 days, we use that period. We may ask you to confirm your request from the email address on your account. We do not charge for this and we will not treat you differently for using your rights.
Complaints to us. If you are unhappy with how we use your personal data, tell us through the privacy request form (choose "Complain about how you handle my data") or by email to admin@vufro.app. The form shows a reference as soon as you send it, which is our acknowledgement; if you write by email, we acknowledge your complaint within 30 days. We look into it and tell you the outcome without undue delay.
Complaints to an authority. You can also complain to the data protection authority where you live, or, if a data protection law applies to you while you are travelling (for example in the EU, the UK or Switzerland), to the authority there.
11. US state notices
- Consumer health data (Washington, Nevada, Connecticut and similar laws): see our Consumer Health Data Privacy Policy, which forms part of this policy.
- California: we do not sell or share personal information, and we do not use sensitive personal information for anything other than providing the Service. The categories we collect are in section 3, the sources are you, your devices and the sign-in provider you choose, the purposes are in section 4, and retention is in section 9.
12. Children
The Service is for adults. You must be 18 or older to use it. If someone enters a date of birth under 18, their new account is removed at once, and a date of birth under 18 cannot be saved later in Settings. If we learn that we hold data about anyone under 18, we delete it.
13. Security
Data is encrypted in transit (HTTPS) and at rest by our hosting provider, and each account's data is kept in its own separate area. Documents you upload (such as lab reports, scans and photos) are also encrypted with a key unique to your account. Access to our systems is limited to the operator. No system is perfectly secure. If a breach affects your data, we will tell you and the authorities as the law requires. To report a security problem, email admin@vufro.app.
Journal entries and their attachments are stored privately with our hosting provider, encrypted in transit and at rest. Journal entries are not sent to our AI provider.
Cycle records are stored privately with our hosting provider, with encryption in transit and at rest managed by the service providers. This is not end-to-end encryption: the operator can access stored records for the limited purposes in section 7. Cycle records are not sent to our AI provider, analytics systems or advertising systems. Partner views are requested from the server and are not kept as a persistent offline diary for the recipient.
14. Changes
If we make a change that matters, we tell you in the app before it takes effect and, where the law requires, ask you to accept the updated documents. Until you accept them you can still download your data and delete your account.
15. Contact
Pick and Pack LLC, 30 N Gould St Ste R, Sheridan WY 82801, USA. Email admin@vufro.app. Privacy request form. Legal notice.