I'm Tristan. I built NeeTree on my own, and I'm the only person with access to what it stores. This page is the honest version of what that is — written plainly, because that's how I'd want to read it.
The short answer: most of what you log never leaves your phone, and I collect nothing I don't need to make the app work.
What stays on your device
Your areas, habits, main quests, completions, settings, the programs you've started, and any paths you write yourself are stored in a database inside the app, on your device. If you never sign in, none of that reaches me or anyone else.
Two things leave either way. About once a day, when you open the app, it asks my content server whether there are new programs or videos — and if that request doesn't get through, it asks again the next time you open the app rather than waiting out the day. The same server holds the media: playing or downloading a demo clip fetches it from there, and so does opening a meal card with a photo, or a path step with a recorded reflection. Those requests see an IP address and a browser version, the way any request to any website does. They aren't tied to an account, and nothing you've logged travels with them.
The other is a crash report. If the app breaks — the screen goes blank, or something throws an error it wasn't expecting — it sends me a short note about it, so that a bug on your phone isn't something I only find out about if you happen to write to me. The note is the error message, the stack trace that says which line of my code broke, the name of the screen you were on (“today”, or the Life tree and which branch was open), the app's version number, and whether you were in the iPhone app or a browser. Nothing you've written or logged goes with it — not a habit name, not a completion, not a word of a path you wrote. If you're signed in, it's attached to your account, so I can tell one person's five reports from five people's one; if you're not, it's attached to nothing. The app sends at most five per launch, drops them silently if you're offline, and doesn't retry. I keep them for 30 days, then a nightly cleanup deletes them.
One permission is worth spelling out, because it sounds bigger than it is. If you use “Add to calendar” on a training program, the iPhone app asks for calendar access so it can write that program's workouts into the calendar you pick. iOS only offers full access here — there's no narrower option that can also show you your calendars by name and clear out the workouts it added last time, which is what makes adding again replace them instead of leaving you with two sets. So I'll say plainly what it does with it: it lists the calendars you can write to, it writes the workouts, and the only events it ever reads back are the ones it created itself, by the identifiers it saved when it made them. It never reads, searches, or sends anywhere a single event of yours. Nothing about your calendar reaches me or leaves your phone. If you'd rather not, don't grant it — the same schedule exports as a file.
Deleting the app deletes that data with it.
What an account adds
An account exists for one reason: so your history survives a new phone. If you sign in, here is everything I hold.
- Your email address, and the day the account was made. It's how you sign in, and it's the only thing that identifies you. There's no password and no profile.
- A sign-in code, stored hashed, for the ten minutes it's valid.
- A session token, stored hashed, so you stay signed in. It expires after 90 days without use.
- The same records your device holds — habits, quests, completions, settings, programs, and the paths you write yourself, words included — copied as they are, so a second device can catch up.
- Whether you have Premium, and when it expires.
- Your IP address, briefly, as a rate-limit key on the sign-in endpoints. It's there so nobody can turn the code emails into a way to spam other people's inboxes. The count it feeds rolls over within the hour, the row holding it is cleared by a nightly cleanup, and neither is attached to your account.
- Any crash reports your devices sent, if the app has broken on one — attached to your account, so repeated breakage looks different from a one-off. What's in one is described above, and they're deleted after 30 days either way.
- A short trail of server logs. Every request to my API leaves a line on Cloudflare — the time, which endpoint it hit, and, when something breaks, the account it broke for. It's how I find a bug I can't reproduce. Nothing you've logged travels into it, and it ages out on its own.
That's the list. No location, no contacts, no photos, no advertising identifier, nothing read from other apps.
Two things inside those settings are worth naming on their own, since they only look like ordinary settings. The what-should-I-eat finder keeps the height, weight, age and sex you type into it, plus the activity level and the goal (bulk, maintain or cut) you pick from its lists, so your targets can be worked out again later — Apple counts that as health data, and that's fair. And if you give the app a name to greet you by, it's stored with the rest of your settings. Neither exists unless you entered it.
What I don't do
- No analytics inside the app. There's no analytics SDK in it, so I can't see which screens you open or how often you use it. The one exception is the crash report above: it names the screen that broke, and only when it broke. The website and the browser version of the app do sit behind Cloudflare's page-view counter — how many people landed on a page, roughly where they came from, how quickly it loaded. It sets no cookie and can't follow you anywhere. The iOS app isn't behind it at all.
- No advertising, no ad networks, nothing that follows you around other apps and websites.
- No selling or sharing your data — not with data brokers, not with anyone.
- No training any model on what you log.
Other people
There aren't any. NeeTree has no feed, no friends list, no leaderboard, and no way for one person to see another's habits, completions, or email address. Until August 2026 there was one small exception — a Season showed a count of how many people were walking the same program as you. It was only ever a number, and it's gone now.
Payments
Purchases run through Apple in the iOS app, or through RevenueCat's web checkout (with Stripe) on the web. I never see your card number. What comes back to me is whether your account has Premium and when it renews — nothing more. Their own policies cover what they collect: Apple, RevenueCat, Stripe.
Who else touches it
I keep this list short on purpose. Each one does a single job.
- Cloudflare — hosts the app, the API, the database, and this page.
- Resend — sends the sign-in email. It sees your address and the code.
- RevenueCat — records purchases and tells my server who has Premium. It holds an identifier for every account that signs in, not only the ones that buy: that identifier is how the answer comes back.
- Apple and Stripe — take the payment itself.
- Flodesk — sends the free starter guide and the couple of emails that follow it, if you asked for the guide on the website. Their script loads on that page for everyone who opens it, before anything is typed, and the address reaches them when you send the form. That list is separate from the app, it's the only thing your address is used for, and every email carries an unsubscribe link.
Nobody else. The database is mine, running on Cloudflare, and I'm the only one who can reach it.
How long it's kept
Your records stay as long as your account does — that's the point of them. A sign-in code stops working after ten minutes, and a session after 90 days without use. The rows themselves, and the rate-limit counters beside them, are swept by a cleanup that runs once a night, so a dead one can sit there for up to a day before it's actually gone.
Deleting your account
You can do it yourself: Settings → Account → Delete account erases the account and everything attached to it from my servers, right away and for good. Or email me at support@neetree.app from the address you signed in with, and I'll do the same and confirm when it's done. Deleting the account doesn't cancel a subscription — that keeps billing until you cancel it where you subscribed. To clear the copy on your device, delete the app — or use Reset in Settings, which wipes it and starts you fresh.
Your rights
Depending on where you live, you may have the right to see the data I hold about you, correct it, get a copy of it, or have it deleted. Email me and I'll do it — there's no form and no process. It's a short list to begin with.
Where it lives
Cloudflare's network is global, so your data may be stored or processed outside the country you're in, including the United States, where I am.
Children
NeeTree isn't built for or directed at children under 13, and I don't knowingly collect anything from them.
Changes
If any of this changes, I'll update this page and the date at the top.
Questions
support@neetree.app. I read them myself. If you'd rather write on paper: 322 Culver Blvd #1004, Playa Del Rey, CA 90293, United States.