What is this gitlab joltup key cache fail error all about?

[Dave Coder]

I just installed SourceTree 3.3.9 for Windows 10, I don't use GitLab, I haven't heard of joltup (is this a jolt.com thing?), I have no idea why SourceTree's trying to hit a gitlab.joltup.com server, why it thinks I need to cache the key, and why I need a pop-up interrupting everything about something I'm not using.

Is this default SourceTree behavior, or just something in my repo? I'm just working with a new Laravel and Node repo.