Sorry to hear that @Marsux!
So what’s important is that your website is using https:// URLs. When you move back to Production, Chrome will show everything as “Secure” as long as your Production environment has a valid SSL certificate Installed.
It only shows “Not Secure” now because the local SSL Certificate added by DevKinsta isn’t trusted by your browser; there’s no issue with the website.
For a brand new website, all you really need to do is go to your WordPress settings and make sure your Home/Site URLs are using https. This will carry over into Production when you replace the .local URL with your Production URL.
So since your Dev environment is based on your Production site, there’s nothing to worry about when it comes to SSL. You can just ignore the red “Not Secure” and do your developing like normal. This is just Chrome being strict with SSL on your MacBook.
Problem would happen if you changed your URLs from https:// to http:// in Development then forgot to change them back before pushing your changes to Production.