Privacy Policy — KAJI Meals

What the KAJI Meals app collects, why, how long we keep it, and what you can ask us to do about it.

Visiting kaji.studio itself? Read the website privacy policy →

Who we are

KAJI Studio makes the KAJI Meals app. For everything described here we are the data controller, meaning we decide what is collected and why. Our full identification and contact address are at the bottom of this page.

This policy covers the app. Reading it on kaji.studio is a visit to our website, which collects its own small handful of things and has its own policy, linked above.

If you want to exercise any of the rights described below, or you simply want to know what we hold about you, use the privacy contact address at the bottom of this page. It goes to a separate inbox from general support so that a request cannot get lost behind a pile of feature suggestions. We answer within one month, which is the deadline the GDPR sets us.

The short version

We would rather not hold your data. The app works offline on your device, and your content reaches our servers only if you choose a cloud workspace. We sell a subscription, not your information.

  • We do not sell or rent personal data, and we never have.
  • Paid plans carry no advertising. On the Free plan there is one kind of ad, in one place, and only when you choose to watch it — the advertising section below says exactly what that involves.
  • The app contains no analytics. We do not know which screens you open or how long you spend in them. It does send us a report when it crashes, without your name, your email address or your content — the section on crash reports says what is in one.
  • Everything we store on our own servers is hosted in the European Union.
  • There is also a web version at meals.kaji.studio for cloud workspaces on a paid plan. It works only online and sets no cookies; the section on the web version says what it keeps in your browser.

Your account and your workspace

KAJI Meals needs an account, but it does not need your content. When you set up your workspace you choose between keeping it on this device and syncing it to the cloud. Choose local, and your meals, plans and photos stay on your phone — they are never uploaded, and the only thing we hold is the account itself. Choose cloud, and we store the following so your content survives a lost phone and reaches your other devices.

Choosing a local workspace is not the same as us holding nothing, and we would rather say so plainly than let the word local imply more than it should. Your account itself always lives on our servers, because that is what lets you sign in on a new phone. So does a record of the workspace you own — its name and the fact that you own it — even when nothing inside it ever leaves your device.

WhatLocal workspaceCloud workspace
Account: email address, name, password hash, sign-in timestampsOn our serversOn our servers
Profile: avatar colour, eating type, nutrition display preferences, languageOn our serversOn our servers
Licence tier (free or paid)On our serversOn our servers
Workspace record: its name, that you own it, who its members areOn our serversOn our servers
Meals, recipes, ingredients, plans, shopping lists, categoriesYour device only — never uploadedOn our servers
Nutrition targetsYour device only — never uploadedOn our servers
Meal photosYour device only — never uploadedOn our servers

A paid subscription does not change what we store. It unlocks cloud sync and sharing, so in practice a paid user is more likely to have chosen a cloud workspace — but the columns above are decided by that choice, not by what you pay.

With a cloud workspace, this is what we hold and why.

WhatWhyBasis
Email address, name and passwordTo create the account, sign you in and let you reset your password. Passwords are stored as a hash by our authentication provider; we never see the password itself.Performing our contract with you
Your meals, recipes, ingredients, plans, shopping lists and categoriesThis is the content of the app. It is stored so it survives a lost phone and reaches your other devices.Performing our contract with you
Nutrition targets and per-person settingsSo the app can show you progress against the goals you set.Performing our contract with you
Workspace membership and roleSo the right people can see a shared workspace, and so we know who may change what.Performing our contract with you
Language preferenceSo the app opens in the language you chose, on every device.Performing our contract with you

If you share a workspace, the people in it can see the content of that workspace. That is the point of sharing, but it is worth being explicit: a shared meal plan is visible to everyone in the workspace, along with the name on your account.

The web version

KAJI Meals also runs in the browser at meals.kaji.studio, for members of a cloud workspace on a paid plan. It shows the same workspace as the app and reads it straight from our servers, so everything under Your account and your workspace applies to it too. It has no local workspace, shows no advertising and sells no subscriptions; plans are bought in the app.

The page and its files are delivered by Cloudflare. Like any web host, Cloudflare receives the requests your browser makes for them, including your IP address and the description your browser gives of itself, and answers them from its worldwide network, so the data centre that answers may be outside the European Union. Your workspace content is exchanged with our database, as in the app.

The web version uses no analytics and sets no cookies. To work, it keeps a few things in your browser's local storage: your sign-in, so you stay signed in between visits; a copy of your account details (name, email address, plan and workspace), so it opens quickly; your display settings, such as the language, the planner view and the order of your shopping list categories; and a few technical markers, such as the current state of your plan. Signing out removes the sign-in and the account copy. The display settings and markers stay in the browser until you clear its site data for meals.kaji.studio. All of this is strictly necessary for the service you asked for, so it needs no consent under Article 5(3) of the ePrivacy Directive.

One exception sits outside our code: if Cloudflare's security checks ever stop a request that looks like an attack and ask your browser to prove it is not automated, Cloudflare sets its own cf_clearance cookie to remember that it passed. We do not read it.

Meal photos

If you add a photo to a meal, it is uploaded to our storage in the European Union and stored under a path built from two random identifiers — one for your workspace, one for the meal. The link is long and unguessable, and it is not listed anywhere: someone would need the exact address to reach the image.

We should be precise about what that does and does not mean. The file is served without requiring a login, so anyone you deliberately give the link to can open it, and that is what will make sharing a meal possible later. It is not encrypted in a way that hides it from us, and we can access it to run the service. It is not indexed by search engines.

Deleting a meal, or deleting your account, removes the photos that belong to it. The database record goes immediately; the image file itself is reclaimed by a job that runs every night, because storage cannot be cleared in the same operation as the database. So a deleted photo can persist for up to a day before the file is gone. The same job removes any photo whose meal no longer exists, so an interrupted delete does not leave a file stranded.

When you contact support

There are two support forms in the app, and they collect different things because one of them is reachable without signing in. We use what they send to answer you, and for nothing else. The basis is performing our contract with you and our legitimate interest in providing support — not consent, because you asked us for help and we should not need permission to reply.

Report a problem (signed in)
The subject and message you type, the category you pick, and diagnostics: your app version, your platform and version, your device name, your user id, your workspace id, your licence status and your account email address. Your account email is used as the reply address; we ignore any address the app might otherwise send, so a reply can only ever go to the account itself. A diagnostics log covering the last twenty-four hours on your device is attached as well; what it contains is described below.
Trouble signing in (signed out)
The email address, subject and message you type, plus your app version, your platform and version, and your device name. Because you are not signed in, we cannot confirm the address belongs to you, and we treat what you tell us as an unverified claim. We will ask you to prove ownership before changing anything on an account.

The signed-in form also attaches a diagnostics log. The app keeps a running record on your device of what it did — sync attempts and their results, sign-in and routing transitions, subscription entitlement changes, the database version the device is on, how many items a shopping list generated, and errors it ran into. It holds the last twenty-four hours and is capped in size, so older entries are discarded as new ones arrive. It never leaves your device unless you send a problem report, and it is attached to that report so we can see what led up to what you are describing. Your description tells us what you saw; the log tells us what the app was doing at the time, and without it most sync and subscription reports cannot be answered.

The log records what the app did, not what you wrote. Meal names, ingredient names, shopping list contents, the text of your messages and anything else you typed are removed before an entry is written — not filtered out as it is sent, but never recorded in the first place. What it does contain is identifiers (your user id, your workspace id, the ids of the rows involved), table names, counts and status codes. It is deleted from your device after twenty-four hours, does not survive uninstalling the app, and once attached to a report it is covered by the support retention below. We store it nowhere else.

The signed-out form additionally stores two things whose only purpose is to stop the form being abused as a way of sending mail through us: an identifier the app generates once and keeps in your device's secure storage, used to allow one message per device per day; and a SHA-256 hash of your IP address, used to allow three per day from the same address. We do not store the IP address itself. Because the hash is unsalted we treat it as pseudonymous rather than anonymous — it identifies less than an IP address, but not nothing. Our basis for both is our legitimate interest in keeping the service usable. The limits only look back one day, but we keep both for seven days so that a burst of abuse can still be looked into. After that both are deleted, while the message itself follows the twelve-month rule below.

Support messages are deleted twelve months after they are sent, automatically and in both places we keep them. The record in our database is deleted outright. The copy in our support inbox, with our replies and any log attached to it, is moved to the mailbox's trash by a nightly job about a month before the twelve months are up, and the mailbox empties its trash for good within thirty days.

Crash reports

When the app crashes or runs into an error it did not expect, it sends a report to Sentry, the service we use to find and fix such faults. This happens automatically in the versions distributed through the stores, and there is no setting in the app to turn it off. Our basis is our legitimate interest in keeping the app working (Article 6(1)(f) GDPR); you can object to it through the privacy contact address at the bottom of this page.

A report contains the type of error and its message, a technical trace of where in the code it happened, and the app version. It contains details of your device: manufacturer, model, operating system version, screen size, memory and storage size, battery level, time zone, language, connection type, and which permissions the app has been granted. It contains a trail of the app’s recent network requests, reduced to the server, the path and the status code. It carries a random identifier for the installation, which is not your account id and is not linked to your email address. And Sentry works out an approximate location — country and city — from the IP address the report arrives from; the IP address itself is not stored.

A report does not contain your account id, your name or your email address, and no user is attached to it. It does not contain your meals, ingredients, plans or shopping lists, anything you typed, a screenshot, or the app’s log output. Error messages raised by the app’s own code are redacted before they leave your device. A crash in the underlying system code is reported by Sentry’s own component without passing through that redaction; it carries a technical trace, not your content.

In the web version the report comes from your browser. Instead of the device details above, it contains the browser and the operating system with their versions, the screen size and the language, and the address of the screen in the app where the error happened (such as /shopping). Its trail covers recent network requests, reduced as above, and the screens you moved between. It does not record your clicks or what you type, and it carries no identifier that lasts beyond the visit.

Reports are stored in the European Union, in Germany, and Sentry deletes them after 30 days.

Subscriptions and payment

KAJI Meals sells subscriptions through the App Store and Google Play. We never see your card details, your billing address or your payment method — the store handles the payment and tells us only whether an entitlement is active.

We use RevenueCat to manage those entitlements. It receives an anonymous identifier for your install, the subscription events the store sends, and your platform. It tells us whether you are on the free or paid tier, which is what unlocks the paid features. Apple and Google process this outside the EU under their own privacy policies and the European Commission's standard contractual clauses.

Advertising on the Free plan

The Free plan is paid for in part by advertising, in one place only: importing meals or ingredients from our catalog. Before such an import you can choose to watch one short video ad, served by Google AdMob. Ads never appear on their own, and nowhere else in the app. On a paid plan the app requests no ads at all.

To show an ad, Google’s software in the app sends Google your IP address, your device’s advertising ID, your device model and operating system, and which ads were shown, watched or tapped. On an iPhone, Google receives the advertising ID only if you allow tracking in Apple’s prompt; you can change this at any time under Settings → Privacy & Security → Tracking. We do not give Google your name, your email address or anything you have put into the app. Google is not acting on our instructions here: it decides for itself how it uses what it collects, under its own privacy policy at policies.google.com/privacy. For people in the European Economic Area, the United Kingdom and Switzerland the provider is Google Ireland Limited; Google may also process this data in the United States, relying on the EU–US Data Privacy Framework and standard contractual clauses.

If you are in the European Economic Area, the United Kingdom or Switzerland, Google’s consent form appears before the first ad and asks whether ads may be personalised and whether Google may store and read information on your device. Our basis is your consent. If you decline, Google may show ads that are not personalised, or none; when no ad can be shown, the import goes ahead anyway. You can change or withdraw your choice at any time under Settings → About → Ad privacy settings, and you can reset or delete your advertising ID in your phone’s own settings.

Separately, we keep our own record of each catalog import, on every plan: your user id, whether it was meals or ingredients, how many, whether an ad was shown, and when. We use it to work out when the next ad is due and to see how much the catalog is used. It does not record which meals or ingredients you imported, and it is not shared with Google. Our basis is our legitimate interest in running and funding the Free plan.

Who else processes your data

We use a small number of providers to run the service. They act on our instructions under a data processing agreement, and none of them may use your data for their own purposes.

ProviderWhat forWhere
SupabaseDatabase, authentication and photo storage — the account and workspace content described aboveIreland (EU)
ResendDelivering support mail and account emailsEU
Cloudflare, Inc.Delivering the web version at meals.kaji.studio: the requests your browser makes for the page and its filesWorldwide network, under standard contractual clauses
Sentry (Functional Software, Inc.)Crash and error reportsGermany (EU)
Expo (650 Industries, Inc.)App updates — when the app starts it asks whether a newer version is available, sending a random install id, your platform and the app version it is runningUnited States, under standard contractual clauses
RevenueCatSubscription entitlementsUnited States, under standard contractual clauses
Apple, GoogleApp distribution and payment processingUnited States, under standard contractual clauses

Google AdMob is not in this table because it is not a processor: for advertising, Google acts on its own account, as described under Advertising on the Free plan above.

Cloudflare also hosts our website, kaji.studio. The website policy linked at the top of this page covers visits there.

How long we keep things

Your account and its content
Until you delete your account. Deletion is available in the app's settings and removes your account, your content and your photos, with photo files reclaimed by the nightly job described above.
Support messages
Twelve months from the day you send them. Both copies go automatically: the database record is deleted, and the mail in our support inbox is moved to the trash about a month earlier and removed from there for good within thirty days.
Device identifier and IP hash
Stored only by the signed-out support form. Seven days from the day you send the message, then deleted automatically; the message itself is kept for the twelve months above.
Diagnostics log
Twenty-four hours on your device, on a rolling basis, and gone when you uninstall the app. A copy attached to a problem report follows the twelve-month rule for support messages above; we keep it nowhere else.
Crash reports
30 days, then deleted by Sentry automatically.
Catalog import records
Until you delete your account, which removes them along with it.
Deleted content
When you delete a meal or a plan it disappears immediately, but a marker is kept for thirty days so that a device which was offline learns about the deletion instead of resurrecting it. After thirty days the row is removed for good.
Workspace invitations
An invitation code works for fifteen minutes and then stops. The record that it was created is kept for a further seven days, so a failed invite can still be looked into, and is then deleted.

Your rights

Under the GDPR you can ask us for a copy of what we hold about you, ask us to correct it, ask us to delete it, ask us to restrict or stop a particular use, and ask for your data in a portable form. You can also object to any processing we base on legitimate interest, and we will stop unless we have a compelling reason not to.

You do not need our help to delete your account — it is in the app's settings, and it removes your content and photos along with it. For anything else, write to the privacy contact address at the bottom of this page.

If you think we have handled your data badly, we would rather hear it from you first, but you have every right to complain to a supervisory authority instead. In Portugal that is the Comissão Nacional de Proteção de Dados (CNPD); if you live elsewhere in the EU, you may complain to your own country's authority.

Children

KAJI Meals is not aimed at children and we do not knowingly create accounts for anyone under 16. If you believe a child has an account with us, tell us and we will delete it.

Changes to this policy

When we change what we collect, we change this page in the same release, and the date at the top moves. If a change materially affects you — a new processor, a new purpose, a longer retention period — we will tell you in the app rather than relying on you to re-read this page.