Every execution of the Mantil CLI sends an CliCommand piece of data. It contains metrics about the current Mantil workspace, stage, project and series of Events which are command-specific. Look into the definition of the Event to get the feeling about what data we collect.
For example, for Deploy command, we collect metrics about how many Lambda functions are added, updated and removed during the deploy command execution. Further, we collect durations of the build, upload and update phases. How many bytes were transferred to the S3 bucket and whether it was just function updates or we made some infrastructure changes (new function, API gateway).
Events are collected anonymously with the primary purpose of helping us understand how people use Mantil and allowing us to prioritize fixes and features as well as to catch errors as soon as those happen. We are a small team with the product in early beta and would really appreciate keeping the events collection on. However, if you are working on a super-secret government project, there is an option to disable them by setting MANTIL_NO_EVENTS environment variable. Internally we use it just when running integration tests.
We also pay special attention to the kind of data we are collecting, so, e.g., if you put your AWS credentials into the command line, we recognize that and remove them.