Is this legal? Deactivated one NPC, now part of a new NPC.

[GeekyPenguin]

Originally Posted by AChiOhSnap

Question...

Why wouldn't a database that simply had full names, birthdates, and affiliations not work? Even if a woman has a relatively common name, here's how it would work.

Jessica Marie Smith was a member of ABC at East Coast University. She transfers to West Coast University, goes through recruitment, and receives a bid to XYZ.

Especially since she's a transfer, someone from XYZ would check the national NPC database. Forty hits for Jessica Marie Smith come up, but only two initiated at ECU. One Jessica was born 7/8/1971 -- so it's obviously not her -- and another Jessica was born 2/27/1988. Voila, a name and birthday match. A quick phone call to the chapter at ECU or ABC headquarters confirms this girl's identity.

I don't know about everyone else, but I had to verify my identity (via driver's license or school ID which had my legal name and birthday on it) before I could sign up for recruitment because of age restrictions.

I really think this would work, and it would be as simple as a sorority updating their own member databases. It seems relatively easy enough. I'm sure mistakes would be made and if a girl changed her legal name from the time she was in one GLO before she rushed another it might make things sticky, but that seems unlikely. If a PNM is so psycho that she'd take great measures to hide her legal identity in order to cheat the system, my guess is she wouldn't last very long in a sorority anyway.

I think this would be a lot more efficient to search and not run the risks of giving out an SSN.