<aside> <img src="/icons/exclamation-mark_red.svg" alt="/icons/exclamation-mark_red.svg" width="40px" /> timing takes your privacy very seriously. We do not store any personal data — it stays completely private. timing’s foundations were carefully constructed so that it’s never incentivised to know anything about you personally. We’re fully committed to this position and want to be completely transparent about all privacy related matters.

</aside>

Permissions

timing can request the following permissions at various points during its usage:

<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" /> *Requests are prompted ***using the standard device privacy prompts, which clearly communicate intent.

</aside>

timing is a calendar & planner, and so in order to take full advantage of its fundamental utility, calendar and reminders permissions are required. Granting both will give timing access to the calendars and reminder lists already connected to your device. That said, both are not essential. If you only provide calendar permissions, you can use timing to manage your calendar only. Whereas only providing reminder permissions effectively turns it into a to-do list app.

Notifications are mainly required in order to send alerts for events & reminders at the requested times. They are also used to send your timely summaries and to let you know when an active timer is finished.

Location is used for improved suggestions when a location is being attached to an entry. This is purely to accelerate the process, and doesn’t send your location to a third-party — everything happens on device. Location is also used to present a list of local events happening nearby. Your GPS coordinates are sent to Yelp who provide the results — no user identifiable data is sent in the request. That is, Yelp is queried for data tied to a specific location, and has no other information linked to you in any way. Please refer to Yelp’s privacy policy to understand what they do with the data they’re sent.

Data

timing is an alternative interface for your existing calendars and reminder lists. That is, we do not personally store any of your events or reminders. We retrieve them using the EventKit system framework, and any edits made are sent to the system to update. For example, if you make an edit to the title of an event or reminder within timing, the change will be reflected in the iOS Calendar and Reminder apps immediately, and vice-versa.

timing does include an additional data layer so you can assign custom metadata to the aforementioned entries. For example, to set an estimate or energy level for a task (fields that don’t exist within the Calendar or Reminders apps). This information is stored locally on device, and can move between devices using the CloudKit system framework which securely stores data in iCloud on behalf of the user.

Integrations

timing has carefully selected a few third-party services who respect user privacy and whose additions help us make timing a better product for you.


Instabug is used to monitor app performance & quality with data sent anonymously. Please refer to their privacy policy to understand what they do with the data they’re sent. You can file bug reports/feedback with your personal details if you wish but this can be communicated anonymously too. The information collected through Instabug helps timing perform better and more reliably, and deliver to users their personally requested features.

Amplitude is used to monitor user engagement anonymously. Please refer to their privacy policy to understand what they do with the data they’re sent. The information collected through Amplitude helps us understand how people are using timing, so our development focus is clear. This ensures we prioritise work in areas that have deep engagement, identify pain points in need of improvement, and re-evaluate under-utilised features.

If you unlock timing’s premium Everything upgrade (whether through a subscription or lifetime purchase), additional non-personally identifiable data will be stored locally on device. We will only receive information on whether or not you have access to the upgrade, the term you signed up for and when it is due to expire (we have no knowledge of your billing — or any personal — details). This anonymous data is shared with RevenueCat, our purchase provider who facilitate the purchasing flow. Please refer to their privacy policy to understand what they do with the data they’re sent.