Privacy Policy
161 is built for people working on something personal, so we designed the app to know as little about you as possible. This page explains, plainly, what stays on your device, what reaches our servers, and why.
The short version: your health data, weights, meals, calories, journal entries, training logs, lives on your device and is not stored on our servers. Our servers only ever learn that you did something, never the numbers. Even coach chat stays on your device, see "Coach chat" below. The one exception is buddies, and only if you join: the tick for a habit you approve for a group is shared with that group, never weights, meals, cycle, journal or anything else. You can stop sharing a habit at any time.
Buddies (optional)
If you join a buddies group, your first name and a done or not done tick for each habit you choose to show are shared with the people in that group, and nothing else. Nothing is shared until you approve it, you can take a habit back whenever you like, and leaving the group stops all sharing.
What stays on your device
161 is local-first. The content of your day-to-day use is stored on your own device and is not transmitted to us:
- Weigh-ins and body measurements
- Meals, food logs, and calorie information
- Journal entries and moods
- Workouts, cardio, and training logs
- Your plan, its settings, and every adjustment you make to it
- Your answers to the health-readiness questions
- Your first-week record (the small steps you took in your first seven days)
If you delete the app (or clear your browser's site data on the web version), this data is gone with it. We could not recover it for you, because we never had it.
What we do collect
Account information
When you sign in (in the native app), we store the basics needed to run an account: your email address and a user ID. Accounts and data are hosted with Supabase, our authentication and database provider.
Your acceptance of the Terms
When you accept the Terms, in the app or at checkout on our website, we keep a record of it: the version you accepted, the time, and your account or checkout email. We keep this record for three years, including after you delete your account, so there is a record of what was agreed to.
The link that brought you
If you arrive from a link that carries tags (often called utm tags, for example which post or page the link was on), we store those tags with your checkout so we can see which links people came from. They describe the link, not you.
If you arrive from an ad on Meta or TikTok, the click identifier that ad added to the link is kept in your browser. When you start a trial or pay, that identifier is sent back to that platform from our server so the ad can be measured. No name, email, health or plan information is sent with it.
Occurrence-only usage events
To understand engagement, and to know when a gentle check-in might help, the app records that certain actions happened and when. For example: a weigh-in was logged, a workout was logged, a meal was logged, the app was opened. These events carry a name, a timestamp, and the platform (iOS, Android, or web). They never include the content or the values: not the weight, not the calories, not the mood, not a word of a journal entry.
We use these events for product improvement and for the re-engagement check-ins described below. You can turn this off in the app's settings, and it is off entirely when you use 161 without signing in.
From these events we also keep simple engagement summaries per account, things like the date you were last active, how many days you have logged something, and a lifecycle label (for example "engaged" or "inactive"), so we can see who might benefit from a check-in without reading through raw events.
Push notification tokens
If you enable notifications in the native app, we store the device push token needed to deliver them. Turn notifications off and it goes unused.
Website analytics
On our marketing site we record occurrence-only interactions: that a page was viewed or a button was clicked, with a random anonymous identifier stored in your browser. We do not store your IP address with these events, and we do not fingerprint your device. The anonymous identifier is never joined to a name or an email.
If you join the waitlist, we keep your first name, your email, the invite code we make for you, the code from the friend or creator link that brought you (if there was one), the plan you picked, whether you'd like to do this with a friend, any link tags, and a scrambled form of your internet address that we use only to stop spam signups. We use this only to tell you when 161 opens and to know whose link brought you. Email us and we will take you off the list.
Coach chat
The in-app coach runs entirely on your device. Your messages, your plan numbers, and the coach's replies never leave your phone or browser, are never sent to our servers, and are never processed by any AI service. Changes the coach makes to your plan also happen on your device.
Re-engagement check-ins
If you have been away for a while, we may send a gentle check-in by push notification or email. These are deliberately constrained, with the core limits enforced in our database, not left to good intentions:
- Never more than 2 messages in any rolling 7-day period
- Each type of message has a cooldown of at least 30 days before it can repeat
- The moment you open the app again, any pending check-in is automatically cancelled
- A do-not-contact setting that always wins, ask once and outreach stops
- No sends during quiet hours (10pm–8am in your timezone)
To stop these at any time, use the notification settings in the app or email us and we will set do-not-contact on your account.
After you join, we also email you a few getting-started notes in your first week (each has an unsubscribe link), and notes about billing, such as a reminder before a free trial ends or a notice of a failed payment.
Payments
If you buy a membership on our website, payment is handled by Stripe, which holds your card details. We store your email, your Stripe customer identifier, your plan, and whether your membership is active, never your card number. We use your email to send you a welcome email with how to get started and the getting-started and billing notes described above, and to link your membership to your app account when you sign in with that same email.
Apple Health
In the native iOS app, and only with your permission, 161 reads your step count from Apple Health. Steps are processed on your device to inform your plan. They are not sent to our servers.
What we don't do
- We do not sell your personal data. Not to advertisers, not to data brokers, not to anyone.
- We do not use third-party advertising trackers. There are no ad pixels or ad SDKs in 161.
We share data only with the service providers needed to run the product, Supabase (accounts and hosting) and Vercel (web hosting), each only for the purpose described above.
Deleting your data
You can delete your account from within the app. That deletes your server-side account and everything associated with it, your email, usage events, engagement summaries, and push tokens. The one thing we keep is the record that you accepted the Terms, described above, for three years. You can also email us at [email protected] and we will delete your account for you.
Your on-device health data is yours to remove any time by deleting the app or clearing its data, it was never on our servers to begin with.
Age
161 is for adults. You must be 18 or older to use it, and we do not knowingly collect data from anyone under 18. If you believe someone under 18 has created an account, contact us and we will delete it.
Changes to this policy
If we change how we handle your data, we will update this page and its effective date. For meaningful changes, we will tell you in the app before they take effect.
Contact
Questions about privacy, or a deletion request: [email protected].
161 provides general fitness and nutrition guidance and is not medical advice. See our Terms of Service for the full health disclaimer and crisis resources.