Yes, there is that nuance, but:
1. It is displayed to you and you alone
2. On receiving the data of your IP, at least here they warn you about it, unlike other resources 
3. find in this and a good component - it can be used to check that your account is not used by someone else, respectively from another IP, because all your posts are labeled for you IP from which the post is made 
Thank you, I have found it. With the IP address we only think it is a privacy problem because the authorities can find out every IP or ask if they are stored, especially in the mixer area.
Now we will check whether the information is stored inside the service or not. Now I’m using a VPN, with an address in a completely different country and even a different continent
If my previous post and this one have 2 different IPs, that means they are stored and tied to each individual post... Now I’ll publish it and write down which ones IPs are displayed for me...
UPD.
The previous post shows IP 46.1**.*.*
The current post does not show any IP address...
In total, I can assume that there is a certain address that can be stored as a “base” address for the user. And if he comes from another IP, then it is not displayed, informing that this is a “different IP”.
In a word - it is better to seek advice from the owners of the resource
From our point of view, every IP is stored by post, not just a base one.
It all depends on the implementation.
There are at least 2 variants:
1. store the basic one, store all other ones. Compare - does not match - somehow display information about this fact
2. Store the base, dynamically compare with the current one - does not match - somehow display information about this fact.
Globally, of course, storing the IP is not the best solution from the point of view of user privacy.... If you just need to check whether the user's IP is familiar or suspicious, you can store a hash of the IP + salt, and then the user's privacy is protected, and you can identify the "unfamiliar" IP.