Cronfig is a micro service living in other server than yours. You have to create an account in the service so the service knows it's you who is viewing/creaing/modifying your tasks. The account is as minimal as it can be. All you need is an email address. That's it. Here is how the workflow of creating a new account looks like:
The system you've installed Cronfig plugin into will remember the API key for you. No need to search for the registration email every time.
After you log in you may notice the information about all the limits your account have. The purpose of the limits is that one account won't take all server resources for itself at the expense of other accounts.
If you need Cronfig to work harder for you, please take a look at the paid plans and consider if you could chip in on the project maintanance.
The proces is little bit cumbersome thanks to EU laws. Here is how it currently looks like:
You probably noticed that there is some manual work involved. I'm processing the orders ASAP, but it may happend that I'm out of keyboard. I plan to automate the process but it's at the bottom of Cronfig's road map. I have cooler things to implement for this service.
The Cronfig service intention is NOT to get your personal information. As you could notice, all it needs is your email address so it can contact you when your system is having troubles processing the jobs. But if you are not interested in using Cronfig anymore, there is a link in your registration email which will delete your account, your jobs, your logs from Cronfig.
How can you be sure it does that? Apart from that you won't be able to log in with your API key anymore and your tasks will stop being executed, you can try to register again. It will let you. That's the trick. It won't let you if an account with the same email address exists. Only if it does not.