Connections
My Daily Tool connects to the services you already use — fitness trackers, calendars, weather, news, markets — and every connection is opt-in, revocable, and honest about what flows where.
Every integration below is live in the app today. No Google services. No telemetry.
Live integrations
Each card names what syncs, where the data flows, and how to disconnect. Connecting is always your choice — nothing connects silently.
What syncs: steps, activity, sleep, and heart-rate data from your Fitbit account into Health Center.
Data flow: Fitbit's servers → the app's secure token proxy (tokens stay server-side, your phone holds only a session reference) → your device.
Disconnect: revoke access from the app\u2019s device settings or your Fitbit account. Tokens live server-side and are discarded on disconnect.
What syncs: recent activities and workout stats from your Strava account into Health Center.
Data flow: you log in at strava.com (OAuth2 — the app never sees your Strava password); the authorization code is exchanged for tokens through the app's server-side token proxy (tokens stay server-side, your phone holds only a session reference) → your device.
Disconnect: revoke access from the app's device settings or your Strava account at strava.com/settings/apps. Tokens live server-side and are discarded on disconnect.
What syncs: readiness, sleep, and activity data from your Oura Ring into Health Center.
Data flow: Oura app → Apple Health → your device. There is no direct Oura connection; the Oura app writes to Apple Health and the app reads it from there.
Disconnect: turn off the Oura → Apple Health sync in the Oura app, or revoke Health access in iOS Settings.
What syncs: workouts, steps, sleep, heart rate, and any other HealthKit data you approve, per-category.
Data flow: entirely on your iPhone — HealthKit never leaves the device, and the app reads only the categories you grant.
Disconnect: iPhone Settings → Privacy → Health → My Daily Tool, or revoke per-category.
What syncs: events from any ICS calendar URL you add — Google Calendar exports, Outlook, team schedules.
Data flow: your calendar URL is fetched through the app's ICS proxy (so the feed URL itself stays private) and merged into the Planner.
Disconnect: Planner → calendar feeds → remove the feed. Events from that feed disappear with it.
What syncs: forecasts for your routes and day plan — no account, no key.
Data flow: your approximate location goes to Open-Meteo's public API for the forecast you requested; nothing is stored server-side.
Disconnect: nothing to disconnect — weather is fetched only when you open a route or the forecast card.
What syncs: headlines for the News card, fetched on demand.
Data flow: the app's server proxy calls the World News API and returns headlines; your reading list never leaves your phone.
Disconnect: remove the News card from Home. No fetch, no data.
What syncs: crypto prices for the Finance watchlist, fetched on demand.
Data flow: the app's server proxy calls CoinGecko and returns prices; your watchlist and holdings stay on your device.
Disconnect: remove the Finance card or clear the watchlist.
The boundary
No Google sign-in, no Google Calendar sync, no Gmail — those were removed entirely. No analytics SDKs, no advertising identifiers, no crash-reporting service. The only automatic network traffic the app makes is the operating system's own; everything else on this page is fetched because you asked for it. The privacy policy has a “verify it yourself” section with proxy-inspection steps so you don't have to take our word for it.
