*Caution* problem with past PINs still being active

As a retired Teradata DBA, I know that timely modification of the database is essential in something like this.

On a discrepancy that big, I would have taken a screen shot of my app as proof.  I would want to be able to provide non company provided proof of the situation.  No matter how well intentioned and honest a company is, bad, dumb stuff like this CAN happen.  

• Those who don't know how to take a screen shot on their phone should take the time to learn how, and practice a couple of times.  On my Motorola Z2 Play, its as easy as saying, "OK Google, take a screen shot."

 

As R Reagan once said, "Trust, but verify".

But it does sound as if deactivation of PIN numbers might be some sort of manual entry at the SimpliSafe end.  Regardless of how deactivated PIN numbers are removed from the database, I would suggest that SS send an email when a deactivated PIN number is truly deactivated.  And, as a business level customer, I would not consider a PIN number inactive until I got that email.  And if I didn't get that email in a timely manner, I would contact SimpliSafe.  

I don't think SimpliSafe should try to market to businesses if they can't provide a fast turn around on something like this. Sorry SS, I like your product, but this is just common sense.

@glenbarrington, my nod to you as a professional propeller head expert (term of respect that I always extended to our DBAs, even when we went to our monthly bad movie of the month). Just wanted to add on my Galaxy S7 and many other phones you can also set it up to capture the screen very easily by swiping the side of your hand over the screen.  BTW were you a physical or logical DBA? (Just read my post and realized I have just set my self up for bad humor from drunkpenguin).