Your food data stays on your phone.

Most food apps treat your diary as something to hold for you. Adra treats it as something that belongs where it was made. That difference is not a setting you switch on. It is how the app was built from the first line.

• Every photo you take and every meal you log.
• Your full diary, corrections, and favorites.
• Your targets, your notes, and your history.

None of it is uploaded. None of it is synced. There is no server that holds a copy of your food life, because there is no server to hold it. The list above is not a promise about what the app chooses to send. It is a description of what the app is able to send, which is nothing.

Most privacy pages describe a policy and ask you to trust it. Here is something better. The entire network traffic of Adra fits on one line, so it can be written out in full rather than summarized.

That is the whole request. A barcode number goes out and a product name comes back. Nothing you photographed is part of it, and nothing about your diary is either. When a claim can be shown this completely, there is no need to take it on faith.

Photo recognition runs on the phone's own chip, using models that ship inside the app. The food catalog travels with you too. 247,065 foods, searchable offline with no connection at all.

That is why airplane mode changes nothing. There is nothing to reach for, because everything is already there.

Barcode lookups are the single exception, and they are optional. When you scan a packaged food that is not already in the local catalog, the app asks Open Food Facts, a public food database, for that barcode number. The catalog travels with the app, so this happens only for products it does not already know.

The request carries the barcode number. Your photos are not part of it, and neither is your diary. Skip packaged foods and the app never touches the network at all.

Google Play requires every developer to declare what an app collects and shares. Adra's data safety label says:

Those words come from the developer and they are shown on the store page. You can read them yourself on the Play listing.

Most data breaches are described as an attacker reaching a company database. That description assumes a company database exists. Here it does not. There is no login to steal and no store of diaries to leak, because Adra keeps no accounts at all. I did not want to hold anyone's food diary, so the app was built without a place to hold it. Your diary is stored on the phone, in the same private storage as the rest of your apps.

Backups are a zip file you export and keep, photos included. Move to a new phone by restoring that file. There is no cloud account involved, and nothing depends on a server staying alive. The copy of your history is the one you hold.

Delete the app and it takes the diary with it. Your phone's own backup settings apply, as they do for any app.

No cookies. No analytics. No third-party requests. This page loads only from this domain, and there is no consent banner because there is nothing to consent to. A privacy claim is easier to believe when the page making it behaves the same way.

Food logs are personal. They reveal health, habits, and beliefs, and they say something about a person that most data does not. Adra treats them the way they deserve, and the site does the same. More detail lives in the privacy policy.