Atisbo does not ask for your name, email address or a password, and does not create a profile about you. There is no login, so there is no account of yours for anyone — including us — to read, hand over, or lose in a breach.
Section 8 covers the one thing that reaches us outside the app: an email, if you send us one.
Your food log, exercise log, weight history, body measurements read from a smart-scale export, your saved foods and your meal photos are stored on your device, in storage belonging to the app. We cannot read any of it. It is never uploaded to us, and deleting the app removes it.
Foods you have logged before are looked up on your device first. When you search for a food, describe a meal, or look up a restaurant dish, the app first checks your own saved foods for the same words. If it finds them, it uses what you logged last time and sends nothing. Only what it cannot find there is looked up as described in section 3.
When an entry’s figures came from fatsecret (see section 3), the app keeps fatsecret’s own number for that food alongside the entry, on your device, together with the credit to them. fatsecret permits its figures to be kept on your device on that condition. It identifies the food, not you.
The app also keeps, on your device, a short record of the notices you have accepted: which version, when, and a fingerprint of the exact wording you were shown. It is included when you export your data. We hold no copy of it and no record of who accepted what.
Your date of birth is asked for and then discarded. The first time you open Atisbo it asks for your date of birth so it can check that you meet the age requirement in our Terms. The date is not stored and is not sent anywhere. Your device does the comparison, keeps only the yes-or-no result, and drops the date itself. There is no birth date in the app's storage, none on our servers, and nothing anywhere that records who answered or what they answered.
Some features work by sending the item you are asking about to an AI service, or to an outside nutrition database. This only happens when you take that action.
| Feature | What is sent | Sent to |
|---|---|---|
| Photo estimate | the photo or photos you took (up to three), any description you typed alongside them, and the names of up to ten foods you have recently logged or saved, so a repeat item can be recognised. Names only — no amounts, times or dates | Anthropic PBC |
| Text search — not in our own databases | the words you typed, sent from our server first to Open Food Facts, then to fatsecret; then, if neither has a match, to the AI service for an estimate. The foods the app picks out of “just tell me what you ate” are looked up the same way, by name. Answers from fatsecret are not stored on our server | Open Food Facts, then fatsecret (Australia), then Anthropic PBC |
| Describing a meal in your own words | the sentence you wrote, so it can be turned into entries. Sent whenever you use this feature, not only when a lookup fails | Anthropic PBC |
| Restaurant dish — chain in our menu database | when your order is not a single listed item: the restaurant name, the dish you typed, and that chain’s menu item names, so the AI service can say which items were ordered. The nutrition figures come from our own database, not from the AI service | Anthropic PBC |
| Restaurant dish — chain not in our database | the dish you typed, for an estimate. The restaurant’s name is sent with it only when it is a chain we recognise; for any other restaurant the dish is estimated the same way a text search would be, and the restaurant’s name is not sent | Anthropic PBC |
| Barcode we do not recognise | the barcode number alone, sent from our server when the product is not in our own reference database: first to Open Food Facts, then, if it does not have the product, to fatsecret. The answer Open Food Facts gives for a barcode is saved on our server against that barcode (see section 4) so nobody has to ask again. Answers to searches are not saved, and an answer from fatsecret is not saved | Open Food Facts (a non-profit, France), then fatsecret (Australia) |
Voice dictation: your microphone, not your audio. When you dictate, your own device turns the speech into text and passes us only the text, which is then handled exactly like text you typed. We never receive audio, and no recording is made or stored anywhere.
This deserves a plain explanation, because the usual browser behaviour is the opposite. Most browsers implement speech recognition by streaming the microphone audio to their own servers — Google's in Chrome, Microsoft's in Edge. Atisbo does not use that mode. It uses on-device recognition only, and where a device cannot transcribe on its own the microphone button is simply not offered and you type instead. We would rather drop the feature on a device than send your voice to a company that is not named in this policy.
What is not sent: your name, your email address, your location, any identifier we hold for your subscription, and — with the one exception in the photo row above, which is names only — your stored history and your other entries. The request carries the item you submitted and nothing that ties it to you or to your other activity.
Getting there. The request passes through Cloudflare, which hosts our service and necessarily sees your device's IP address in order to route it. Request-level logging is switched off, and that setting is checked on every build. Cloudflare does not receive your content for any purpose of its own.
These providers process what they receive under their own terms and their own privacy policies. We do not control what they do with it or how long they keep it, and we do not make claims on their behalf — please read their terms directly:
Product data returned by Open Food Facts is made available by Open Food Facts under the Open Database License (ODbL). The app names Open Food Facts on any result that came from it.
Nutrition data returned by fatsecret is shown with the credit “Powered by fatsecret”, linked to their website, on any result that came from it. The credit is a plain link: nothing is loaded from fatsecret when the result is shown.
We do not keep the item you submitted after the result is returned to your device, and we never store it against you, your device, or your subscription record. A photo you take is saved with the meal on your device so you can see it later; that copy is yours and is not uploaded to us.
Three things, and none of them is about you.
First, one subscription record — so the app knows your subscription is active and how much of your plan you have used. It contains a random identifier created for this purpose, your plan, the dates of your current period, a usage count, and a one-way scrambled form of your store purchase receipt.
It does not contain your name, your email address, a device identifier, your location, or anything you have entered in the app. The random identifier is not derived from anything about you or your device, and it cannot be used to work out who you are. Its only job is to let our server recognise a paid subscription without knowing whose it is.
Second, a shared barcode table. When Open Food Facts answers for a barcode, we save its answer against that barcode so the next person who scans the same product gets it without our asking again. A barcode names a product, not a person: the table holds no record of who scanned it or when, and a copy of the whole table would say nothing about any customer.
Nothing you type is saved in it, or anywhere else on our server — not the words of a search, not a food from “just tell me what you ate” or the sentence itself, not a restaurant or a dish, not an activity, and not an estimate the AI service made. Each is used to answer you and then dropped. Answers from fatsecret are never saved, and photos are never saved. The reuse of foods you eat often happens on your device, from your own saved foods (section 2).
Third, feature counters. For each kind of lookup — photo, barcode, search, restaurant, describing a meal — we count how many times it was used across all users in each hour, day and month, which step answered it (our own database, an outside nutrition database, or the AI service), and what the AI service charged us for it in total. For a restaurant chain on our list of large chains that we have no menu data for, we also count how many times it was asked for in each month — the chain’s name and a total, nothing else; a restaurant that is not on that list is never recorded. We use these to see which steps are working, which menus to add, and to set prices. They are totals with nothing in them about any person: no identifier, no content, no sequence of what one user did.
Purchases and subscriptions are handled by Google Play. We never receive your payment details, card number or billing address. Your store tells our server only whether a purchase is valid. As with any app sold through a store, the store gives us commercial reports about sales; those come from Google, not from the app, and we cannot connect them to anything you submit.
You can stop all transmission by not using the AI features; the rest of the app continues to work. Deleting the app removes everything stored on your device.
You can also ask us to cancel the subscription record we hold. We deactivate it and keep the deactivated record as part of our billing history — it contains no information about you or about what you used the app for. This ends access to paid features. To ask, email [email protected] with your Google order ID.
We will have your email address and whatever you wrote, the same as any correspondence. We ask for your Google order ID, use it to answer you, and then delete the thread. We do not build a customer list from it, and nothing from that exchange goes into the app or its database.
Atisbo is for adults. Our Terms set a minimum age of 18, and the app asks for your date of birth before you can use it, checks that date on your own device, and does not let you continue if you do not meet the requirement. As explained in section 2, the date itself is not stored and is not transmitted — only the yes-or-no result is kept, on your device.
We should be plain about what that check can and cannot do. It establishes that every person who uses the app was asked. It cannot verify the answer, because there is nothing here to verify it against — and building something that could would mean collecting identity documents, which would be a far larger intrusion than the problem it solves.
Atisbo is not directed to children and is not listed in Google Play’s Families programme. We do not knowingly collect information from children, and because the app has no account and stores your food log on your own device, there is no profile of any user — child or adult — for us to hold. If you believe a child has used the app, deleting the app removes everything it stored; there is nothing on our side to delete.
What changed in version 1.7 (22 October 2026). We keep less. Until this version the shared lookup table in section 4 also saved the AI service’s estimate for a food described in words, the answer Open Food Facts gave to a search, how a restaurant order was matched to a chain’s menu, and the effort level of an activity, each against the words that were typed. None of that is saved any more, and what had been saved is deleted: the table now holds Open Food Facts answers for barcodes only. Instead, the app looks in your own saved foods on your device first (section 2). For a restaurant we have no menu data for, the restaurant’s name is now sent to the AI service only when it is a chain we recognise (section 3). Section 4 now also describes the monthly count of requests for chains on our list that we have no menu for, which has been kept since September 2026. No new recipient, no new category of information and no new purpose; nothing you need to accept again.
What changed in version 1.6 (10 October 2026). A new recipient was added: fatsecret (Secret Industries Pty Ltd, Australia), a nutrition database. When a food you search for, or a food the app picks out of “just tell me what you ate”, has no match in our own databases or Open Food Facts, the words are now sent to fatsecret before the AI service is asked; and a barcode Open Food Facts does not have is sent to fatsecret. It receives the words or the number and nothing else. Its answers are not stored on our server. Section 2 now says the app keeps fatsecret’s number for a food with the entry, on your device. The in-app notice was reissued as version 6 and is shown again to every user.
What changed in version 1.5 (26 September 2026). Nothing about what we collect, send, keep or share. A note in the page’s source code was removed, and because every edit to this policy gets a new version number, this is version 1.5.
What changed in version 1.4 (3 September 2026). Open Food Facts, already a recipient for barcodes, now also receives the words you type when you search for a food that is not in our own databases, and the food names the app picks out of “just tell me what you ate”. It is asked before the AI service, so more searches are answered from published product data and fewer are estimated. No other recipient or category changed. The in-app notice was reissued as version 5 and is shown again to every user.
What changed in version 1.3 (2 September 2026). A new recipient was added: Open Food Facts, which receives the bare barcode number from our server when a scanned product is not in our own reference database. Two rows in the section 3 table were widened: a photo estimate now also carries a description you type and the names of up to ten recently logged foods; and for a restaurant chain we have menu data for, an order that is not a single listed item now sends the chain’s item names to the AI service so it can say what was ordered, with the figures still coming from our own data. Section 4 adds the barcode and order answers to the shared lookup table, and adds a third stored thing: aggregate feature counters, which contain nothing about any person. The in-app notice was reissued as version 4 in the same release and is shown again to every user.
What changed in version 1.2 (29 August 2026). The app now asks for your date of birth on first use, to check the minimum age in our Terms. Section 2 and section 9 were rewritten in the same release to say so, and to state plainly that the date is checked on your device and then discarded rather than stored or transmitted. Section 2 also now describes the record the app keeps, on your device, of which notices you accepted and when. No new recipient was added — Anthropic remains the only one, and the table in section 3 is unchanged — and nothing new began being collected by us.
Version 1.1 is withdrawn. Two different documents were published under that single label: an original, and a later amendment adding the restaurant-dish row to the table in section 3. Because a version number that identifies two different documents makes every reference to it ambiguous, 1.1 is withdrawn rather than corrected, the number is not reused, and version 1.2 supersedes both. The substance of the later 1.1 is carried forward here unchanged; nothing that was disclosed has been removed. Every published version of this policy is archived and can be produced on request.
What changed in version 1.1 (28 August 2026). Features were added to the app — describing a meal in your own words, voice dictation, barcode lookup, and an estimate for restaurant dishes we have no menu data for — and this policy was updated in the same release so it describes what the app actually does. Section 3 gains a row for the sentence you write when you describe a meal, a row for the restaurant and dish you type, and states plainly that voice audio never leaves your device. Section 4 no longer says barcodes are resolved by the AI service: they are answered from our own reference database, so nothing about a scan is transmitted to anyone. Section 2 now mentions your exercise log and the body measurements read from a scale export, which like everything else you record stay on your device. No new recipient was added — Anthropic remains the only one — and no new category of information began being collected.
If this policy changes we will post the new version here and update the version number and effective date above. If a change is material — a new recipient, a new category of information, a new purpose — we will tell you in the app before it takes effect.
AscentApps LLC · [email protected] · Arizona, USA