Your user name and password for any grid service (e.g.Second Life) are never transmitted to anyone other than that grid service.
By default, the viewer contacts our server to download certain resources (eg fetching release notes when a version is first used). The only identifiable information transferred is the IP number. Access is logged, as is normal for almost every web server, but no additional use is made of the information
Our web services (eg Confluence, Jira, Bitbucket) allow access without creating a login although in most cases having an account makes for a better experience. We used hosted services provided by Atlassian.
We maintain an access log of all connections to our server, including IP addresses. The log does not contain personally identifiable information. We may analyze the log to monitor download counts, web site "hits", etc.
The sections below describe these policies in more detail.
Metaverse Login Details
This section describes our policy regarding your metaverse login details, i.e. the user name and password that you use to log in to a grid service such as Second Life.
The viewer only transmits your metaverse login details to the grid service(s) you use, strictly for the purpose of logging in to the grid service(s).
The viewer never transmits your metaverse login details anywhere else.
To make logging in more convenient for you, the viewer may store your metaverse login details on your computer. Your password will not be stored unless you have instructed the viewer to do so (e.g. by enabling "Remember my password"). In that case, your password is stored in an encrypted form on your computer.
By default, the Kokua Viewer is configured to request certain resources from our web server. The viewer does not transmit your login name, password, or any personally identifiable information when connecting to our server. You may disable the viewer from connecting to our server as described below.
The viewer connects to our server in the following cases:
For redirection to the correct Release Notes page in Confluence when a new version is first launched
Kokua Website Login Details
Certain optional services on the Kokua website (eg the Jira issue tracker allow you to create an account in order to use those services. You are not required to create an account on those services in order to download or use the Kokua Viewer. This section describes our policy regarding user information you provide to those services.
Most of our online presence is provided through kokua.atlassian.net, a cloud based service provided by Atlassian
Some services may use browser cookies to remember that you are logged in to that service. You may disable cookies in your browser, but some services may not function fully without cookies.
For security purposes, the services may record the IP address that was used to create or log in to an account on that service.
Like most web sites, our server software keeps logs of all connections to the server, including the IP address of incoming connections. Your IP address does not identify you personally, and is not associated with your user name or other details about you, except that some optional services on our web site may record the IP address used to create an account for security purposes.
From time to time, we may analyze the access logs in aggregate (i.e. as a non-personally-identifiable collection) in order to measure download counts, number of web site "hits", and other similar metrics. We do not track any individual's usage of our website or of the viewer.
Access logs are viewable only to the web site operator and are removed from the server on a monthly basis.
Viewer Crash Logs
From May 2021 Windows versions of Kokua will use the BugSplat crash tracking service. It is not enabled on Mac or Linux builds for technical and user experience reasons but may be in the future if the available facilities improve.
In versions of Kokua that support crash reporting there is an additional tab in Preferences called Crash Reports. This allows you to determine what is sent along with the basic crash information. Sending the viewer log file is often invaluable for figuring out how a crash was caused, however it does include information such as IP number, file paths (and hence probably the login name, but not password, for the computer) and the teleport movements of the avatar in that session.
The Crash Reports tab also includes settings covering whether to include your avatar name (which will also be disclosed if the log file is sent) and whether to ask every time about sending crash reports. Setting it to ask every time gives an opportunity to write a brief summary of events that led to the crash and provide an email address if you choose to do so (in the absence of an email address we may make contact by instant message within Second Life).