Hi Sean,
I suspect you are using an auto-numbered value in Medal right? So by exposing the number you are actually exposing all the other medals as well - because I can try ?Medal=6284, ?Medal=6285 and so on.
This is a common flaw in database design which is especially poor under auto-inc, and has lead to some rather high-profile data attacks over the years.
Also passing unique ID's on the command line like this can lead to data leakage, because this request is stored in logs etc. So using "real" values is problematic.
To avoid all this unpleasantness NetTalk employs a system which translates these "real values" into temporary (session based) random values. Using this approach users are not able to guess "other correct values" and are not able to re-use the link in another session, or after the current session expires.
A discussion of this approach, and how to pass parameters safely, is described here;
https://www.capesoft.com/docs/NetTalk11/NetTalkWebFAQ.htm#W4Of course with this the URL is still visible, just meaningless to the user, and can't be abused. Even if we make the URL invisible though, you still want to use this approach because this is not the only place this value is visible. It may be the most obvious place, but simply moving the problem somewhere else is not helpful. So first correct this, then if we need to we can look at removing it from the URL.
cheers
Bruce