Privacy Policy
Last updated 20 November 2026
This policy covers the MassDelta app, on iPhone and on Android, and the websites norply.co and massdelta.app. It is written to be read. The short version is in section 2; the rest is the detail behind it.
1. Who is responsible for your data
Norply Inc., a Delaware C-Corporation registered at 131 Continental Dr, Suite 305, Newark, DE 19713, USA, is the data controller for everything described here. For any question or request, email founders@norply.co.
2. The short version
- You sign in with Apple or Google. Since version 2.0 the app needs an account. We receive the email address Apple or Google shares (Apple can give a private relay address instead of your own) and nothing else about you: no name, phone number or location.
- Your plan and your log are kept in your account on our server as well as on your phone. That lets another phone restore them, and it lets Delta, the coach, work while the app is closed: it reads them to decide whether to text you and to set each week’s calorie target. Nothing goes up until the app has shown you what it keeps.
- Some of it is read by a model. A meal description or photograph is sent so a model can read the calories off it; a question to Delta is answered from what your account holds; Delta’s texts and weekly reviews are written the same way. What is kept afterwards, and for how long, is in section 6.
- We do not sell it, share it for advertising, or track you across apps. The app has no advertising identifier. On massdelta.app, outside the EU, the EEA, the UK and Switzerland, Google’s advertising tag sets cookies to count taps through to the App Store (section 12); norply.co sets none. The app tells PostHog, our analytics provider, which screens you open and what you tap, so we can see what works. It never sends your meals, weights or chats that way, and you can turn it off in More › Privacy. Daily grades of your progress, and what you search for in Log food, go to PostHog only if you say yes on a separate screen.
- Deleting is in the app: More › Account › Delete account removes the account and everything it holds. Section 10.
3. What the app collects, and why
Most of what the app sends is sent to make the app work. Two things are sent to improve it instead, and you can turn both off: usage events, and your progress (daily grades and food searches), which are only sent if you say yes.
| What | Why it leaves the phone |
|---|---|
| Meal descriptions, typed or dictated | To read calories and macronutrients off them. If you dictate, your phone’s speech recognition may send the audio to its provider to transcribe it (Apple on iPhone; on Android usually Google); the app receives text. |
| What you say in voice mode | In voice mode, what you say is streamed to OpenAI, which turns it into text for Delta. We don’t receive or keep the audio. |
| What you search for in Log food, and barcodes you scan | To find the food. Everyday foods are found on the phone itself. Anything else is looked up in our own copy of USDA FoodData Central and Open Food Facts, on our server. A barcode we don’t have is looked up from the phone on Open Food Facts, which receives the barcode and your IP address and nothing else. A nutrition label you photograph becomes your own food and is never sent to Open Food Facts. |
| Photographs of meals and nutrition labels | To read what is on the plate or the panel. Taken with the camera or chosen from your library, with your permission. |
| A few settings with each meal | Your unit system, language, local hour, the names of things you logged recently, and any diet or allergy you set — so the reading fits how you eat. |
| What you ask Delta | When you ask Delta a question, the server reads what the answer needs from your account — your plan, recent logs, weigh-ins, notes and earlier conversations — and sends it to the model with your question, so the answer can be about you. The question and the answer are kept as section 6 says. We may read some conversations to improve Delta. |
| Your email address and a sign-in id from Apple or Google | To know which account is yours, and to bring it back on another phone, iPhone or Android. We never see your Apple or Google password. |
| Your plan, meals, weigh-ins, saved foods and meals, settings, your chats with Delta and its texts | Kept in your account so a new phone picks up where this one left off, and so Delta can read them when it decides on a text or a target. Nothing is uploaded until you have seen what the account keeps and continued. |
| Delta’s texts | Through the day our server reads your plan and log to decide whether a text would help: a creatine dose not logged yet, a weigh-in reminder, a day heading off course while there is still time to fix it, logs that stopped, how your week is going. When it would, the model writes it and it arrives as a notification, delivered by Apple on iPhone and by Google (Firebase Cloud Messaging) on Android. You can turn each kind off, or all of them, in More › Notifications. |
| The weekly target review | Once a week Delta goes through your log and weigh-ins and sets your calorie target for the week ahead. To do the arithmetic, the model is handed your log as files, which are deleted as soon as the review is done. The decision and its reasoning are kept in your account, so the next review can build on it. |
| What Delta remembers of a conversation | After a chat, the server writes one line summing it up, so Delta can recall it later. These lines are kept in your account, are in your data download, and go when you delete the account. |
| A device id, a push token, time zone, language and app version | To tell your phones apart, to let Apple or Google deliver Delta’s texts, to roll daily limits at your local midnight, and to know which version to support. On Android, the app also asks Google Play Integrity to confirm that a request comes from our app on a genuine phone; our server receives Google’s verdict, not anything about you. |
| Phones that used a version before 2.0 without an account: their plan and log | Kept for that phone, as a backup and for the morning message those versions had, until the phone signs in or you ask us to delete them. |
| Whether the subscription is active | Apple or Google Play, and RevenueCat, tell our server. We never see your card, your Apple Account or Google account details, or your purchase history beyond that. When a trial starts, renews, converts or ends, the server adds that to your usage events, with the plan and its price, so we can see which people stay. |
| Usage events: which screens you open and what you tap, how long a meal reading or a coach answer took, error codes, crash reports, the app version, phone model, iOS or Android version, language, time zone, and the city your internet connection is in | To see which parts of the app work, where people get stuck and what breaks. They never contain your meals, weights, measurements, photographs or anything you typed. They are tied to a random id the app makes, and to your account if you sign in. PostHog receives them in the EU, looks up the city your IP address is in, and does not keep the address itself. You can turn them off in More › Privacy. |
| How each answer, text, review and meal reading was made: the model, the number of tokens, the time it took and what it cost, and which kind of text it was | To keep Delta fast and its cost under control. Never the question, the answer, the text or the numbers sent with it. |
| Only if you say yes: daily grades of your progress, and your food searches | How each row of your brief was graded, from harmless to critical (eating, protein, carbs and fat, creatine and tracking), whether you weighed in, and once a week your trend against your planned pace. Never a number: no weights, calories or grams. It shows us which advice actually helps people gain. Also what you type into the search in Log food and which result you pick, so search shows the right food sooner. The app asks once, on its own screen, and you can change your answer in More › Privacy. |
| Only if you say yes to a coach: your food log, weigh-ins, targets and goal | If a coach who uses MassDelta sends you their link, or you use their code, the app asks whether to share your log with them. If you say yes, that coach can read what you log, from your first day in the app: each food with its amount, calories and macronutrients, your weigh-ins and trend, your targets and goal. Never your chats with Delta, its notes, your photographs or your email address. The coach sees it while you have MassDelta Pro. You stop it in More › Coach, and the coach loses access at once. |
| Your email, only if you write to us | To reply. |
Your weight, height, age, sex, activity and goal — what you answered when you set the app up — are used to set your first target, and are part of what your account keeps. The model is sent what it needs of them for an answer, a text or a review, and no more. The setup answers that are not about your body (how long you have been lifting and how often you train, whether you have counted calories before, why you train and the method you chose, what you see going wrong, how often you can weigh in, whether you set your own calorie target, whether you take creatine, and whether you turned notifications on) are also part of usage events, so we can see how the app works for different people.
The device id is personal data. Nothing here names you, but what the server holds is tied to your account and the ids of its phones, and that lets us tell your records apart from everyone else’s — which is what GDPR means by personal data. That is why the App Store’s privacy label lists what MassDelta collects as linked to you, and Google Play’s data safety section lists it as collected: linked to your account and its email, never to a name we ask for.
4. What we do not do
- No fingerprinting anywhere. In the app, on either phone, no advertising identifier, no advertising and no tracking across apps or sites. The one exception is the massdelta.app website outside the EU, the EEA, the UK and Switzerland, where Google’s advertising tag measures our Google ads (section 12).
- No selling or renting of personal information, ever.
- One analytics and crash-reporting SDK inside the app, PostHog. It sends no health values unless you say yes to sharing your progress, and your IP address is discarded once the city it is in has been looked up. Nothing it receives is used for advertising or combined with data from other apps or websites.
- No precise location. The app never asks for your phone’s location. It knows your time zone, and our analytics sees the city your internet connection is in.
- No contacts, no health-data integration, no reading of anything on the phone the app did not create.
5. Who touches it
We do not sell your personal information and never have. The only parties that handle it are the providers we need to run, named here rather than described as partners:
- Apple — on iPhone, distribution through the App Store, billing, speech-to-text when you dictate a meal, and delivering Delta’s texts as notifications; on either phone, Sign in with Apple if you choose it.
- Google — on Android, distribution and billing through Google Play, delivering Delta’s texts as notifications (Firebase Cloud Messaging), speech-to-text when you dictate a meal, and Play Integrity, which confirms that requests come from our app on a genuine phone; on either phone, Sign in with Google if you choose it; and Google Ads, which on massdelta.app, outside the EU, the EEA, the UK and Switzerland, learns when a visitor taps through to the App Store, so we can see which of our ads lead to the app (section 12).
- OpenAI — reads meals and labels from what you type or photograph, turns what you say in voice mode into text, answers as Delta, the coach, including its web search, and writes Delta’s texts, weekly target reviews and the line it remembers of each chat.
- Open Food Facts — looks up, from the phone, a barcode our own food database doesn’t have; it receives the barcode and your IP address.
- Amazon Web Services — runs our server, in the US (us-east-2).
- Neon — our database and photo storage, in the US (us-east-2).
- RevenueCat — tells our server whether a subscription is active.
- PostHog — receives usage events and crash reports, and daily progress grades and food searches if you say yes, in the EU (Frankfurt).
- Vercel — hosts our websites, counts page views without cookies, and tells massdelta.app which country a visit comes from, so the Google Ads tag stays off in the EU, the EEA, the UK and Switzerland.
The model provider reads meals, answers as Delta, and writes Delta’s texts, weekly reviews and the line it remembers of each chat. Our requests to it are made with storage turned off, so it does not retain them to train on, and the files a weekly review computes on are deleted as soon as it is done. Delta can also search the web when a question calls for it, using a short list of medical and nutrition references rather than the open internet, and it tells you where an answer came from.
Your coach, only if you say yes. A coach you chose to share with reads your log on a page we run, signed in with their own MassDelta account. They are not one of our providers and they decide for themselves what to do with what they read; section 3 says what that is, and More › Coach stops it.
We would also disclose information if the law required it, or to protect our rights or someone’s safety. If Norply Inc. is acquired, this data may transfer to the acquirer, who would remain bound by this policy.
6. How long we keep it
These are the clocks our server actually enforces. They are the same figures the app declares to Apple and to Google Play.
| What | Kept for |
|---|---|
| Meal photographs | 24 hours, then deleted. There is no option to keep them longer. |
| Meal descriptions | 90 days. |
| Analysis records — what was read and any correction you made | 24 months, tied to the device id. |
| What is sent to the model with a question, a text or a review | Not stored by the model provider. The files a weekly review computes on are deleted when it is done. |
| Coach conversations on the server | 24 hours. The transcript you see is kept on your phone and in your account. |
| Your account: its email, sign-in ids, and what it keeps (plan, meals, weigh-ins, settings, chats, the line Delta remembers of each chat, the weekly target reviews) | Until you delete the account. Something you delete in the app is removed from the account; its contents are kept for up to 30 days in case a sync goes wrong, and the note that it was deleted for 90 days, so your other phones hear about it. |
| Coach evaluation rows — the question, the answer, which tools were used | 90 days, to check the coach is answering well. |
| A phone’s plan and log from before 2.0, without an account | Until the phone signs in or you ask us to delete them, as described in section 10. |
| Delta’s texts, the ones it decided against, and reminders you set | 90 days. |
| Device record and subscription status | While the install exists, and until you ask us to delete it. |
| Your answer to the progress question | As long as the device record, so we can show what you agreed to and when. |
| Your yes to a coach, and when you stopped | As long as the account, so we can show what you agreed to and when. It is part of the file from More › Account › Download my data. |
| Usage events, crash reports, progress grades and food searches, at PostHog | Up to 12 months, which is PostHog’s limit. We delete a person’s events sooner when asked. |
| Database backups | Our database keeps short point-in-time backups, so something deleted can remain in a backup for up to 7 days before it is gone for good. |
| Email you send us | As long as needed to help, then archived under our ordinary business retention. |
| Your email on the Android waitlist (massdelta.app) | Until you ask us to remove it. |
7. Where it is stored
Our server and database run in the United States (AWS and Neon, us-east-2). As a US company we access our own data from the US. Where personal data of EU or UK residents is transferred to the US, we rely on the European Commission’s Standard Contractual Clauses as included in our providers’ data processing agreements. Usage events, crash reports, progress grades and food searches are stored by PostHog in the EU (Frankfurt).
8. Legal basis (EU and UK)
- Performance of a contract (Article 6(1)(b) GDPR) for everything needed to provide the app you subscribed to: reading meals, answering as Delta, its texts and reviews, checking the subscription.
- Explicit consent (Articles 6(1)(a) and 9(2)(a)) for keeping your plan, meals, weigh-ins and chats in your account, having Delta read them, and reading some chats ourselves to improve Delta, which can say something about your health. You give it by signing in and continuing past the screen that says what the account keeps; you withdraw it by deleting the account, after which the app can no longer be used with it.
- Explicit consent (Articles 6(1)(a) and 9(2)(a)) for daily grades of your progress and your food searches. You give it by tapping “Share my progress” on the screen that asks, and withdraw it in More › Privacy. Saying no changes nothing in the app.
- Explicit consent (Articles 6(1)(a) and 9(2)(a)) for sharing your log with a coach. You give it by tapping “Share my log” on the screen that names the coach, and withdraw it in More › Coach. Saying no changes nothing in the app.
- Consent (Article 6(1)(a)) for the Android waitlist on massdelta.app. You give it by entering your email and joining; you withdraw it by emailing us, and we remove the address.
- Legitimate interests (Article 6(1)(f)) for keeping the service secure and within its limits, for checking the coach’s answers, and for usage events and crash reports, which show us how the app is used and what breaks. Usage events carry no health values, and you can turn them off in More › Privacy.
9. Security
Everything travels over HTTPS. The app proves it is the same install with a key it makes on the phone (on Android, with Google Play Integrity as well), and signing in goes through Apple or Google; there is no password of ours to leak. An account holds an email address, never a name we ask for. No system is perfectly secure, and if we learned of a breach affecting you we would tell you.
10. Your rights, and how to delete
Wherever you live, you can ask us to tell you what we hold about your device, send you a copy, correct it, delete it, or restrict how we use it. We act on every request without charge and without asking why.
- To get a copy: More › Account › Download my data gives you everything the account holds, as one file.
- To delete: More › Account › Delete account. It removes the account and everything it holds — including Delta’s texts, what it remembers and the weekly reviews — the meal analyses and coach records of every phone signed in to it, and your sign-in link with Apple; the phone is cleared too. It cannot be undone.
- A phone that used a version before 2.0 without an account: delete the app, then email founders@norply.co, ideally from the app (More › Legal & support), so the message carries the device id. We remove that device’s records on our server and its usage events at PostHog, and confirm. Without the id, tell us roughly when you used the app and we will find it.
To have your usage events, progress grades and food searches at PostHog deleted without deleting anything else, email us the same way; we delete them with the id they belong to.
Cancelling the subscription is separate and is done with the store that bills you: on iPhone, iOS Settings → Apple Account → Subscriptions; on Android, Google Play → your profile picture → Payments & subscriptions → Subscriptions. Deleting the app, or the account, does not cancel it.
EU and UK: you also have the right to data portability and to complain to your supervisory authority; we would rather you gave us the chance to fix it first. California: the CCPA and CPRA give you the right to know, delete, correct, and opt out of sale or sharing. We do not sell or share personal information as those laws define it, so there is nothing to opt out of, and we will never treat you differently for exercising a right.
11. Children
The app and the sites are not directed at children, and we do not knowingly collect personal information from anyone under 16. If you believe a child has used the app, write to founders@norply.co and we will delete what we hold.
12. The websites
norply.co sets no cookies, and neither does massdelta.app in the EU, the EEA, the UK or Switzerland. Both sites use Vercel Analytics, which counts page views without cookies and without a profile of you across sites, recording the page, the referrer, the country and the browser type. There is no session recording, and the only form is the Android waitlist below.
The Android waitlist on massdelta.app. While MassDelta is not yet on Google Play, the Google Play button on massdelta.app opens a form that takes your email. We keep the address on our server (section 7), with the language of the page and which button you used, to email you when MassDelta is on Google Play. To be taken off the list, email founders@norply.co.
Google Ads on massdelta.app. We advertise MassDelta on Google. Outside the EU, the EEA, the UK and Switzerland, massdelta.app loads Google’s advertising tag. It sets Google’s cookies and tells Google that the page was visited and when a visitor taps through to the App Store, so we can see which of our Google ads lead people to the app. Ad personalisation is switched off: we tell Google not to use it to show you ads elsewhere. Google receives that, with what its tag reads from your browser, under Google’s privacy policy; How Google uses information from sites that use its services explains what it does with it.
The tag never loads in the EU, the EEA, the UK or Switzerland, and never when your browser sends Global Privacy Control. To decide, the site asks our host, Vercel, which country your IP address is in; the answer is used for that decision only and is not stored. That is why there is no cookie banner: where consent would be needed, the tag does not load. Separately, when you arrive from one of our Google ads, the App Store links on that page carry a campaign name, so App Store Connect can count installs from Google ads; it is read from the page address, and nothing is stored or sent.
13. Changes to this policy
If we change this policy we update the “Last updated” date at the top. If a change materially affects how we use data we already hold, we say so in the app before it takes effect.
14. Contact
founders@norply.co, or Norply Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, USA. See also the Terms of Service.