Privacy
Shareable links carry the thing they share
A result URL that encodes the score or an image ID can be read from history, logs and referrers, so the link itself is data.
A shareable result link is convenient precisely because the address itself contains the content, and that convenience is also the leak.
What ends up in the address bar
Some tools build result pages at a URL that includes a score, a short id tied to your specific image, or both, so that copying the link is enough to reproduce the page for anyone who opens it. That string does not stay confined to the address bar. It is written into browser history on your device, into the server's own access logs on the way to being served, and into the referrer header sent to whatever page you clicked through from, if any script on that page reads it. A link pasted into a chat app, forwarded in an email, or shortened by a link-shortening service passes through at least one more party that now has the same string.
The safer design, and the one worth checking for, uses an opaque, random identifier that reveals nothing on its own - the id is a lookup key, not a description of the content - rather than embedding the score or any recognisable detail directly in the path. An opaque id still identifies the result to anyone holding the link, which is the point of a shareable link, but it does not additionally broadcast what the result was to every system the string happens to pass through.
What to do about it
Treat a result link the same way you would treat the content it points to: do not paste it somewhere public, and be aware that "unlisted" is not the same as "unlinkable" once the URL has been sent anywhere at all. How presigned and signed links work more generally covers the mechanism behind most sharable-link systems, including how long a given link stays valid before it is worth checking. The same string sitting in your own browser history is covered under local traces more broadly, which is the version of this problem that lives entirely on your device rather than in transit.
Rate Cock uses opaque result identifiers rather than encoding the score in the address, which is the safer of the two designs and worth checking for in any tool you use. Whether a measurement log uses the same convention is covered by Measure My Cock's data documentation. A human-reviewed result shared as a link carries the identical exposure once it exists as a URL at all, something Rate Penis's review pages note in their own context. Comparing link designs across rating tools directly is better suited to Penis Rater's tools coverage than to a single mechanism here.