In our commitment to ensuring user privacy and data protection, we have implemented measures to prevent the direct storage of email addresses. Instead, we utilise a cryptographic approach, hashing, to represent email addresses in our system. This article delves into the specifics of this method and its implications for data privacy.
How we handle email addresses
No raw storage
We never store the raw or plaintext version of the email address. This is a proactive measure to prevent unintended access or breaches that could compromise personal information.Hashing instead of storing
Whenever we receive an email address, it's transformed into a hashed format. Hashing converts data (in this case, the email address) into a fixed-size series of numbers and letters. This resulting "hash" serves as a unique identifier for the email in our system.Irreversibility of hash
A fundamental property of the hashing method we use is its irreversibility. This means that once an email address is converted into its hashed form, it cannot be transformed back into its original form. The technology ensures that even we can't retrieve or view the original email address from its hash.
Why this matters
Enhanced privacy
By not storing raw email addresses and only using hashes, we provide an added layer of protection to user data. In the unlikely event of a data breach, malicious actors won't find usable email addresses.Identification purposes
The hash serves a critical function in our system β identification. Though we cannot see or retrieve the original email address, the unique hash allows us to recognise and differentiate users.Compliance with best practice
Using hashes for email addresses aligns with best practices for data handling and privacy protection in the technology sector. This method reduces potential risks while still allowing us to perform necessary operations.
We remain committed to ensuring the highest standards of privacy and security for our users. If you have any further questions, please get in touch with our support team.