DaffoDiary

Privacy policy

Your garden stays on your phone unless you turn on backup, which keeps a copy — photographs included — against your account so a new phone can get it back. Photographs and a rough location are also sent out to answer a question you asked, and a copy of that is kept for three days — deleted automatically, normally within a day or two after that — so we can fix it when the answer is wrong.

Version 2026-10-10.1

The short version

DaffoDiary has no advertising. You need an account — made with an email address or with Sign in with Apple — to identify a plant, write its year of care or ask a question; the manual already on your phone reads and prints without one. Your manual — the plants, the photographs, the twelve months of tasks — lives in a database on your phone. Ten things leave it, each for a specific job: the email address your account is made with, so it can be yours; a rough location, so the calendar can be timed to your garden rather than a zone chart; photographs, so a plant can be identified; the plant’s name and climate — and, when you ask for its year to be written again on the full manual, what you recorded doing to it — so a year of care can be written for it; a question you send about one plant, with any photograph you attach to it, so it can be answered; the manual itself, when you export a PDF and we make it for you; the patch of ground your garden plan covers, if you line it up with an aerial photograph; if you subscribe, your account and the receipt Apple issues, so the subscription follows you to a new phone; what each of those calls cost us, so we can see what running the app comes to; and counts of what happened on the phone — an error, a crash, a step of setting up — so we can find what is failing without waiting for somebody to tell us.

We keep two things. A record of what each call cost, for ninety days, tied to your account as a one-way scramble rather than by name. And a copy of each call — the photographs included — for three days, so that when an identification comes back wrong we can see what the computer was actually looking at. That copy is readable only by us, and it is deleted automatically once the three days are up — normally within a day or two after that — whether we looked at it or not.

There is no third-party analytics or crash-reporting software in the app — the counts above go only to our own server — nothing is sold, and nothing is used to advertise to you.

Where your garden is

With your permission the app takes a single location reading while it is open. It never reads your location in the background, and it does not track you.

Coordinates are rounded to about eleven metres and sent to Open-Meteo, a weather service, to fetch ten years of frost history, the current soil temperature and the coming week’s overnight lows. They are sent with no name, no account and nothing else attached. If you would rather not share a location at all, type a place name instead — that is looked up the same way and works just as well.

The country your garden is in is kept because it decides which weedkillers and treatments may legally be suggested to you. It comes from the location, not from your phone’s language settings, because a US phone in a British garden must produce British guidance.

Photographs

Photographs you take or choose are stored on your phone. When you ask for a plant to be identified, the photographs for that plant, anything you typed about it, and the country are sent to our server, which passes them to Anthropic’s Claude to get an answer back.

They are used to answer that one question, and they are not used to train anything.

A copy is kept for three days. Identification from a photograph is the part of this app most likely to be wrong, and without the picture the computer saw there is no way to work out why — so the request and the answer are stored for three days and then deleted automatically. Our storage provider clears expired files on its own schedule rather than at the stroke of the third day, so the deletion normally lands within a day or two after that. Only we can read them, they are never sold or shared, and nothing is done with them except finding out what went wrong.

Photographs also leave your phone when you export a PDF and we make it for you, which the next section explains.

Deleting a plant deletes its photographs from your phone with it.

Pictures of the plants it is choosing between

When the app is not sure what a plant is, it offers you the few it is choosing between and shows a reference photograph of each one so you can compare them with what is actually in front of you.

Those pictures come from Wikipedia. To fetch them the app sends Wikipedia the botanical names it is weighing up — "Hydrangea paniculata" — and nothing else. None of your photographs, your location, or any identifier goes with them. It is a question about a species, not about your garden, and it is asked only while that screen is open.

The pictures are shown with their photographer and licence beside them, and they are not saved. They never become part of your manual, and they are not in anything you export.

Aerial photographs and building outlines

If you draw a plan of your garden, you can line it up with a photograph from above and draw over it, and in some places add the outline of your house from public building maps. This is only offered where a government publishes them openly: the United States, New Zealand and New South Wales.

To fetch them, the app sends our server the patch of ground you are lining up — a box of map coordinates around your garden — and the country. Our server asks the public source for that place. For the photograph that is the US Geological Survey, NSW Spatial Services or Land Information New Zealand. For the outlines it is MassGIS, the Massachusetts mapping office (whose data Esri also hosts), for a garden in or near Massachusetts; FEMA’s building data (which Esri hosts) elsewhere in the US, or when MassGIS has nothing for that patch; or Land Information New Zealand. They see our server’s address, not yours, and they are sent nothing else: no name, no account and no identifier.

The photograph is shown while you draw and then forgotten. It is not saved on your phone or on our server, and it never appears in your manual or anything you export. What is kept is your drawing and the patch of ground it covers, which are part of your manual like the rest of it — so they are in your exports, and in your backup if you have turned that on.

Making a PDF of your manual

When you export a PDF and your phone has signal, the app sends your whole manual to a second small server of ours: the property’s name, every plant and its tasks, and the photographs as they appear on the page. That server draws the document and passes it to Cloudflare’s browser service, which turns it into a PDF and sends it back.

It is used to make that one document. Nothing is kept afterwards — not the manual, not the photographs, not the PDF.

When there is no signal, or that service is busy, your phone makes the PDF itself and nothing leaves it. You are not told which happened, because the document is the same either way.

Each printed month and plant carries a small code that opens that page in the app. The code holds a month number or a short string that means nothing without your phone — never the garden’s location or a plant’s name — so a page left with somebody else tells them nothing the page itself does not. Your phone remembers when you printed each page, so it can tell you which have changed; that stays on the phone.

Sharing a read-only link

If you make a read-only link for somebody looking after the garden, or for the next owner, the app sends a copy of your manual to our server: the garden’s name and approximate location as the printed manual shows them, every plant and its year of tasks, and the photographs only if you switch them on. Anybody with the link can read that copy without an account, and nothing else.

The copy is kept until you turn the link off, or for 30 days for a house-sitter’s link, which then stops on its own. A link for the next owner lasts until you turn it off. Deleting your account deletes every link you made. The pages are not shown to search engines and load nothing from anybody else.

Writing a year of care

To write twelve months of tasks, the app sends the plant’s common and botanical name, the frost dates and winter minimum derived for your garden, the country, and — for a lawn — the grass type. That particular call does not send your photographs, your coordinates or your property’s name.

On the full manual, when you ask for a plant’s year to be written again, the app also sends what you marked done for that plant in the last twelve months — the dates, the tasks and your notes, but not the photographs — so the new year can take account of what has worked in your garden. A year written this way is never cached or shared with any other garden. A year written for the first time, or in the background, does not send it.

Generated years are cached on the server so that two gardens with a similar climate and the same plant do not each cost a fresh answer. The cache is keyed on climate and country. It holds no photographs and nothing that identifies you or your address.

A copy of this call is kept for three days as well, on the same terms as the photographs above, so that a year of tasks that comes back wrong can be looked at rather than guessed about.

Asking a question about a plant

Each plant has a box where you can ask something about it — why the leaves are browning, when to prune it, whether now is the right time to feed it. When you send a question, the app sends what you typed, the plant’s name, the month, the frost dates and winter minimum derived for your garden, the country, today’s soil temperature if it has one, and the tasks your manual already lists for this month — so the answer does not contradict the page you are reading it beside.

If you attach a photograph to the question, that photograph goes with it. Nothing else on the plant is sent: not your other photographs, not your coordinates, not your property’s name.

When you choose “Ask what next” on something you marked done, the box opens with a question already written from that record — the task, the date and your note — and the photograph you took with it attached. You can change or remove either, and nothing is sent until you press Ask.

A copy of this call is kept for three days as well, on the same terms as the photographs above, so that an answer that comes back wrong can be looked at rather than guessed about.

The answer is kept on your phone, next to the plant, with the date you asked on it. It is not part of your manual: it is not exported, it is not in the PDF, and it is not backed up to your account. Only the last few answers for each plant are kept, and removing the plant removes them.

It is horticultural guidance from a computer and it is sometimes wrong, in the same way an identification is. It is not a diagnosis, and nothing in it replaces reading the label on anything you buy.

Marking a task done

When you mark a task done, the date, any note you write and — on the full manual — any photograph you take with it become part of your manual. They are kept on your phone, printed in the plant’s history, included when you export the manual or a PDF, and copied to your account if you turn on backup, on the same terms as the rest of your garden. Nothing is sent anywhere when you mark something done; it leaves the phone only in the ways described above.

Our server, and keeping costs sane

The app talks to Anthropic through a small server of ours rather than directly, because the key that authorises those calls cannot safely live inside an app anyone can download.

That server sees your network address, as every web server does, and counts requests against it to stop one caller running up the bill. The address is used for that count and is never written to our logs.

The app also sends an installation identifier: sixteen random numbers it made up the first time it needed one. It is not your name, your device’s serial number, or anything derived from you or your phone, and deleting the app destroys it — reinstalling makes a new one. We store it only as a one-way scramble, on the records of calls described below, so that when something goes wrong we can tell your phones apart. It is no longer what we count usage against — your account is.

What we record against your account for ninety days is what each call cost and which of the calls it was — not your photographs, not your address. Alongside that, for three days only, sits the copy of the call itself described above: what was sent, including the photographs, and what came back. Both are deleted automatically when their time is up.

The app also sends our server counts of what happened on the phone: how many gardens were set up, walks started and finished, identifications kept or corrected, and errors — counted by which part of the app they happened in and what general kind of error they were, never by what the error said. A launch that follows the app closing unexpectedly is counted the same way. These counts carry no account, no installation identifier, no photograph, no place and no words from your garden, so they cannot be traced to you or told apart from anybody else’s. We keep them for ninety days.

You can ask us to delete your copies sooner, or to tell you what is held, using the contact address at the end of this policy.

Your account

You need an account to identify a plant, have its year of care written, or ask a question about it. Each of those is a call that costs us money, and an account is how we stop one caller running up the bill for everybody. The manual already on your phone — reading it, printing it, exporting it — needs no account.

We hold your email address and, if you chose one, a password, kept by Supabase, who provide the sign-in service.

If you sign in with Apple, Apple tells us an email address — your own, or a private relay address Apple makes if you choose to hide yours — and nothing else. We also keep a token from Apple against your account, until you delete the account. It is used for one thing: telling Apple to forget the link between you and DaffoDiary when you do.

If you turn on backup, a copy of your gardens goes to that account — the plants, the twelve months, and the photographs. That copy is held until you delete it or delete your account, not for a set number of days, because the point of it is to still be there when you get a new phone. It is stored by Supabase, encrypted in transit and at rest, and is reachable only by an app signed in to your account.

Backup is off until you turn it on, and turning it off stops any further copies being made. Your coordinates travel with the garden, because the calendar is derived from them and a restored manual with no location would have no timing.

If you subscribe, Apple takes the payment and RevenueCat, who check subscriptions for us, receive your account’s identifier and the receipt Apple issues for it. They see what you bought and when it renews — never your garden, your photographs or your location — and that is what lets the full manual follow you to a new phone. We do not see your card or your Apple account.

Our server asks RevenueCat the same thing, using the same identifier, before it answers a question or writes for a lawn or a weed — the parts of the full manual — so the limits hold however the server is reached. On the free manual it also counts your plant identifications for the month, against the same one-way scramble as the cost record, and forgets the count once the month is over.

The calls described above are recorded against your account, which is how we can answer you when you write to say an identification was wrong, and how we limit how many calls one person can make.

You can delete your account from the account screen in the app. That deletes the account and its backup straight away — every garden and photograph copied to it. It takes your account off the record of what your calls cost — the amounts stay in our daily totals, tied to nobody — and, if you signed in with Apple, tells Apple to forget the link first. The records of calls made while you were signed in carry your account and are not removed at that moment: they delete themselves within thirty days, like every other record of a call. A subscription is billed by Apple and is not cancelled by deleting the account — cancel it in your phone’s settings. RevenueCat is told to delete its record of you; Apple keeps its own record of what was bought, as it does for anything bought on the App Store. The gardens on your phone are not touched, and stay until you delete them or the app.

The manual you export

An exported manual is a single HTML file containing your whole manual, which is what lets it be read back into the app later. Treat it as you would any other document: whoever you send it to can read everything in it.

When that file is opened, it fetches its two typefaces from Google Fonts, so opening it makes a request to Google. The app itself does not — it carries its fonts inside it.

What we do not do

Beyond your account, its backup if you turn one on, the record of a subscription, and the records described above, which delete themselves, we hold nothing of yours. We do not use third-party analytics or advertising software, we do not sell or share personal information, and we do not build a profile of you. The installation identifier described above is attached to records of calls and nothing else.

DaffoDiary is not designed for children, and we do not knowingly collect anything from them.

Your choices

Location and camera permissions can be withdrawn at any time in your phone’s settings. The app keeps working without them: type a place name instead of sharing a location, and choose photographs from your library instead of taking them.

Deleting the app deletes the manual on your phone with it, so export it or turn on backup first.

Changes, and getting in touch

If this policy changes in a way that matters, the app will show it to you again rather than quietly updating it.

Questions about any of this can go to support@daffodiary.com.