Last update: January 25th 2016.
Collection and Use of Personal Information
Personal information is data that can be used to uniquely identify or contact a specific individual.
Here are some examples of personal information that we collect:
- When you contact the CalenGoo support, e.g. for a support request, we keep a record of your communication.
Collection and Use of Non-Personal Information
Non-personal information is data that cannot be used to uniquely identify a specific individual. We may collect, use, transfer, and disclose non-personal information for any purpose. We may combine personal and non-personal information for certain purposes; this data will then be treated as personal information for as long as it remains combined. Conversely, aggregated information, i.e. data that might have originated from personal information, but that has been processed in such a way as to not allow personal identification, is treated as non-personal information.
Here are some examples of non-personal information that we collect – either by ourselves or through the use of third-party services:
- When you visit our website, we keep logs of your Internet Protocol (IP) address, browser type and language, referring and exit pages, operating system and date/time stamp.
- Our Software periodically checks our servers for important updates or notices or to download e.g. holiday calendars; in this case, we also log the IP address, device type, language, operating system and the date and time of the request.
- To increase the sync speed with Google Calendar CalenGoo uses a server that keeps track of changes. Google Calendar informs that server that a certain resource (e.g. a calendar list or a calendar) has changed. The next time the CalenGoo app syncs it can ask that sever which resources (called "channels") it has to sync. That makes the sync faster by syncing only e.g. the necessary calendars. The server knows only channel IDs, it does not know any details about your events or which event has changed. The server cannot access your Google account. It receives and stores only the notifications sent by Google. Google informs the server only that a certain channel has changed. And CalenGoo asks the server only which channels of a certain list (the list of calendars the user has) have changed. When contacting the server the IP of the request, the time, the channel IDs and the result are recorded.
- When using the widget or that Android Wear action to create an event by voice you can choose to use CalenGoo’s own parser server. That server receives the spoken text and splits it into the date and the title of the event.
- When using the "event tickets" function to find e.g. upcoming events and concerts, some anonymized usage data is collected (e.g. which buttons are tapped) and sent to the server. The purpose is to find out how users use this function and to use this data to improve the function.
Use of other services
CalenGoo Lite uses Google AdMob to display advertisements.
If you have any questions please contact email@example.com.