Privacy policy for Bariatrisk Reise

Last updated 5 November 2026
Norsk · Svenska · Dansk

In brief

Bariatrisk Reise stores everything you enter — food, drink, vitamins, medicines, weight and body measurements — only on your own phone. There is no user account, no server that receives your log, no analytics tools and no advertising.

Some things do still leave the phone, and you should know about them: search terms when you search for foods, barcode numbers when you scan, and technical diagnostic information from Google’s scanning library. If you use AI — to read the diet plan or estimate a meal from photos — the photos you choose and what you write about the food are sent for AI reading, but only after you have given your consent. If you ask BariAI about your plan (iPhone and iPad), your questions and an overview of your plan are sent in the same way. This is explained below.

Who is responsible

The app is developed and run by Ingvard Tjelta, Norway. Questions about privacy can be sent to ingvard.tjelta@gmail.com.

The developer receives or stores none of the information you enter. It stays on your device, under your control. The only exception is AI: then the photos you choose, what you write about the food, and what you ask BariAI, pass through a service the developer runs, which forwards them without storing them (see below).

What is stored, and where

The following is stored locally on the phone, in the app’s own storage area:

This is health data. It remains on the device until you delete it yourself, or delete the app. It is included in a regular iPhone backup if you have that switched on, and is then subject to Apple’s terms for iCloud.

Apple Health and Health Connect

On Android, you can similarly connect the app to Health Connect. The app only asks to read steps, workouts, active energy (to show measured energy for a workout) and weight, and to save the weight you record in the app. You choose what the app gets, and change it in Settings → Health Connect. Whatever is retrieved is handled exactly as described for Apple Health below.

On iPhone, you can choose to connect the app to Apple Health (HealthKit). The app then reads steps, workouts and weight from Health — including what the Fitness app, Apple Watch or a smart scale has saved there — and can save the weight you record in the app to Health. You choose what the app gets access to, in the iPhone’s own prompt, and can change it at any time in the Health app.

What the app retrieves from Apple Health or Health Connect is stored on the phone together with the rest of your log. It is never sent out of the phone: not to the developer, not to the AI service and not to anyone else. It is not used for advertising or marketing. It is only included in the report or the backup if you create and share them yourself.

Calendar and app lock

If you choose Import from calendar, the app reads the appointments in the calendar on the phone for the next six months and shows them to you. Only the ones you tick are added to the app. The calendar is not read otherwise, and nothing from it is sent out of the phone. Access can be withdrawn in the phone’s settings.

If you switch on the app lock, the app asks the phone to confirm that it is you — with Face ID, fingerprint or passcode. The app only receives the answer yes or no, never the face, fingerprint or passcode itself.

Purchases and subscription

AI requires a subscription, because every use costs money. The subscription also gives some insight features; the rest of the app is free. The subscription is bought and paid for in the App Store (iPhone) or Google Play (Android), under Apple’s and Google’s own terms and privacy policies. The developer never receives card details, your name or your email address.

To know whether the subscription is valid, the app sends a reference to the purchase with each AI request. The reading service then asks Apple or Google directly whether the purchase is valid, and which tier it gives. The answer is remembered for at most six hours. The number of uses is counted per purchase, and the counters are deleted after two days (per day) and 40 days (per month). Nobody else is told about the purchase.

What is sent out of the app

To whomWhatWhen
Kassal.app The search term you type, or the barcode number you scan, together with your own API key Only when you search or scan, and only if you have entered a key
Open Food Facts The search term or the barcode number Only when you search or scan. In addition, the app makes one lookup at start-up to check whether internet access works
Google ML Kit Technical information about the device (model, operating system version, hardware) and usage and performance data for the scanning feature When you use the barcode scanner
The developer’s reading service, hosted by Cloudflare The photos you choose — of the diet plan, or of the food, a recipe or a package —, what you write about the food, the random device ID, and when you read in a new document from the plan: an overview of what is already in your plan (phase names, rules, notes and supplements), so the AI can point out what is repeated. If you have chosen a language other than Norwegian in the app, the language choice is sent too, so the answer comes in that language. If you have a subscription, also a reference to the purchase. The service forwards the photos and the text to Anthropic and does not store them. It only counts the number of uses per device ID or purchase, per day and per month; the counters are deleted after two days and 40 days Only when you tap ‘Read the plan’ or ‘Estimate the meal’ or ask BariAI, and only after you have given your consent
Apple (App Store) or Google (Google Play) The reference to your purchase, sent from the reading service to check that the subscription is valid When you use AI and have a subscription, at most once every six hours per purchase
Anthropic (Claude), USA The same. Anthropic reads it and returns phases, rules and supplements from the plan, or an estimate of what you have eaten. You review it before anything is added. If you ask BariAI, Anthropic returns the answer, with sources from the plan. If you have written the name of a restaurant or a brand, Anthropic can look it up online; the search consists of words such as the name of the place and the dish, not the photos Same as above

About AI. A photo of a diet plan from the hospital is health data, and may contain your name, national identity number and address. Cover these up before you take the photo. Photos of meals and what you write about them are also information about your diet. Anthropic deletes what is sent to them within 30 days, except for content that their safety systems flag, or that the law requires them to keep, and does not use it to train its models. See Anthropic’s retention rules. Anthropic is based in the USA, so the photos are processed outside the EEA.

When you ask BariAI (iPhone and iPad). BariAI answers questions about your plan, with sources from the plan, and the answers are marked as AI. Your questions are sent together with an overview of your plan: the type of surgery and which day you are on, all the phases with their days, rules, daily list and targets, the notes and supplements, the items in “Check the setup”, allergies and what you tolerate poorly or dislike, your own targets, your meal pattern, recipes from your cookbook and a summary of the figures from today and the last week. Names, dates, weight, body measurements, medicines, daily notes and photos are not sent. The conversation only exists in the app while it is open; the service does not store it, and Anthropic deletes it within 30 days.

The barcode recognition itself takes place on the device — the camera image is not sent anywhere. However, Google’s library collects diagnostic and usage data, as Google itself describes in ML Kit’s data disclosure and terms and privacy.

None of these recipients receive your meal log, weight, body measurements, medicines or notes. They only receive what is listed in the table and under ‘When you ask BariAI’.

When you share a meal. ‘Share meal’ sends the foods, amounts and nutritional content of that one meal to a small service at Cloudflare, which stores them for 30 days and returns a short link. You share the link yourself, with whoever you like. No name, device ID, plan, weight or anything else about you is stored — only the meal itself. After 30 days it is deleted. The service keeps no logs, and only retains a day-stamped, irreversible hash of the IP address for one day to limit misuse. The person you share with sees what you share and decides for themselves whether to add it to their own log. Without an internet connection, a link is created instead with the meal contained in the link itself, and then nothing is stored with us.

User-shared (recipes from other users). Off by default; switched on under About you. If you share a recipe, the name of the dish, the ingredients with amounts and nutritional content, the method, time, servings and the photo (if you have added one) are sent to a service at Cloudflare, where the database and photos are kept in the EU. The developer reads the recipe and approves it before it becomes visible to others who have switched on User-shared. No name, email or device ID is stored — only a hash of a random key that is kept on your phone, so that you can see the status and delete what you have shared. The photo is redrawn in the app before it is sent, so location and other metadata from the camera are not included. If you report a recipe, the reason you choose is stored. The service keeps no logs, and only retains a day-stamped hash of the IP address for one day to limit misuse. What you share stays there until you remove it (in the recipe, or by switching off User-shared and choosing to remove everything) or the developer takes it down. The recipes are made by other users, not by the hospital or the app. The alerts about allergies and your plan are calculated on the phone; your plan and your allergies are never sent.

What the app does not do

Legal basis

The processing takes place locally on your device, on your own initiative and under your control. The developer has no access to the information.

For the outgoing calls in the table above, the basis is your own consent, given by choosing yourself to search, scan or enter an API key. If you do not use search or scanning, nothing is sent — except for the one start-up lookup to Open Food Facts, which contains no information about you.

For User-shared, the basis is your consent, given by switching it on and choosing yourself what you share (Article 6(1)(a) of the General Data Protection Regulation (GDPR)). The recipes must not contain health data; do not write anything about yourself in them.

For checking the subscription, the basis is the subscription agreement (Article 6(1)(b) GDPR).

For AI, the basis is your explicit consent (Article 9(2)(a) GDPR), which you give in the app before first use. You can withdraw it at any time via the menu at the top right → About the app.

Your choices and rights

Because everything is on the device, you have full control directly in the app:

Under the General Data Protection Regulation (GDPR), you have the right of access, rectification, erasure, restriction and data portability. Since the developer has no access to the information, you exercise these rights yourself in the app. If you wish to complain, you can contact the Norwegian Data Protection Authority (Datatilsynet) or the data protection authority where you live.

Children

The app is made for adults who are going to have or have had bariatric surgery, and is not aimed at children.

Changes

If this policy changes, the date at the top is updated. Significant changes will be announced in the app.

Contact

Ingvard Tjelta, Norway
ingvard.tjelta@gmail.com