PrivacyThe transparency of recorded information and the privacy of proprietary information have been important considerations for the DevCreek team from the beginning.
It is our explicit policy to be transparent about the data we are collecting. The API's we use to collect the data are documented and open. Where it makes sense, we provide simple manual online data submission screens. In other cases, the tools we have created to send data to the central DevCreek service use these same public API's. We also work with other Tool creators to ensure that they send data that conforms to the transparent, public API's. Please refer to our Metrics section for more details on the various public API's supported by DevCreek.
For our Testing API clients, we currently record Java and Ruby test results, and details of how the DevCreek Eclipse client is being used. We intend to expand to record other kinds of test results, but we will always provide details of what we record. From the Eclipse client, users can also download and examine all of the information that has been recorded recently for their projects.
We have two kinds of project in DevCreek, Open and Walled. Walled projects are not included in aggregate reports, and limit access to project-specific reports to project members.
Walled project data, once obfuscated to remove identifying project and method name information, may be used for industry vertical reports or research reports.
How is the data transferred?
Users can upload data via either HTTP or HTTPS. We highly recommend HTTPS.
Where is the data stored?
The data from the DevCreek client is sent to a central secured server that collects and collates results for teams all over the world.
How is the data accessible?
The data can be seen in the Eclipse client and the web site; people can also use the client to download data for their own projects to their local machines. All attempts to access data must pass the same security checks.