Intel Labs QS Sense-Making Too

by Intel Labs

An in-browser platform to help users make sense of their personal data.

An in-browser platform to help users make sense of their personal data.

The goal is to build a data analysis and visualization toolkit that is accessible to the long tail of less technically-inclined self-trackers. Although this toolkit will support import from CSV/JSON files, we plan to integrate with several popular services to make the import process easier for our users.

The system syncs timeseries data periodically, with the syncing interval determined on a per-service basis to respect API rate limits. This process is automatic by default, but individual users may opt out on a per-service basis.

Future versions of the system may allow for users to share their data with others for the purpose of collaborating on data analysis and visualization. Sharing will be on a purely opt-in basis, with the user selecting specific datasets to share and specific users to share them with. No data will be made public.

The platform is currently in development, with the first production release scheduled for end-of-year.

If you have any questions regarding this request, or if you require additional details before issuing an API key, please let us know via the following email addresses:

savage.evan@gmail.com
lama.nachman@intel.com

(see description)

- user data will be stored in a MySQL database that is owned by a password-bearing non-root user, and set up to only accept localhost connections;
- users will be authenticated via one of: email/password, Facebook Connect, Google/OpenID;
- all web traffic will be over HTTPS with a valid signed SSL certificate, to protect personal data and user credentials;
- all access to personal data will require authentication;
- by default, users will only be able to access their own personal data;
- any functionality to share data between users will require explicit opt-in by the user who owns the data;
- the user will be able to request permanent deletion of their personal data from the service.

If you have any questions, or want more specifics (CSRF tokens on non-GET requests, proper escaping to prevent XSS holes, etc.), let us know!

(see description)