Agreed. The rational was not to "pollute" Spotify with a bunch of public Trackafind playlists. But I've received this feedback elsewhere. Plan is to add flexibility to make the playlist private/public cause I've received feedback for wanting that ability. Alternatively, drop the private scope altogether and have all playlists public by default.

Edit: it needs the create, edit permissions to create the Trackafind playlist and add tracks to it. The follow just comes as part of that auth scope.