← Back to Thali

Privacy Policy

Effective 27 August 2026 · Last updated 27 August 2026

This policy explains what Thali collects, why, who else sees it, and how long it is kept. It is written to be read. Where a detail is awkward, it is stated plainly rather than left to a phrase like "and other similar data".

1. Who we are

Thali ("Thali", "the app", "we", "us", "our") is an iOS calorie and nutrition tracking app. It is operated by Upwan Chachra, an individual developer based in Calgary, Alberta, Canada. For the purposes of the EU and UK GDPR, Upwan Chachra is the data controller for the information described in this policy, and can be reached at krish.aerialmedia@gmail.com.

This policy covers both the Thali mobile application and this website. Section 15 describes what the website itself does, which is much less than the app.

2. Age restriction

3. What we collect

• Account information. Your email address, and a password that is stored only as a salted hash by our authentication provider. We never see or store your password itself.
• Account identifier. When your account is created we assign it an ID. It keys every row we store for you, and it is the identifier we send to RevenueCat so your subscription follows you across devices.
• Profile and body metrics. Date of birth, sex, height, current weight, goal weight, and activity level. These are the inputs to the metabolic-rate formula that sets your targets, and your date of birth also confirms you are 18 or older.
• Nutrition goals. The daily calorie and macronutrient targets calculated from your profile, and which subscription plan you selected.
• Food and meal logs. The foods you log, their nutrition values and timestamps, the names you give dishes, dishes you save for reuse, and any free-text note you attach to a photo for context.
• Food searches. The text you type when you look up a food. It is sent to the AI and nutrition database services in section 7 to be identified, and it is retained in the shared cache described in section 6.
• Weight history. The weights you log over time.
• Streak data. Your logging streaks and the counters behind them.
• Subscription status. Whether you have an active subscription. Your payment is processed by Apple, and we never receive your card details.
• Usage records for abuse prevention. When you use an AI feature, our servers record your IP address, which feature ran, and a timestamp. This is used to enforce rate limits and nothing else. Retention is covered in section 9.
• Server error logs. When a lookup fails, our servers write a short diagnostic log that can include the text you typed and your user ID. These are held by our backend provider for a short operational period, are used only to fix faults, and are not part of the account database.

We do not collect your name, phone number, address, contacts, precise location, or advertising identifier. The app does not ask for them and has no code that reads them.

4. Photos and AI analysis

When you photograph a meal, the image is resized on your device and sent to Google's Gemini API to identify the food and estimate its nutrition. We do not store your meal photos. The image is held in memory only for as long as it takes to answer that one request, and is then discarded. There is no photo storage in our backend, and no code path anywhere in the app that uploads a photo to a file store.

We do not use your photos, food logs, or any other content to train our own models, and our agreements with our AI providers do not permit them to use your content to train theirs. When you log food by typing instead, the text of your query is sent to the AI and nutrition database services listed in section 7.

5. How we use it, and our legal basis

If you are in the EU, the UK, or another region with similar law, we must have a lawful basis for each use. Here they are, mapped one to one.

One row of that table deserves plainer words than a category label. Your weight, height, goal weight and what you eat are measurements of your body, and tracked over time they can say something about your health. We treat them accordingly. They are used for exactly one thing: calculating your calorie and macro targets and showing you your own history. We do not use them to infer anything else about you, we do not use them for advertising, and we do not share them beyond the providers listed in section 7. Where we rely on legitimate interests you can object, and section 11 explains how.

6. The shared food cache

Asking an AI model the same question twice costs money and returns the same answer, so we keep a shared cache of food lookups. When anyone looks up a food by typing, the text of that query and the nutrition result are stored in a single cache that all users share.

The cache is keyed by the query text itself, for example "3 eggs two toast" or "chicken shawarma". It has no user column. Nothing in it records who typed a query, when, or from which account, and it cannot be searched by user.

The consequence is worth stating plainly rather than leaving you to discover it: the cache is not designed to hold anything about you - no entry records who typed it - so deleting your account does not remove entries from it. What remains is the query text and its nutrition values, indistinguishable from the same query typed by anyone else. Because the key is the text you typed, please do not put personal details - your name, a health condition, anything about yourself - into a food search. If a query you typed contains something personal, or you would like any entry removed for any reason, email us and we will remove it.

7. Who we share information with

We do not sell your personal information, and we never have. We share data with the following service providers only as needed to run the app. Each one receives the minimum that its job requires.

We may also disclose information if required by law, or where necessary to protect rights, safety, or the integrity of the service.

Which of these see your IP address

Your IP address is not forwarded to the AI or nutrition lookup providers. Requests to Google Gemini, Anthropic and USDA are made by our servers, not by your device, so those three see our server's address and never yours.

Services your device contacts directly do see your IP address, because that is unavoidable in any direct network connection. Those are Supabase (every time the app loads or saves data), RevenueCat (when it checks your subscription), Apple (when you purchase or restore), and Open Food Facts (only when you scan a barcode). Netlify sees it when you visit this website.

8. Where your data is stored and processed

Your account and app data are stored in Canada, in Supabase's Canada Central region. Some processing happens elsewhere: the AI and nutrition lookup providers above may process your queries and photos on servers in the United States or other countries. By using Thali you understand that your information may be transferred to and processed in countries other than your own, which may have different data protection laws. Where such a transfer involves personal data from the EU or UK, it is made under the relevant provider's standard contractual clauses.

9. How long we keep it

Retention is enforced by an automated job that runs daily, not by intention alone.

Deleting your account removes your usage records immediately, rather than waiting for the windows above to expire.

10. Security

Every connection between the app and our servers uses HTTPS. Passwords are salted and hashed by our authentication provider and are never stored in readable form. Your login session is held in the iOS Keychain on your device, which is encrypted by the operating system. Access to the database is restricted by row-level security rules, so one account cannot read another's data. Our managed database provider encrypts stored data at rest.

To be precise about what that does not mean: Thali is not end-to-end encrypted. Your food logs and weight history are stored in a form our backend can read, which is what makes features like your history and charts possible. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

11. Your rights and choices

Depending on where you live you may have rights to access, correct, export, or delete your personal information, to object to or restrict certain processing, to withdraw consent, and not to be discriminated against for exercising any of them. Thali gives every user these controls regardless of location.

• Access and correct. View and edit your profile, goals and logged data directly in the app.
• Delete. Settings, then Delete Account. This permanently removes your account, profile, food logs, weight history, streaks, saved dishes and abuse-prevention records, and instructs our subscription provider to delete your customer record. Your deletion never waits on a third party: if that instruction fails, everything else is still removed. The two exceptions are described in sections 6 and 9: the shared food cache, which is not linked to any account, and short-lived server error logs. Deleting your account does not cancel your Apple subscription, which you cancel in iOS Settings under your Apple ID.
• Export. Email us for a copy of your data in a portable format.
• Withdraw consent or object. Email us, or use Delete Account.

Reach us at krish.aerialmedia@gmail.com. We aim to respond within 30 days. If you are in the EU or UK and are not satisfied with our response, you may complain to your local supervisory authority.

12. California residents

This section is for California residents under the CCPA as amended by the CPRA. In the previous twelve months we collected the categories below. We did not sell or share personal information as those terms are defined by the CCPA, and we have no plans to.

The health information in the table above - your body metrics and food intake - is sensitive personal information as California defines that term in section 1798.140(ae). We collect and use it only to provide the service you signed up for: calculating your targets and keeping your logs. We do not use it to infer characteristics about you, and we do not sell or share it. You may exercise your rights to know, delete, correct, and limit the use of sensitive personal information through the app or by emailing us, and we will not discriminate against you for doing so. Because we do not track users across sites, we do not respond differently to Global Privacy Control or Do Not Track signals; there is nothing for them to switch off.

13. Canadian residents

Thali is operated from Alberta and your data is stored in Canada, so Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) applies. Under PIPEDA you have the right to access the personal information we hold about you, to challenge its accuracy and have it corrected, and to withdraw consent subject to legal and contractual restrictions. The rights and contact route in section 11 cover all of these.

If you have raised a concern with us and are not satisfied with the outcome, you may complain to the Office of the Privacy Commissioner of Canada.

14. No tracking or advertising

15. This website

This site is a set of static pages. It sets no cookies, runs no analytics, and has no login, no forms, and no way to identify you.

Two things happen anyway, and you should know about both. Netlify, which hosts these pages, records standard web server logs including your IP address. The pages load their two typefaces from Google Fonts, which means Google receives your IP address when the fonts are fetched. Neither is used to identify you, and neither is connected to your Thali account.

16. Changes to this policy

We may update this policy from time to time. If we make material changes we will update the date at the top and, where appropriate, tell you in the app. Continuing to use Thali after a change takes effect means you accept the updated policy.

---

Contact

Questions, requests, or a privacy concern: we would rather hear about it than not.

Home · Terms of Service · App Store