AMEE:Privacy policy

From AMEE

This page defines various privacy policies relating to the AMEE project.

AMEE Service Privacy Policy from an end-user perspective

We have tried to keep AMEE as far away from privacy issues as possible.

In relation to 3rd party entities who build front-end applications using the AMEE Managed Service (e.g. UK Government, Google, Morgan Stanley, etc.), the following applies;

o AMEE uses an anonymous key system. 3rd parties create and manage their user's energy profiles using this key.

o 3rd parties store the answers to questions in the AMEE platform WITHOUT revealing personal identity information. AMEE does not store your name or e-mail address.

o AMEE does not own your data, the 3rd party does (and this is based on its user agreement with you).

For example;

The 3rd party (e.g. Google) knows who you are. They store an anonymous key in their database against the account you hold with them.

AMEE stores this anonymous key against an AMEE profile. The AMEE profile is populated when you answer a question on the 3rd party site (e.g. you have 1 car) and stores this answer on their behalf. Since the AMEE profiling engine is tied into its CO2 calculation engine, whenever the 3rd party asks "what's the CO2 profile of 1 car with this anonymous profile key", AMEE returns the CO2 value in Kg. The 3rd party then displays the answer to you.

AMEE can, with the 3rd parties permission (and therefore yours), look at anonymous, aggregate trends. There are over 500,000 aggregate AMEE profiles today (18 Feb 2008).

By enabling many organisations to retain their user-relationship, but enable anonymous, aggregated analysis, the AMEE team hope to enable broad trends to be analysed and acted upon.

AMEE Wiki policy

Aside from the public contributions you make to this wiki, we will never share or otherwise use your personally identifiable details (e.g. email/name) without your explicit prior approval.

Please see the Copyright page for other details.