Another Major Leap in Security

Starting with unifiedKeys 1.4, we have added public IP address identification within tokenKey. This further increases the security of tokenKey. With this kind of data, we uphold ourselves to higher data privacy than ever before.

First off, including your public (by public, we mean IP addresses that almost every website in the world stores and accesses as soon as you load the website) IP address is 100% optional. You will never be forced to include your public IP address if you are not comfortable. This will not hinder your experience with tokenKey.

tokenKey only uses your IP address to get the closest or exact city you are in to circumvent rolling or dynamic IP address from affecting the decryption of tokenKey.

We also do not compute your IP address, we use a third-party API (here is the direct URL, the same one that tokenKey uses: https://api.ipify.org?ipv=4). We do not store your tokenKey on other servers; everything is computed on device, and requires and internet connection if you choose to include your IP address.

If you are concerned about data privacy, you can look at the official IPify website here: https://www.ipify.org/

Furthermore, we ensure that all communication with the third-party API is secure and encrypted, using HTTPS, protecting your data from potential interception. This means that even if you opt to include your IP address, it remains safeguarded through secure transmission channels.

We believe in transparency and user control, which is why we provide you an option. Users can easily toggle the IP address inclusion feature on or off, and we offer clear explanations of the implications and benefits of including your public IP address.

In summary, the introduction of public IP address identification in unifiedKeys 1.4 is designed to enhance security while maintaining user privacy and control. We are dedicated to providing a secure, transparent, and user-friendly experience.

If you do choose to include your IP address and you aren't connected to the internet, tokenKey will treat the key as if you didn't consent to allowing your IP address to be used, leaving the section 'blank' in the key.

If an IP address is included in the tokenKey, but you aren't connected to the internet, the decoding will fail, and you will encounter an error.