Version 1.0, October 2019
Your privacy and permission is important to us…
We are committed to protecting and respecting your privacy.
This policy sets out the basis on which any personal data we collect from
you, or that you provide to us, will be processed by us. Please read the
following carefully to understand our views and practices regarding your
personal data and how we will treat it. By using WorldClock you are
accepting and consenting to the practices described in this policy.
Please note that some of the features discussed below may not be available
in the current WorldClock release and may reflect feature additions
scheduled to be incorporated in future releases.
We may change this policy from time to time by updating this page. You
should check back occasionally to ensure that you are happy with any
changes. This version of the policy is effective from October 1, 2019.
Who we are
Our website address is https://www.worldclock.ws
What personal data we collect and why we collect it
We do not collect any personal information about you or your use of
WorldClock. Should you choose to communicate with us via email (for
customer support or any other inquiries) we may save your name and email
address for the express purpose of facilitating future communications.
Under no circumstance will we disseminate this information to a third
party.
Sensitive data
We do not collect any sensitive data about you. Sensitive data refers to
data that includes details about your race or ethnicity, religious or
philosophical beliefs, sex life, sexual orientation, political opinions,
trade union membership, information about your health and genetic and
biometric data. We do not collect any information about criminal
convictions and offences.
Google Calendar users – your privacy and the WorldClock application
If you are a Google Calendar user, by using the WorldClock application, you
will be asked to authenticate a link between WorldClock and your Google
Account. This privacy policy clearly lays out Actions the
service may perform using this authentication. The summary below is
consistent with the
"Google API Services User Data Policy" (May 30, 2019 version)
. This privacy policy will be reviewed quarterly for ongoing consistency.
Google Calendar information that WorldClock collects
At a high level, the WorldClock application collects the following
information:
-
persistent identifiers (your Google ID);
-
various tokens required to access the Google Calendar API;
-
calendar and event information;
-
information that we get from you either directly or via the permissions
API.
The ID and API token information is saved locally and is strongly encrypted.
WorldClock accurately represents its identity and intent:
1. Our Identity: You authorise WorldClock
to access Google API Services on behalf of your account and these
credentials are kept confidential and secure.
2. Data Requested: The data types WorldClock requests are
limited to read-only access to your calendar and event information. If this
changes from what is disclosed in this privacy policy, then we will update
this privacy policy and prompt WorldClock users to re-consent to any
changes before we may access additionally requested data. When you
authorise WorldClock to access your Google Account, we request permissions
to view your list of calendars and all events associated with your
calendars.
How WorldClock uses information in, and with Google Calendar
So that you can recognise these Actions triggered by, or impacting Google
Calendar as an integrated system the next time you access them in
WorldClock, information from your Google Calendar account is used in the
following actions in WorldClock:
-
to list your upcoming calendar events for the day
– using the Google Calendar API we read and list all events for the
current day;
-
to create a long-term schedule of upcoming events
– using the Google Calendar API we will display a window of events
occurring within a user-defined date range
WorldClock's use of Google Calendar "Scopes"
When you give WorldClock permission to access your Google Calendar, WorldClock does so via the use of "scopes".
This is Google's mechanism to restrict an application's access only to specific areas of your Google account.
WorldClock uses the following scope to access your Google Calendar data:
-
https://www.googleapis.com/auth/calendar
WorldClock will use the https://www.googleapis.com/auth/calendar scope to obtain a list of
all available calendars in your Google account; from this list you can choose a specific calendar whose events
you want WorldClock to display. We also use this scope to obtain a list of all events for the current day in
your selected calendar; these events will then be displayed in WorldClock's daily activity panel. And finally,
this scope will be used to obtain an extended list of events spanning up to three months into the future;
these events will then be displayed in WorldClock's extended Schedule display. At the moment WorldClock will
read, but not modify, your calendar and event information. In a future release we intend to add the ability
to edit/create events directly from WorldClock; at this time we will need to modify your calendars and events
as required.
Note that WorldClock does not request access to information that it does not need.
Office 365 users – your privacy and the WorldClock application
If you are an Office 365 user, by using the WorldClock application you will
be asked to authenticate a link between WorldClock and your Office 365
account. This privacy policy clearly lays out Actions the
service may perform using this authentication. The summary below is
consistent with the
"Microsoft APIs Terms of Use" (May 2019 version)
. This privacy policy will be reviewed quarterly for ongoing consistency.
Office 365 information that WorldClock software collects
At a high level, the WorldClock application collects the following
information:
-
persistent identifiers (your Office 365 ID);
-
various tokens required to access the Office 365 API;
-
calendar and event information;
-
information that we get from you either directly or via the permissions
API.
The ID and API token information is saved locally and is strongly encrypted.
WorldClock accurately represents its identity and intent:
1. Our Identity: You authorise WorldClock to access Office 365 API Services on behalf of
your account and these credentials are kept confidential and secure.
2. Data Requested: The data types WorldClock requests are
limited to read-only access to your calendar and event information. If this
changes from what is disclosed in this privacy policy, then we will update
this privacy policy and prompt WorldClock users to re-consent to any
changes before we may access additionally requested data. When you
authorise WorldClock to access your Office 365 Account, we request
permissions to view your list of calendars and all events associated with
your calendars.
How WorldClock uses information in, and with Office 365
So that you can recognise these Actions triggered by, or impacting Office
365 as an integrated system the next time you access them in WorldClock,
information from your Office 365 account is used in the following actions
in WorldClock:
-
to list your upcoming calendar events for the day
– using the Office 365 Calendar API we read and list all events for the
current day;
-
to create a long-term schedule of upcoming events
– using the Office 365 Calendar API we will display a window of events
occurring within a user-defined date range
WorldClock does not request access to information that it
does not need.
How we protect your data
We have put in place appropriate security measures to prevent your personal
data from being accidentally lost, used or accessed in an unauthorised way,
altered or disclosed.
Data retention
We retain your calendar information locally in a file cache on your
computer. This is done to minimize the number of requests that need to be
sent to the calendar services. This data is ephemeral in nature and will
not, under any circumstance, ever be shared with a third party.
|