Previously: Fantastical Version 3
I’ve finally had a chance to play a bit more with Fantastical version 3, and I’m really disappointed to learn that the new version of their Apple Watch app is useless without a free Flexibits account.
In version 2, the watch app synced data directly from the iOS app via WatchConnectivity. Version 3 syncs event data from the iPhone up to their servers, then back down to the watch. This was done to allow the watch to sync without a direct connection to the iPhone.
I’d prefer not to expose my event data to their server, even if it is end-to-end encrypted. Event data in my calendars doesn’t change without my direct input (or approval), so there really isn’t any benefit to me from enabling independence of the watchOS app.
Account passwords, events, tasks, and contacts are stored only on your device and are not sent to servers.
In the section titled “Where are my events, tasks, and contacts stored?”, this is contradicted:
Event and task data synced to your Apple Watch is stored on Flexibits servers. This data is end-to-end encrypted and we are unable to access it.
The summary claim (that event data is stored only on device) is reiterated in the section titled “When does an app send data to Flexibits?”:
Fantastical for iOS:
- When making changes to your calendar or dismissing alerts. No event data is ever sent to Flexibits, our servers only receive a notification that changes were made on your account. This notification is then relayed to Fantastical on your other devices.
For now, I’ve switched back to using the native Calendar watch app. In watchOS 6, it seems to offer everything that the version 2 Fantastical app did (with direct sync!). I’m still using Fantastical on iOS, but I’m going to give the native app another test run in the upcoming weeks.