ActiPrivacy
The short version: your activity data stays on your watch and phone. Nothing leaves your devices unless you turn on an AI feature or create a cloud account — and even then we send the smallest useful summary, never raw sensor streams. No ads, no trackers.
What stays on your device
By default, Actidial is device-first:
- Steps, active minutes, calories, distance and heart rate are collected and stored on the watch, with a rolling history.
- Goals, units, reminders and your day-to-day history sync only between your own watch and phone over the Wear Data Layer.
- Weather uses your approximate location on-device to fetch a forecast (Open-Meteo by default). Location is used only for weather and sunrise/sunset, and is requested in the foreground.
- Calendar events (your next two) are read on the phone and pushed to the watch to display — their text isn't sent anywhere else.
If you never enable an AI feature or a cloud account, your activity data does not leave your devices.
What leaves the device — only if you opt in
Some optional, premium AI features need a backend. When you turn one on, you'll see a one-time consent screen stating exactly what's sent before the first call. Here's the honest picture:
| Feature | What's sent | Where it goes |
|---|---|---|
| AI configuration | Your typed message plus your current goals (e.g. step / active-minute / calorie targets). | Actidial's backend, which calls Anthropic to interpret it. |
| AI insights (coming soon) | A summary of recent activity (totals, trends, averages) — never raw per-minute samples. | Actidial's backend → Anthropic. |
| Meal calorie estimator | The meal photo(s) you choose to capture, to estimate calories and macros. | Actidial's backend → Anthropic. |
These features send activity summaries and, for meals, the photos you take. We deliberately minimise: the smallest data that answers the question, never raw sensor streams, calendar contents, or your device identifiers in prompts.
The backend and Anthropic
When an AI feature is on, requests go to Actidial's backend, which holds the API credentials and calls Anthropic's models to generate the result. This lets us meter usage and rotate keys without shipping a secret in the app. The Install Assistant on this website works the same way — your questions are sent to the backend to generate a reply, and the conversation is kept only in your browser tab (session storage) until you close it.
No ads, no trackers
Actidial contains no advertising SDKs and no third-party analytics or tracking. This website self-hosts everything it needs — no external fonts, CDNs or tracking pixels.
Cookieless site analytics
To understand which pages are useful, this website records basic, self-hosted page-view analytics — sent to our own backend, never a third party. For each page view we store the page path, the referring URL, a coarse browser family (e.g. "Chrome, mobile" — parsed on the server, no version or device fingerprint), a truncated IP prefix (first three octets only, so it can't identify you), and a random per-tab session id kept in your browser's sessionStorage and discarded when you close the tab.
There are no cookies and no cross-site or persistent identifiers. If your browser sends Do Not Track, we send nothing at all. The code is a tiny self-hosted script (assets/analytics.js) you can read.
Your control
- AI features are off until you enable them and are gated behind an explicit consent screen.
- Consent is revocable — turning an AI feature off stops future sends and clears any stored key.
- Because activity data lives on your devices, uninstalling removes it; a cloud account (if offered) can be deleted on request.
Cloud accounts
Actidial works fully without an account. If a cloud sync/account option is offered in future, it will be opt-in, clearly described at sign-up, and deletable on request.
Contact
Questions about privacy, or a data request? Email hello@actidial.com.
This page describes how Actidial is designed to handle data. It isn't legal advice; a formal policy will accompany the store release.