barm app privacy policy

Nima Project Ltd is the data controller for the barm app. We are a company registered in England and Wales, company number 13152926, with a registered office at 3rd Floor, 86-90 Paul Street, London EC2A 4NE. You can reach us at [email protected].

This policy covers the barm app. The thenimaproject.com website has its own privacy policy, which describes the cookies and the analytics on the website. The app loads none of that, so if you only use barm, the website policy tells you nothing about you. It is still the place we keep the shared parts — your rights, and how to complain — and this page links to it where that is the case.

What you agree to when you use barm is set out separately in the barm app terms.

barm is in closed alpha on Android, so some of what is described here is still moving. When it moves, this page changes with it.

• There are no accounts, and there is no server. No name, no email address, no sign-up. Every batch, note and photograph lives on your phone.
• Your photographs never leave the device. No upload, no cloud backup, and no server that could hold one.
• Reminders are scheduled on your phone by the phone’s own operating system. There is no push service and no device token.
• Two services see technical data about the app: PostHog for which screens get opened, which you can turn off in the app, and Sentry for crash reports. Both are named below.
• There is no advertising, no advertising identifier, and no tracking of you across other apps or websites. Nothing is sold.

The rest of this page is the same thing said precisely, because a summary is not a disclosure.

barm asks you for no name, no email address, no phone number and no password, because there is nothing to sign in to. We hold no account record about you, because no account exists.

Your batches, your timings, your notes, the recipes you tune and save as your own, and everything on your shelf are written to the app’s own storage on your device. There is no server holding your data, so there is no copy for us to read, to lose or to be asked for.

This cuts both ways and it is worth being plain about it: if you delete the app or lose the phone, your batches go with it, because there was never a second copy.

barm does not send your photographs to an AI provider, and it does not send them to us. Whatever your phone itself does with its own photo library or its own backup is between you and your phone; barm keeps its pictures in its own storage and leaves it at that.

The same is true of your notes and of anything you type. It is on the phone. That is the whole story.

When barm tells you a step needs you, that reminder was scheduled locally, by your own phone. The operating system holds the alarm and decides when to show it.

There is no push service involved, no server sending anything to your device, and no device token — the identifier a push service would need in order to reach you. We could not send you a notification if we wanted to.

barm sends product analytics to PostHog, run by PostHog Inc., on their EU region at eu.i.posthog.com. It tells us which parts of the app get used and which get abandoned.

What is sent is product usage only: which screens are opened, and which recipes get started. It does not include your photographs, your notes, what is on your shelf, or anything you have typed.

When barm crashes or hits an error, it sends a crash report to Sentry, a service run by Functional Software Inc. in the United States. We use it to find out that something broke, and where.

A crash report contains:

• a stack trace — the technical trail of which piece of code failed
• device metadata, such as the phone model, the operating system version and the version of barm you are running

Photographs, the names of your batches and file paths are scrubbed before a report is sent. A crash report will not tell us what is in your jar.

Sentry is in the United States, so this is a transfer out of the UK and the EEA. Section 10 says what that means.

barm carries no advertising. It does not read or use an advertising identifier, it does not track you across other apps or websites, and it takes part in no cross-app or cross-site profiling.

We do not sell, rent or share your data with anyone for their own purposes. The only third parties involved are the two processors listed in section 9, each doing one job for us.

These are the only third parties that receive anything from barm. Each one processes on our instructions and for the single purpose named.

That is the whole list. There is no AI provider, no push service, no advertising network and no storage provider, because barm sends them nothing.

Crash reports leave the UK and the EEA. Sentry is run by Functional Software Inc. and barm reports to their United States organisation, which was a deliberate decision across all our apps. If you are in the UK or the EU and barm crashes, the report about that crash is sent to the United States.

What is in it is the stack trace and the device metadata described in section 7. Photographs, batch names and file paths are scrubbed before it is sent, so the transfer does not carry what you are making.

Sentry’s data processing addendum, which we are party to, relies first on the EU–US Data Privacy Framework for transfers from Europe to the United States. If that framework is invalidated or does not apply, the addendum incorporates the European Commission’s Standard Contractual Clauses, Module Two, covering a controller sending data to a processor, which is the arrangement here. For data leaving the United Kingdom those clauses apply as amended by the UK Addendum, and for Switzerland the equivalents under the Swiss FADP.

PostHog processes in the European Union, so analytics is not a transfer out. Nothing else leaves your phone at all, so nothing else can be transferred anywhere.

Payments have not launched, so nothing in the app can charge you anything today and no payment processor is involved yet.

When Pro can be bought, Apple and Google will handle the billing. barm never sees your card and never learns it.

A purchase-entitlement service, RevenueCat, will be added at that point — and this page will name it as a processor before it goes live, not after.

This covers the categories that belong to the app. The general retention rules are in our main privacy policy, so that there is one source of truth rather than two that can drift apart.

Under the UK GDPR and the EU GDPR we need a lawful basis for each thing we do. barm does very little, so the list is short:

• Analytics. You choose. It can be turned off in the app, and while it is on we rely on that choice and on our interest in knowing which screens people actually use.
• Crash reports. Our legitimate interest in keeping the app working and finding out what broke.

Everything else — your batches, your photographs, your notes, your reminders — needs no basis from us at all, because we never receive it.

The analytics switch is in the app’s settings, and turning it off stops the events at source rather than filtering them later.

You have the rights the UK GDPR and the EU GDPR give you — access, correction, erasure, restriction, objection and portability — and how to use them is set out in our main privacy policy. We keep them there rather than repeating them here, so there is one set of words to keep correct.

There is one practical wrinkle worth knowing, and it is a consequence of having no accounts and no server. We cannot identify you, and we hold almost nothing about you to give back or to erase. Your batches, photographs and notes are on your phone: deleting them in the app, or deleting the app, is faster and more complete than asking us, because we have no copy to delete. If you do write to us and we genuinely cannot tell which data is yours, we will say so rather than guess.

If you are unhappy with how we have handled your data you can complain to a supervisory authority — in the United Kingdom the Information Commissioner’s Office, and in the EU the authority in the country you live in. We would rather you told us first, at [email protected], but that is your choice and not a condition.

barm is not designed for children, and we do not knowingly process the data of a child below the age of digital consent where they live.

Under the GDPR that age is set by each country and it is not the same everywhere: 13 in the United Kingdom, 15 in Greece, 16 in Germany. Other countries set it somewhere between 13 and 16. barm ships in eight languages, so this is a real difference rather than a technicality.

If you are younger than the age that applies where you live, use barm only with a parent or guardian, who takes responsibility for how the app is used. barm is also a kitchen app, and a young cook should have an adult with them.

We will update this page when the app changes and when a processor changes its own terms or its position. The current version always lives at this address, with its date at the top.

Where a change materially affects you — a new processor, or a new category of data — we will tell you in the app before it takes effect.

Email: [email protected]. A person will answer.

Nima Project Ltd
Company number 13152926, registered in England and Wales
3rd Floor, 86-90 Paul Street, London EC2A 4NE

What you agree to when you use the app is in the barm app terms. The barm product page is at thenimaproject.com/barm.