Usage Data

When you first start Tokaido, you'll be asked if you'd like to opt-in to our anonymous usage reporting tool. This page provides a bit more insight into what this tool collects and why we ask you to share this information with us.

As developers, we are are inherently skeptical of any data collection mechanisms when we encounter them. Most organisations make no assurances that they won't use this data to market to us, and of course when data isn't truly anonymous and is then stolen or leaked, it's us as users who pay the price.

We also see the incredible value that these collection systems offer to a developer. By being able to see how our tools are used in the wild. Tokaido is an open source, self-funded tool that we do not make any money from. This sadly means that we can't work on it full time, and so what limited time we have to contribute to the project needs to be directed into the most valuable new features and fixes.

For these reasons we've taken immense care in designing this usage reporting system in a way that honours our commitment to your privacy. We've designed a privacy policy that specifically limits what we can do with your data, and what data we can collect. Please click here to read the privacy policy in full.

The Usage Data We Collect

When you explicitly opt-in to the usage reporting system, Tokaido generates a random UUID that identifies your installation of Tokaido and that of any project(s) you use Tokaido for. These IDs are essential to ensure that we can record individual users and projects, without ever recording any sensitive data like your computer name or project path.

In addition, when you use Tokaido we collect the following information:

• Your Tokaido “Sync Strategy”
• How long it took your Tokaido project to startup
• Your system memory and CPU profile (cores and clock speed)
• The number of Tokaido projects configured on your system
• The version of Tokaido that you are using
• Which database engine and version you have enabled
• Which version of PHP you have enabled and non-sensitive PHP configuration settings such as allow_url_open, memorylimit, post_max_size, etc.
• Which Tokaido commands you run (but not their arguments, input, or output)
• Which add-on services you have enabled (such as mailhog, adminer, etc)
• Which Content Management System (“CMS”) frameworks you are using
• Which CMS versions you are using
• Whether or not you are using the PHP XDebug feature
• Your Operating System and version
• The country your submission originated from

The Usage Data We Don't Collect

In accordance with our Privacy Policy, any usage data that is not listed above is not stored. When Tokaido uploads this information, our API server will create logs of your IP address (which isn't listed above), but only stored in our web server logs and is not recorded with your installation and project identifiers at any stage.

Who Has Access To View This Data?

Tokaido is built and primarily maintained by Ironstar.

Ironstar team members who work on Tokaido have access to review and create reports on this data, but Tokaido contributors who are not part of the Ironstar team do not have access to view this data.

Will You Sell This Data?

No. We will never sell or license this data. We also will never use this data to market to you (we really can't).

Why Do We Need This Data?

This usage data helps us to identify key trends for Tokaido in the long term. For example with data we can make more intelligent decisions around things like:

• As adoption of PHP 7.3 grows, we can more confidently say when we should roll in PHP 7.4 support.
• How many of our users use XDebug, so we can see if we should devote more time to enhancing our support for it?
• What is the average start up time for a Tokaido project? Are we improving it with time?
• What is the minimum system specs (CPU and memory) we see? Can we make Tokaido more powerful?
• What is the average number of developers working on one project? Should we prioritise collaboration tools?
• What are the most popular Tokaido commands? Should we invest in expanding those?
• Which countries are users from? Should we work add a translation to our docs for primary language spoken there?

Being able to see real data to back up our assumptions on what features we should build or improve helps us to make the right choice.