• Home
  • Privacy

Blog

The Difference Between Hashing and Encryption

Here at BIGtoken we take data privacy and security seriously and we want our BIG community to fully understand how it works. To keep data secure in our system, we use two security techniques: end-to-end encryption and hashing. Let’s break down the differences between each technique and explain how we keep your data safe!

 

How data encryption works

Encrypting a piece of information, such as a name, turns it into a random string of characters that makes it unreadable without a special key. Those with the right key can decrypt the data to view is as the original text. At BIGtoken we use an deeper security method called two-level encryption, also called end-to-end encryption. This means the entire database is encrypted AND each individual piece of data is encrypted. Most databases only encrypt on the database level, which means a hacker would only need one key to access everything.

How hashing works

Rather than converting data into a random string of characters, this method uses a hashing algorithm to turn text into numbers. The more complicated the algorithm, the harder it is to turn a given string of numbers, or hash, back into its original form. This technique is great for storing passwords and private information, as raw data is never transmitted during the process. And even if hackers got access to the raw data somehow, it would take ages to crack the code. At BIGtoken, we use this technique when a user who has deleted their account wants to reactivate it. Email addresses stay hashed in our system so they can be stored anonymously and then pulled back into circulation when you want to reactivate.

For advanced protection, we use end-to-end encryption across the board, and a hashing algorithm for special needs. That way your private information can be transmitted from you, to us, to marketers in a completely secure transaction.

 

 

Was this insight helpful? Leave us a comment below.

 

Leave a Reply

Your email address will not be published. Required fields are marked *