on my site im liable, as on the older dsb script its stated the username will not be shown, and is used for billing etc.., but now if i go live with the new etano, im uncovering their real identity, this i can be liable for any damages for the client caused, and against the data protection act
I run a swingers site simular, my clients like to be cloaked with their nicknames, imagine the legal side when I display their real names........
When the migration script aquires the names, i assume it isnt rocket science to choose a different field for which the names are held, as this is how the names are migrated in the first place, the names are unique and the nicknames are unique
Id rather the site requires the nicknames as opposed to realnames to now log in, this can be displayed for people to take notice of on the sign in page
I could go throught the database and manually replace col 1 name with col 2 (nickname) this should work, shouldnt it
All I can say, any one in this simular situation is not to show the real names.... as you could be liable, ive had this in the past