Short answer: usually not, if the analytics tool doesn't set cookies or use local storage to identify you. Most of the time a cookie banner isn't legally required by "analytics" as a category, it's required by what a specific tool does: setting a persistent identifier on the visitor's device to track them across visits or sites.
What actually triggers the requirement
Under GDPR and the ePrivacy Directive, you generally need consent before storing anything non-essential on a visitor's device, or before doing anything equivalent to tracking them, such as fingerprinting. Classic tools like Google Analytics store a client ID in a cookie that persists across sessions, and can be combined with other Google data, which is exactly the kind of thing that requires consent first.
How SimpleStat is different
SimpleStat's tracking snippet doesn't set any cookies or use local storage to identify visitors across sessions. It doesn't fingerprint devices either. What it does record: a page path, a coarse location (country/region/city, derived from the IP address without storing the IP address itself), browser/OS/device type, and a referrer, none of it tied to a persistent cross-visit identifier for that visitor.
The one exception is a first-party cookie used to tell repeat visits within the same session apart from new ones, it doesn't carry any personal information and isn't used to track anyone across different websites.
So do you need a banner?
For most sites using SimpleStat, no, specifically because of it, but this isn't legal advice, and your own site might have other reasons to need one (other tools, forms, ads). If you're not sure, check with whoever handles compliance for your business, this post just explains what SimpleStat itself does and doesn't do.
Curious how the tracking snippet actually works? See the installation guide.