Zingtree data consists of two parts: The decision trees that our customers build (by authors), and any data collected from use of those trees by end-users.
Zingtree's CTO will serve as the primary data custodian.
We treat all customer data as equally sensitive.
For decision trees, these are built using the author's browser. Zingtree sessions are defaulted as https, so there is no chance of a man-in-the-middle attack gaining access to the tree data.
For end-user use, trees can be deployed as https. Session history data is also sent to Zingtree's servers by https via an AJAX call from an end-user's browser.
Both decision trees and session history data are stored in a database server. Our infrastructure uses Amazon RDS, with a MYSQL database.
Decision trees authors access trees via a log in to https://zingtree.com. Authors can also gain access to reports and session data via this login.
End-users may access trees via a secret URL, or an iFrame embedded on a web page in a customer's intranet or web site. In addition, end-users may be restricted by IP address filtering using CIDR notation.
For tree authors, Zingtree has a Snapshots tool, which archives every change made by tree authors, and makes it easy to restore a decision tree to a previous stare, or compare versions. On the server infrastructure level, Our Amazon RDS system includes daily and weekly backups automatically.
All data collected by Zingtree is saved forever. Individual sessions may be deleted by any authorized author.