Originally Posted by
bob12403
My wife and I each had a 2500 mile AA award pending from redemptions on 12/30. Today we each received an email from LSC stating the following:
Dear Live Search Club Participant,
You are receiving this communication from Live Search Club because you recently placed a duplicate prize order with Live Search Club. As noted in our Terms and Conditions, prizes are limited to one of each prize per household. Your duplicate order for 2500 Frequent Flyer Miles has been cancelled and 4,300 tickets have been re-issued to the account from which the duplicate prize order was placed. We are sending this email to let you know that tickets have been re-issued to your account and are ready for you to redeem for another prize of your choice in our Prize Mall.
Originally Posted by
bob12403
Yes, we each had 2500 mile awards prior to 12/19. No, we did not have any other 2500 mile awards after 12/19, although our daughter did have one redemption on 12/31 from DL that posted last week. So I can't definitively address the question of whether or not they are looking back before 12/19, or if we were disqualified due to our daughter's redemption. Knowing that she had 2500 mile redemptions prior to 12/19 as well, I will guess that it was her new award that caused our redemptions to be rejected. In either case, it looks like the restrictions are now in place and being enforced. BTW, the tickets were returned to our accounts.
Interesting... But, the question remains how is LSC figuring out the "same household" issue?
The LSC/Live ID registration processes themselves don't require any street address information, so it can't be that. And, there's nothing to send to a physical address so LSC doesn't ask you to provide that when you request a FF mileage award redemption.
Yes, tracking IP addresses is a possibility, but on the other hand as another poster pointed out, sharing computer access is common especially at public facilities like libraries, etc. so that wouldn't make the tracking process foolproof.
I kinda doubt the identification of duplicate HH requests is happening at the LSC/redemption request level. If so, "offenders" would be getting a "reject" notice at the redemption request stage. They're not -- they're getting notified farther down the line, and then their miles are being redposited.
Which leads me to believe that something is going on at the airline or AI level....
Due to privacy policies, it seems unlikely that the airlines themselves would be sharing FF account holder's details like street address with AI or LSC.
However, maybe they are not *sharing* the info per se, but it seems like it would be a relatively easy process for them to go through an run a search to find FF accounts with the same mailing address and identify these "duplicates" in list form simply by FF acount number.
This list could easily be sent to AI or where they could run a routine to see if any of these "duplicate" FF accounts matched up with FF account numbers of redemptions waiting for processing. If so, no go...
The only thing that puzzles me is the fact that it appears they are able to discern the existence of more than one FF account per household ACROSS airline carriers.
The only way I can figure out *that* may be happening is FF member address information IS being shared with a third party -- most likely AI. Without combing through the privacy policies of all involved, I don't know whether that's possible or advisable -- doesn't seem like it would be.
However, perhaps there are two levels of monitoring going on...
1) IP addresses *are* being monitored. Any time there's a duplicate redemption coming from the same IP address, then the investigation is taken to "Level Two."
2) At that point, suspect FF account numbers are sent to the airline/s to verify whether the account holders reside at the same address. If they do, again, no go...
I guess we could test that theory easily by seeing if anyone here has household members using one IP address, but are depositing miles into FF accounts that are NOT registered at the same physical address and had no problems.
Any takers?
One thing for sure is that LSC/AI/whomever has to be doing a lot more monitoring than in the past. There's your answer why suddenly the timeline for turning around redemption requests has been extended to 60-75 days...
Best,
TMichaels