Skip to main content

Identity Theft and You

I recently was forwarded an email about Google's "scary" (for some) feature of reverse phone searching. You can read more about the email at Snopes.com.

Anyway, I was bothered enough by the false sense of security a FUD email like this provides for those who aren't as wise to today's Internet issues that I was forced to write the following response for my family to read as a counterpoint.

I receive many forwarded emails, but I award few with more than a passing glance. This one is so misguided though, I felt it deserved a response at least to those I know and care about.

Phone numbers and addresses aren't private information and shouldn't be or they betray the very nature of what they are, location devices. Reverse searching for a person or address based on a phone number has been available for a very long time on many websites, the most well known, for me at least, being http://anywho.com.

The advice the original email provided will lead many who read it into a false sense of security while making things harder only for legitimate people looking to contact them. Removing yourself from Google's listing makes it not only harder for the "bad" people to find you but also your friends, family, and business associates. Someone looking to steal your identity or find out information about you has many resources beyond Google in this era of the Information Age.

If you are truly looking to protect yourself from identity theft there are more effective ways:


  1. Create a Google Search Alert for your social security number and/or credit card numbers. This will notify you via email if Google finds one of these numbers on the Internet. That way, if one of these important numbers have been stolen and appears online, you'll be one of the first to know.

  2. Check your credit report annually for free at http://www.annualcreditreport.com. Review it to make sure no one has stolen your identity

    • NOTE: Beware of freecreditreport.com. It is a well-advertised scam.

  3. Place a fraud alert or credit freeze on your credit report. Its an extreme measure, but it then allows only you can get credit in your name using a private PIN.

  4. NEVER use a debit card or personal checks. They are linked directly to your rightfully earned money with no safeguard and provide you no recourse if someone fraudulently takes money from your bank account. A credit card provides many protections a debit card does not.

  5. Ask your credit card company if they provide single-use credit card numbers. Many, such as Discover, provide an online utility to generate a new credit card number to use for each of your online purchases. This will protect you because if that single-use number is stolen it is worthless.


Find out even more ways to protect yourself: http://www.google.com/search?q=protect+identity+theft.

Now I, Brian Jackson, personally wrote every word of this email and I hope THIS is what you pass on to friends and family!
Labels:

Comments

Post a Comment

Popular posts from this blog

3D Photo Viewer for Looking Glass

The Looking Glass I created my first Chrome extension, which is now live on the Chrome Web Store ! It's built for the Looking Glass , a holographic display that let's you view three-dimensional objects without glasses. I've also opened the source to the extension on GitHub. The Chrome extension allows you to view Facebook's "3D Photos", a feature they added in 2018 for displaying photos that include a depth map like those from phones with dual cameras, such as Apple's "Portrait Mode". Getting Started To use the extension, connect your Looking Glass to your computer, navigate to Facebook and open the viewer from the extension's popup menu. This will open a browser window on the Looking Glass display's screen in fullscreen mode. Opening the Viewer Once the viewer is open, the extension watches for any 3D Photo files being downloaded, so browse around Facebook looking for 3D Photos.  I recommend some of the Facebook groups de...
Post a Comment
Read more

Simplifying logging with Maven and SLF4J (Part 2)

So in my  previous post  I explained how to simplify your logging with Maven and SLF4J. If you haven't read it yet, please do before reading more.  Since then I've discovered an easier and cleaner way to remove the secondary frameworks from your Maven dependency tree. Here's a revised overview of the steps: Decided which logging framework will be your primary, aka who will actually write to your log file. Define the dependency scope of all the secondary frameworks to be ' provided '. Configure your project to depend on drop-in replacements of each secondary framework from SLF4J. Define secondary frameworks as provided Use the dependencyManagement section for this. Its used when you might have a dependency transitively. Add dependency on SLF4J Add the following to your pom.xml Conclusion So now in only 3 steps you can redirect all your logging to your primary logging framework without changing a line of code!
Post a Comment
Read more

First Impressions from NoSQL Live

Today I drove up to Boston for the day to attend NoSQL Live . My experience so far within the NoSQL community has been limited to what we've built in-house at Disney and ESPN over the past decade to solve our scaling issues, more recently has been ESPN's use of Websphere eXtreme Scale , and the very latest has been my own experimentation with HBase which hasn't gotten much further than setting up a four node cluster. I've read a little about Cassandra, memcached, Tokyo Cabinet and that's about it. So before the sandman wipes away most of my first impressions of the technologies discussed today, I wanted to record my thoughts for posterity or, at the very least, tomorrow. Cassandra Cassandra seems to be the hottest NoSQL solution this month with press about both Twitter and Digg running implementations. My impression, I'm wary of "eventual consistency". I don't feel I understand the risk and ramifications well enough to design a system properly...
4 comments
Read more