It's possible to have data races if you ignore the language conventions[1]. But even then, Go has provided an effective data race detection tool since 1.1: https://go.dev/blog/race-detector
I've been using Go on a large codebase for a number of years, and I haven't found data races to be a problem in practice.
That's fantastic, good job! "Just be good enough at your job" is why C++ is fully concurrency- and memory safe, too. But, you know, its not, that's not how juniors use it, and boy do they write a lot of codebases I end up maintaining.