Privacy Policy
The short version: your Home Assistant is yours. The app talks straight to it, and your home’s states and controls do not pass through us. Some things do leave your devices: notifications pass through our push relay, webhook messages are stored on it for a short time, the app sends usage analytics and crash reports, and a few features you choose to use send what is listed below. This page names each one.
Effective Date: November 9, 2026
Who we are: Wrist Assistant is run by Jesse Skelton, in the United States.
What stays between you and Home Assistant
Section titled “What stays between you and Home Assistant”Your devices connect to your own Home Assistant, on your home network or at the remote address you choose. Your entity names and states, pages, settings, complications, camera pictures, voice clips, and home map stay between your devices and your Home Assistant. Your watch and iPhone each hold a key made for that Home Assistant. Neither keeps your Home Assistant password.
Push notifications: our relay on Cloudflare, and Apple
Section titled “Push notifications: our relay on Cloudflare, and Apple”Home Assistant cannot reach Apple’s push service by itself, so the Wrist Assistant integration sends each push through our relay, a Cloudflare Worker at push.wrist-assistant.com. The relay holds our Apple push key and passes the push to Apple’s push service (APNs), which delivers it.
What the relay sees for each push: your device’s APNs token, the notification’s title and text, and its data. That data can hold its buttons with the entity ids they act on, and a one-time token for a camera snapshot. For an app older than the snapshot token, it also holds a link to the snapshot on your Home Assistant’s address. The relay also sees the internet address your Home Assistant connects from. The camera picture itself does not pass through the relay: the app fetches it from your Home Assistant.
What is kept: our code stores none of this. When a device registers, the relay signs a token for it and hands it back to Home Assistant, which keeps it. The relay keeps no copy. Its log lines hold no notification text and no tokens.
Apple receives the same push to deliver it, under Apple’s privacy policy.
Cloudflare’s logs. The relay has Cloudflare’s Workers Logs turned on. For each request they record details of the request and the response, along with our log lines, and Cloudflare keeps them for up to 7 days.
Wrist Webhooks: stored on the relay
Section titled “Wrist Webhooks: stored on the relay”This applies only if you set up a webhook in the iPhone app (Settings, Webhooks) or pair the Wrist Notifier app. A webhook gives you a web address and an email address that any service can use to push to your wrist.
A webhook’s record. The relay stores the hashes of its tokens (not the tokens), your devices’ APNs tokens with their platform, your watch ids, your topic and delivery settings, the plan the app reports (free or Pro), and, for a paired Wrist Notifier, its public key. It is kept until you delete the webhook in the app. A device’s token goes earlier if Apple reports that it is dead.
Messages in the inbox. Each message a service sends is stored with its title, text, tags, link, buttons, topic, priority, and time, unless the sender turns the inbox off for that message (Cache: no). Your devices read it back from there.
- A message is no longer served after 48 hours.
- It is deleted at a later publish on that webhook, or at the latest when the webhook has been idle for 7 days, when all its stored messages are deleted.
- Deleting the webhook deletes its stored messages at once.
End-to-end encryption. A webhook can use it. The relay then stores only the sealed message and cannot read it. A title the sender adds outside the sealed part, the topic, the priority, and the sound stay readable to the relay.
Email. Mail sent to a webhook’s email address arrives through Cloudflare Email Routing. The relay turns it into a message: the subject as the title, the first 32 characters of the sender’s address as a tag, and up to about 3,500 bytes of the text. It is then stored like any other message.
Answer buttons. A message that asks a question keeps a hash of its answer token and the answer for up to 48 hours.
Short-lived records. During webhook setup and Wrist Notifier pairing, the relay keeps the device’s APNs token for up to 10 minutes. It counts attempts per day by your internet address, stored as is, and deletes those counts at the next midnight UTC.
Logs. Our log lines for a message hold its id, its topic, and whether it was sealed, not its text.
A message in a web address. A sender can publish with a plain web address that carries the message in it (GET /w/.../publish?message=...). Cloudflare’s logs may record that address, message included, for up to 7 days. To keep a message out of them, send it in the body of a POST request.
How long a webhook lasts. A webhook’s record stays until you delete it.
Usage analytics: PostHog
Section titled “Usage analytics: PostHog”The iPhone and the watch send usage events to PostHog, at its US address us.i.posthog.com.
From the iPhone: events such as the app opening, onboarding steps, Settings opening, the Pro screen opening and purchases being started or finished, and What’s New being read. With them go the integration’s version, how many homes the iPhone uses, and whether it has Pro, plus what the PostHog library adds on its own, such as the app version and build, device model and type, screen size, system version, language, time zone, whether the network is Wi-Fi or cellular, and whether the app is a TestFlight build or runs on a simulator.
From the watch: events such as a tile tap, a quick menu opening, a gesture, a page change, and a change of connection route, sent with its source, its time, and a short list of allowed fields. From version 3.2, those fields are fixed words from the app, such as a device type like light, and a check in the app drops anything else, so no entity id, page name, or room is sent. Watch versions before 3.2 also send the entity id and page name of a tile tap, the entity of a confirmed or cancelled action, and the room of an automatic room change.
The identifier. Each device has a random id that PostHog events carry. The iPhone’s comes from PostHog’s library. The watch’s is made once on the watch and stays when you sign out. Neither is tied to a name or an account, and the app creates no PostHog person profiles. Because the id stays the same, events from one device can be connected to each other.
There is no switch in the app to turn this off.
Your internet address. PostHog receives the internet address of each device that sends to it. Our project tells PostHog to discard that address, so it is not stored with events. Before it is discarded, PostHog uses it to add a rough location, such as a city and a country, to each event.
How long. Our PostHog plan has a 1 year retention period. PostHog says events past that time may be deleted at any point, and are not deleted the moment they pass it.
Crash reports: Firebase Crashlytics and PostHog
Section titled “Crash reports: Firebase Crashlytics and PostHog”iPhone: crashes go to Firebase Crashlytics, a Google service. The app adds no user id, custom keys, or log lines of its own to these reports. Firebase Analytics is off. Google’s documentation says Crashlytics adds device details, such as the system and the hardware model, its own identifier for the install, and a Firebase installation ID. Google says it keeps crash traces and those identifiers for 90 days.
Watch: an uncaught crash is saved on the watch and sent to PostHog at the next launch, with the error’s name and reason, the first 20 lines of its stack, and its time.
Live Support
Section titled “Live Support”Live Support is hidden and off by default, and it runs only when you start it. You turn it on in the iPhone app’s Developer Tools, then tap Start Session in Settings, Support, and give the 6-digit code to support. A banner stays on screen with a way to end it.
What support sees during a session: your device model, system and app version, language, battery level, and Low Power Mode; your Home Assistant’s host name and whether it answers; how many entities you have of each kind; the app’s log lines and activity on the iPhone; and, when support asks for it, a copy of the app’s setup. The app strips tokens, passwords, and authorization headers first, and reduces your Home Assistant’s address to its host name in the status and setup messages. Other text in the logs, such as entity ids, is sent as it is.
How it travels: through a separate Cloudflare Worker, wrist-assistant-support-relay. It passes messages on and does not store them. A code with nobody joining ends after 10 minutes, and a session ends after 30 minutes at most.
Downloads: support can download a session’s logs and the setup copy to help you. We keep them only as long as it takes to solve the problem.
Complication gallery
Section titled “Complication gallery”This applies only if you press Share to gallery in the panel, or use the gallery on wrist-assistant.com.
What an upload holds: the complication’s share text, its title, description, notes, tags, slot labels, the author name you type, preview pictures, the panel’s version, the device kind, and a fingerprint and id of the design it came from. The same scrub as the panel’s Share text removes entity ids and friendly names first. Free text you wrote is not scrubbed, so the panel lists it for you to check. An approved upload is public, apart from the id and fingerprint.
What identifies you: a hash of a random gallery key your browser keeps. It lets you update or remove your own uploads. Votes store a hash of a random id your browser keeps.
Internet addresses: daily limits count uploads, votes, and imports by a salted hash of your internet address. The address itself is not stored, and the counts are deleted after about two days.
Who sees it: uploads are stored in Cloudflare D1 and R2. The owner reviews each one before it is public. A private Discord channel gets the title of each new upload.
How long: until you press Remove in the panel, which deletes the upload, its pictures, and its votes.
Rejected uploads: an upload the owner rejects or takes down stays in the database with that status, and its preview pictures may stay too, until they are deleted by hand. Email us to ask for that.
Our websites
Section titled “Our websites”wrist-assistant.com and docs.wrist-assistant.com are hosted on Cloudflare Pages, which sees the internet address of each visit. A pairing link or a complication link keeps its contents after the # sign, which a browser does not send to a server.
Our pages carry the Cloudflare Web Analytics script, which counts page views and measures how fast pages load, with details such as the page, browser, system and country. Cloudflare says it uses no cookies and does not track visitors over time.
When you contact us
Section titled “When you contact us”If you email us, post on GitHub, or post on Discord, we see what you send there. GitHub and Discord are public or community services with their own policies. Support Diagnostics on the iPhone and the watch’s diagnostics download make files that stay with you until you choose to send them. Tokens and authorization headers are removed from the iPhone’s bundle.
Email to [email protected] passes through Cloudflare Email Routing to Google’s Gmail. It stays there until we delete it.
Purchases
Section titled “Purchases”Pro is bought through Apple. We never see your payment details. If you use webhooks, the app tells the relay only whether your plan is free or Pro.
Other places the app connects to
Section titled “Other places the app connects to”- Addresses you set up. HTTP actions and web card tiles go to the addresses you give them.
- Your remote access. If you use Home Assistant Cloud or another remote address, that service carries your connection.
- GitHub. The iPhone asks GitHub’s public API for the integration’s latest version. GitHub sees the iPhone’s internet address.
Permissions
Section titled “Permissions”- Camera (iPhone): scanning the pairing QR code, photos you choose for tile icons, and scanning rooms for the home map. Photos and room scans go to your Home Assistant.
- Microphone: Assist voice commands on the watch, and voice clips you send to your speakers or to an HTTP action.
- Local network: finding your Home Assistant.
- Siri: adding tasks and running quick actions.
- Compass heading (watch): Point Control reads it on the watch. The app does not ask for your location.
What we do not collect
Section titled “What we do not collect”- Your name, email address, or phone number, unless you give them to us when you contact us or type them in a gallery upload
- Advertising ids
- Your device’s location from its location services
- Your Home Assistant password or access tokens
- Your entity names and states, apart from what you choose to put in a notification, a webhook message, a Live Support session, or a gallery upload, and what watch versions before 3.2 send as described under Usage analytics
Sharing
Section titled “Sharing”The services named on this page handle data for us. The app contains no advertising code, and it declares no tracking to Apple.
We do not sell your personal data or share it for advertising.
Your choices
Section titled “Your choices”- Delete a webhook in the iPhone app (Settings, Webhooks) to delete its record and messages.
- Remove a gallery upload in the panel.
- Remove a device in the Wrist Assistant panel to end its pairing.
- Delete the app to stop it sending anything from that device.
To ask for a copy of your data or its deletion, including from PostHog and Crashlytics, email [email protected].
Children
Section titled “Children”Wrist Assistant is not made for children under 13, and we do not knowingly collect their data. If you believe a child has given us data, email us and we will delete it.
Changes
Section titled “Changes”We may update this policy. Changes will be posted here with an updated date.
Contact
Section titled “Contact”Email: [email protected]