đź”’ Privacy policy
Last updated: 17 November 2026 · עברית
Wellness Bot is a Telegram bot for keeping track of habits and health: reminders, the answers you give, and data from health services you choose to connect. This page says what it keeps, why, who else sees it, and how to delete it.
Who runs it
Wellness Bot is a personal, non-commercial project run by one private individual (the "operator") for themselves, family and friends. It is not a company, it is not sold, and it has no advertising.
Contact: the operator, through the bot
What the bot keeps
- Your Telegram account’s number, so the bot knows it’s you — not your name, username or phone number.
- Your settings: language, timezone and quiet hours.
- What you set up and log: trackers, reminders, your answers, and anything you write to it (notes, and a few lines about yourself if you add them, which may include health conditions and medication you choose to share).
- If you connect a health service (Garmin or WHOOP): the data it provides — such as sleep, heart rate, heart-rate variability, resting heart rate, blood oxygen, breathing rate, steps, calories, stress, recovery, strain, and your workouts with their details — and the access key the service gives the bot. You sign in on the service’s own page; the bot never sees your password there.
- If you connect an Android phone (with the HC Webhook app, or the bot’s earlier Android app): the Health Connect data you allow it to read (such as steps, sleep and its stages, heart rate, heart-rate variability, blood oxygen, weight, body fat, blood pressure, and workouts with their laps), with the name of the app that recorded each — and a key it sends with it, stored only as a fingerprint the server can check. Heart-rate readings are used to fill in your workouts, not kept.
- If you connect an iPhone (with the PulsHealth app, or the earlier Wellness Shortcut): the Apple Health data you allow it to share (such as steps, sleep and its stages, heart-rate variability, resting heart rate, blood oxygen, weight, blood pressure, and workouts with their heart rate and laps), with the name of the app or device that recorded each — and a key it sends with it, stored only as a fingerprint. Workout routes (locations) and the personal details PulsHealth can send (name, email, birth date) are discarded, never stored.
- If you use the AI features: the insights written for you, and a record of what you asked the assistant and what it proposed.
- Short technical records: which command was used and when (kept 90 days), and server logs (kept until the service is next updated, usually a few days).
What it’s used for
Only to run the bot for you: sending your reminders, recording your answers, showing you your own data, and — only if you turn them on — writing AI insights and understanding your free-text requests.
Nothing else: your data is never sold or rented, never used for advertising or marketing, and never used to build a profile of you for anyone else.
Who else sees it
- Telegram carries your messages with the bot, under Telegram’s own privacy policy.
- Anthropic (the maker of Claude) — only if you turn on AI insights or the free-text assistant. For each insight or request, the bot sends what that needs: your trackers and entries, your reminder times, health-service numbers for the period, your workouts (type, time, length, distance and heart rate, never where), and the lines about yourself. Anthropic processes it under its commercial API terms, which don’t allow using it to train models.
- Your own Claude — only if you connect it to the bot yourself. It then reads your data with the permission you gave, under your own agreement with Anthropic, and can send workouts it designed to your Garmin.
- Your training partners — only people you invited, or accepted, in /friends, and only what the two of you chose to share (workouts, and if chosen fitness, sleep, recovery or daily-activity numbers; never where you are, your trackers or insights). They see it in the bot, and their own Claude can read it when they ask it. Either of you can stop at any time; what their Claude already read can’t be taken back.
- Garmin and WHOOP receive only the bot’s requests to read your data, with the access you approved — and Garmin also receives the workouts your own Claude sends it, if you allowed that. On Android, HC Webhook (an open-source app by another developer, under its own privacy policy) sends your Health Connect data straight from your phone to the bot’s server only. On an iPhone, PulsHealth (an open-source app by another developer, under its own privacy policy) sends your Apple Health data straight from your phone to the bot’s server; PulsHealth contacts its own servers only if you sign into an account with it, which the bot doesn’t need.
- Amazon Web Services stores encrypted backups (in its Stockholm region). They are encrypted before they leave the server, and the key that opens them is kept neither on the server nor at Amazon.
- The operator can technically reach the server and its database, to run and fix it. They look at someone’s data only to fix a problem that person reported, or to keep the service working.
- YouTube (Google) — only if you press play on the short tour video on the website’s home page. The player then loads from youtube-nocookie.com, under YouTube’s own privacy policy. Until you press play, nothing on the website loads from YouTube or Google.
No one else. Your data is not shared with anyone for any other purpose.
Data from WHOOP
If you connect WHOOP, the bot reads your name on WHOOP, recovery, daily strain (cycles), sleep and workouts through WHOOP’s official API, with the permissions you approve on WHOOP’s own page. It uses that data only to show it to you and, if you turned them on, for your AI insights and assistant as described above. It never sells it, shares it for advertising, or uses it for anything else.
Disconnecting WHOOP in /connect deletes the bot’s access key at once; you can also revoke the bot’s access from your WHOOP account. The data already imported stays until you delete it (see below).
Where and how it’s kept
On a server run by the operator in Israel. Access keys for health services are stored encrypted (AES-256-GCM), the bot’s web pages use HTTPS, and backups are encrypted. No system is perfectly secure, so the bot keeps only what it needs.
How long, and deleting it
Your data is kept until you delete it. Sending /delete_me to the bot erases everything about you at once — settings, trackers, entries, health data and access keys. Copies inside backups disappear within 35 days, when those backups expire. Disconnecting a health service — or the phone, in /connect — deletes its access key immediately.
Your rights
You can see your data in the bot at any time, change it, disconnect health services, and delete everything with /delete_me. For anything else — a copy of your data, a question or a complaint — write to the operator, through the bot. You may also complain to your data-protection authority (in Israel, the Privacy Protection Authority).
Children
The bot is not meant for children under 16.
Changes
If this policy changes in a way that matters to you, the bot will tell you before the change applies. The date at the top is the current version’s.