The website uses Google Analytics to track anonymized site navigation patterns in the same way as most websites in the world. Google Analytics relies on cookies to track this information.
If you leave personal information to get early access to the app, if you give us feedback, or if you contact support, we only use your personal information in-house to follow up with you as promised.
If you download the Herotime app through one of the links provided on this website, like for any other downloads, we may see general, anonymized download statistics from Apple.
You can find details about how the Herotime app uses any of your personal information and application data within the app. Here are some additional notes on our view on privacy when it comes to user and application data.
We are building privacy into the Herotime app, as we would like to see it as users ourselves. Privacy is important to us. We don’t like to leave personal information all over the internet, unless there is a clear service offered to us that requires this information.
The app gathers anonymized usage information to allow us to improve the app in the best way for our users. However, we have decided against having user accounts to store user-created data at all at this point. User (vs. usage) data is only stored within your, the user’s own private cloud service, IF you decide to export any data at all. We offer storage in Evernote, Dropbox and Google Drive for now. The app transfers data from the user’s mobile phone to the user’s own cloud storage without transmitting any of this data to us as the developer of the Herotime service. We don’t ever see this data. For cloud storage, we request only a minimum number of privileges so that the app can store its own data. The app does not request or attempt to access any of the user’s other data in these cloud services.
At present, we do not employ a backend at all with which the Herotime app communicates. There are no central databases owned, managed and accessed by us. In the future, for certain synchronization operations as well as additional services that require this, we may employ a limited backend, but not for now.
There is a philosophy behind this: We believe that the future of user data storage is different from today. Users should and will not only own (a) their own personal data as well as (b) service-related data. They will also decide, which cloud service this data is managed in. Personal data such as name and date of birth will only be stored in a central storage facility that the user (or government?) decides on. Users will only give restricted access to this to the likes of Google, Facebook or Herotime. Mobile apps and web services will only transfer and manage service-related data for the user in a suitable cloud storage facility that only the user decide on, too. So the user keeps the privilege of seeing all the data stored by such services for them. Furthermore, the user can at any point in time decide to delete that data; the service has to account for this case. This is the data storage and privacy philosophy that we try to implement as best as possible with the Herotime app given the infrastructure available today.