Chronus Information Widgets
Our Privacy Policy
We do not collect, nor do we share any Private information of our users. The information Chronus uses is exclusively limited to displaying the appropriate content in the placed Widgets on the configured device.
The permissions we need
The ACCESS_COARSE_LOCATION, ACCESS_FINE_LOCATION and ACCESS_BACKGROUND_LOCATION permissions are used to determine the device's Geolocation coordinates (Latitude/Longitude) when geolocation is turned on and the weather data is refreshed.
NOTE: neither of these permissions are used anywhere else in Chronus and if weather is not enabled, their associated data is not accessed.
We use the ACCESS_NETWORK_STATE to detect when the network state changes so we can either stop background network queries (Weather, News) when the network is not connected (such as when Airplane mode is on) or restart the queries when the network becomes available again. This saves a lot of battery!
The DISABLE_KEYGUARD permission is needed to allow for the clicking of links in the News and Forecast panels while on the Lock screen. We use this permission to trigger the standard Android secure unlock challenge API prompting the user to unlock so that Chronus can launch the browser to display the link. Your device's security is not compromised in any way.
The INTERNET permission is required for the widget to access your device's network to retrieve the Weather and News data.
The calendar panel uses the READ_CALENDAR permission for accessing the calendar API to retrieve upcoming calendar events.
RECEIVE_BOOT_COMPLETED is required to trigger the starting up of the back-end services at boot time. These services include the Weather, News, Tasks, Stocks and Calendar update services.
The WAKE_LOCK permission is required to wake the device temporarily to do a any of the background updates. These updates typically only take a second or two after which the WAKE_LOCK is released and the device goes to sleep again.
The READ_EXTERNAL_STORAGE and WRITE_EXTERNAL_STORAGE permissions are used by the 'Backup and restore' feature when writing and reading the backup files to and from the SDCARD.
The GET_ACCOUNTS and READ_CONTENT_PROVIDER permissions are used by the built-in Gmail Extension to list the available accounts and display an unread count. We don't have any access to the email content. NOTE: neither of these permissions are used anywhere else in Chronus and if the extension is not enabled, their associated data is not accessed.
The USE_CREDENTIALS permission is used if the Google Tasks widget is enabled to allow for login.
The ACTIVITY_RECOGNITION permission is used by the built-in Fitness+ widget to show the Step, Calorie or Distance counters.
The BILLING permission is self explanatory.
And lastly, the READ_LOGS permission is used for the 'Logcat' feature in the About Chronus section and only allows access to the Chronus log events, nothing else.
The OAUTH scopes we may use
Google Tasks API (.../auth/tasks) - Create, edit, organize, and delete all your tasks: Chronus includes a optional 'Tasks Widget' that allows the user to display, create and edit their Google Tasks and Task lists. Tasks functionality is also integrated into the Chronus's 'Calendar widgets', allowing for the display, creation or editing of the user's Google Tasks with a due date.
The data is used only for display and management purposes within the widget. The user's data is stored on the authenticated device only, and not shared or used for any other purposes other than what is stated above.
You can watch a video demonstrating it's use on YouTube