ijEncoder is a free tool entirely written in JavaScript. It runs completely on the client side in the browser and it does not store any data entered by the user.
The application screen consist of two Input/Output text areas that are used to either hold the input for processing or to hold the output of the processing. The top of each of the Input/Output text areas contains Open File, Save File and Compact buttons, and an Auto Encode checkbox. Depending on the version, there is either a series of radio buttons (for a desktop version) or a drop-down list box (for a mobile version) allowing selection of or switching between different content encoding formats. The Open File and Save File buttons allow content of each of the text areas to be either loaded from a disk file or saved to a disk file. Loading the context of a file into the text area by using drag and drop is also supported. The Compact button allows for all white space, including spaces, tabs and new line characters, to be removed from the content in the text area. The Auto Encode checkbox determines whether the content is automatically decoded from the source format and encoded into the target format depicted by the radio button or drop-down list box selection, when the file is either loaded or saved, or when radio buttons or the drop-down list box are used to switch between the encoding formats. If auto encode option is checked, the target format for the file save operation is always binary string (Latin1).
NOTE: Although displaying binary content using Latin1 is possible, there is a potential for data corruption when the displayed binary content is subsequently converted to another format due to the inherent encoding performed by the text area HTML element used to display the content. To avoid this risk please use Hex, Base32, Base64 or Base64URL formats to reliably display and handle binary content.
In the middle of the application screen, there is a Function drop-down list box, which is used to select a content processing function and the two buttons with arrows pointing up (▲) and down (▼), which are used to initiate the processing and place the result into upper or lower text area, respectively. The middle section of the application screen also contains the Compare button which, when pressed, compares the content in the upper and lower text areas, the Clear button which, when preseed, clears the context of all text boxes, and the Help button which, when pressed, displays this set of instructions. The middle section also contains a label that displays the current length of the text area content, in both characters and bytes, when the mouse is hovered over the text area or when the content is being entered via keyboard. This labels also shows the result of the various validation operations as well as the result of the content comparison when Compare button is used.
Depending on the function selected, additional text boxes or drop-down list boxes, which are used to select additional options or input additional parameters for processing, may be presented in the middle section of the application screen. For more details please refer to the Functions section below.
At the bottom of the application screen, there is a copyright statement, which also contains links to the License information and a Privacy Policy. There is also a [change settings] button, which can be used to manage system settings and a [contact us] button which can be used to provide feedback, ask questions or report issues with the ijEncoder Crypto Tool. Depending on the version there could be additional buttons present at the bottom of the application screen, as follows:
The mobile version of the ijEncoder will have a [switch to desktop version] button, which, when pressed, redirects to the desktop version of the application. Desktop version has a user interface which is not responsive but it is easier to use on larger screens (more than 1020 pixels wide).
The desktop version of the ijEncoder will have a [switch to mobile version] button, which, when pressed, redirects to the mobile version of the application. Mobile version has a responsive user interface which is easier to use on smaller screens (less than 1020 pixels wide). This version will also have a [download standalone version] button which allows for the download of the standalone version of the desktop application. The standalone version is a self-contained HTML file that can be run locally in the browser and does not require Internet access.
When [change settings] button is pressed, it displays the Settings pop-up screen which allows for various configuration options to be modified. These include the preffered colour theme, default text encoding format and default binary encoding format. The settings can be saved saved to the browser's local storage and will be automatically applied the next time ijEncoder is used. If Save button on the Settings pop-up screen is pressed the currently selected options will be saved. If the Cancel button is pressed or the Settings screen is closed without saving, the currently selected options will not be saved, and the options will revert back to the previous values.
Colour Theme allows for different colour schemes to be selected in order to customise the appearance of the ijEncoder user interface. The selected colour theme will be applied immediately to show the appearance of the user interface, however, it must be saved in order to take affect after closing the Settings screen.
Default Text Format allows for selection of the data encoding format which will be automatically applied when the operation produces a plain text output but the currently selected data encoding format is more appropriate for binary output. For example, when generating TOTP the output is typically a number of decimal digits, so the applicable result encoding format could be either Latin1 or UTF8.
Default Binary Format allows for selection of the data encoding format which will be automatically applied when the operation produces a binary output but the currently selected data encoding format is more appropriate for text output. For example, when generating SHA-1 the output is typically a binary string, so the applicable result encoding format could be either Hex or Base64.
The summary of the functionality and a description of additional parameters needed by each of the functions are given below.
This function enables generation of the Universaly Unique Identifier (UUID) that conforms to the v4 UUID specification (RFC 4122). The alpha characters in the resulting string representation of the UUID are all encoded using lower case.
If ▼ button is pressed, the function will place the output into the lower text area. If ▲ button is pressed, the function will place the output into the upper text area. The output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area.
This function enables generation of the Universaly Unique Identifier (UUID) that conforms to the v4 UUID specification (RFC 4122). The alpha characters in the resulting string representation of the UUID are all encoded using upper case.
If ▼ button is pressed, the function will place the output into the lower text area. If ▲ button is pressed, the function will place the output into the upper text area. The output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area.
This function enables generation of the pseudo-random binary or alphanumeric string of any choosen length. The parameters are Length and Chars. The Length parameter determines the length of the generated pseudo-random string in bytes or characters. The Chars parameter contains alphabet of UTF-8 encoded characters to choose from. If Chars parameter is empty, the resulting binary string will consist of all the characters in the extended ASCII table (0-255). If Chars parameter is not empty, only the characters specified in the Chars parameter will be used for the generation of the resulting pseudo-random string.
If ▼ button is pressed, the function will place the output into the lower text area. If ▲ button is pressed, the function will place the output into the upper text area. The output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format, if needed.
This function enables generation of the Secure Hash Algorithm 1 (SHA-1) message digest from the input specified in one of the Input/Output text areas.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. The output of this function will always be 160 bits (20 bytes) long. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format.
This function enables generation of the Secure Hash Algorithm 2 SHA-256 message digest from the input specified in one of the Input/Output text areas.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. The output of this function will always be 256 bits (32 bytes) long. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format.
This function enables generation of the Secure Hash Algorithm 2 SHA-384 message digest from the input specified in one of the Input/Output text areas.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. The output of this function will always be 384 bits (48 bytes) long. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format.
This function enables generation of the Secure Hash Algorithm 2 SHA-512 message digest from the input specified in one of the Input/Output text areas.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. The output of this function will always be 512 bits (64 bytes) long. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format.
This function enables key derivation or message digesting using Password Based Key Derivation Function 2 (PBKDF2) algorithm, by applying a pseudo-random function (PRF) such as HMAC to the input, along with the salt value, and by repeating the process many times to produce a derived key or a message digest. This function uses a number of parameters. The Rounds parameter is used to specify a number of times the PRF is applied. The Key Size parameter is used to select the bit length of the output. The Hash parameter is used to specify the PRF hash algorithm to apply. The Salt parameter is used to specify the salt value to use when applying the PRF. The drop-down list box next to the Salt parameter is used to indicate the encoding format of the salt value. Instead of specifying a particular salt value, the SaltGen button can be used to generate pseudo-random salt value. The bit length of the pseudo-random salt value to be generated is specified by the Length parameter.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format.
This function enables use of the Time-Based One Time Password (TOTP) Algorithm specification (RFC 6238) to generate or validate OTP values. This function uses a number of parameters. The Operation parameter is used to specify whether to generate the new OTP value or to validate the existing one. The Hash parameter is used to specify the hash algorithm to apply. The Time Step parameter is used to specify the counter time step in seconds. The Digits parameter is used to specify the number of output digits. The Key parameter is used to specify the HMAC key value to use when applying the hash. The drop-down list box next to the Key parameter is used to indicate the encoding format of the key value. Instead of specifying a particular key value, the KeyGen button can be used to generate pseudo-random key value. The bit length of the pseudo-random key value to be generated is specified by the Length parameter. If the output format selector is depicting an encoding data format that is more suitable for binary output, the function will automatically select the default text format as the output format.
If ▼ button is pressed, the function will place the output into the lower text area. If ▲ button is pressed, the function will place the output into the upper text area. The output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. For validation operation, the OTP value to validate is placed in the input text area and the verification result is displayed in the middle of the application screen as either a green or a red box indicating whether the OTP is valid (green) or not (red). Please note that, in order to account for latency and clock synchronisation drift, in addition to the current time, the validation operation will automatically try one time step window before the current time and the validation will be deemed successful if either of them produces a valid OTP.
This function enables generation of the keyed-Hash Message Authentication Code (HMAC) from the input specified in one of the Input/Output text areas. This function uses two parameters. The Hash parameter is used to specify the hash algorithm to apply. The Key parameter is used to specify the HMAC key value to use when applying the hash. The drop-down list box next to the Key parameter is used to indicate the encoding format of the key value. Instead of specifying a particular key value, the KeyGen button can be used to generate pseudo-random key value. The bit length of the pseudo-random key value to be generated is specified by the Length parameter.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format.
This function enables use of the Advanced Encryption Standard (AES) block cipher to encrypt or decrypt input specified in one of the Input/Output text areas. This function uses a number of parameters. The Operation parameter is used to specify whether the input is to be encrypted or decrypted. The Key parameter is used to specify the AES key value to be used for encryption or decryption operation. The drop-down list box next to the Key parameter is used to indicate the encoding format of the key value. Instead of specifying a particular key value, the KeyGen button can be used to generate pseudo-random values for both Key and IV parameters. The bit length of the pseudo-random key value to be generated is specified by the Length parameter. The bit-length of the IV value generated is always 128 bits (16 bytes). The Padding parameter is used to specify the padding scheme to apply to the plaintext input to the encryption operation. The Mode parameter is used to specify the AES block chaining mode of operation. Please note that some modes of operation do not use padding and if invalid combination of the padding and mode parameter is selected the automatic correction will be applied to one of the parameters. The IV parameter is used to specify the value of the Initialisation Vector (IV). The drop-down list box next to the IV parameter is used to indicate the encoding format of the IV value.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format.
This function enables use of the Rivest-Shamir-Adleman (RSA) public-key cryptosystem to encrypt, decrypt or digitally sign input specified in one of the Input/Output text areas. It could also be used to verify that the value placed in one of the text areas represents a valid digital signature of the message placed in the other text area. This function uses a number of parameters. The Scheme parameter is used to specify the combination of the signing or encryption padding scheme and a hashing algorithm to use. The Operation parameter is used to specify whether the input is to be encrypted, decrypted or signed, or whether the signature validation operation is going to be performed, depending on the scheme selected. If signing scheme is selected, only signing or verification operations are allowed. If encryption scheme is selected only encryption and decryption operations are allowed. The Key Format parameter is used to select the encoding format for the RSA public/private key pair. The RSA Private Key and RSA Public Key parameters are used to specify the values of the private and public keys, respectively. Instead of specifying particular key values, the KeyGen button can be used to generate key pair and populate the values for the RSA Private Key and RSA Public Key parameters. The bit length of the public key modulus to be generated is specified by the Length parameter, while the value of the exponent is always set to "0x01 0x00 0x01" (hexadecimal). The Key Format drop-down box can also be used to convert key pair values from one encoding format to another.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format. For signature verification operation, the digital signature value is placed into the input text area, while the value of the original message is placed in the output text area. The verification result is displayed in the middle of the application screen as either a green or a red box indicating whether the digital signature is valid (green) or not (red).
This function enables use of the Eliptic Curve Cryptosystem (ECC) to digitally sign input specified in one of the Input/Output text areas. It could also be used to verify that the value placed in one of the text areas represents a valid digital signature of the message placed in the other text area. This function uses a number of parameters. The Scheme parameter is used to specify the combination of the signing and hashing algorithms to be used. The Operation parameter is used to specify whether the input is to be signed or whether the signature validation operation is going to be performed. The Key Format parameter is used to select the encoding format for the ECC public/private key pair. The ECC Private Key and ECC Public Key parameters are used to specify the values of the private and public keys, respectively. Instead of specifying particular key values, the KeyGen button can be used to generate key pair and populate the values for the ECC Private Key and ECC Public Key parameters. The type of the eliptic curve to be used for key pair generation is specified by the Curve parameter. The Key Format drop down box can also be used to convert key pair values from one encoding format to another.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. If the output format selector is depicting a format not suitable for binary output, the function will automatically select the default binary format as the output format. For signature verification operation, the digital signature value is placed into the input text area, while the value of the original message is placed in the output text area. The verification result is displayed in the middle of the application screen as either a green or a red box indicating whether the signature is valid (green) or not (red).
These functions enable use of the JSON Web Token (JWT) and JSON Web Signature (JWS) specifications (RFC 7519 and RFC 7515) to sign or verify data input specified in one of the Input/Output text areas. Both JSON Web Token (JWT) and JSON Web Signature (JWS) represent content secured by digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with these specifications are described in the separate JSON Web Algorithms (JWA) specification (RFC 7518). Both of these function use a number of parameters. The Operation parameter is used to specify whether the input is to be signed or verified. The Algorithm parameter is used to select the signature algorithm to be used. Depending on the Algorithm selected, additional attributes are applicable, as follows.
HS* Algorithms: The Key attribute is used to specify the HMAC key that is going to be used for signing. The drop-down list box next to the Key parameter is used to select the encoding format for the key value. Instead of specifying a particular key value, the KeyGen button can be used to generate pseudo-random value for the Key parameter, while the Key Length parameter can be used to specify the bit length of the HMAC key to be generated.
RS* and PS* Algorithms: The Key Format parameter is used to select the encoding format for the RSA public/private key pair. The RSA Private Key and RSA Public Key parameters are used to specify the values of the private and public keys, respectively. Instead of specifying particular key values, the KeyGen button can be used to generate key pair and populate the values for the RSA Private Key and RSA Public Key parameters. The bit length of the public key modulus to be generated is specified by the Length parameter, while the value of the exponent is always set to "0x01 0x00 0x01" (hexadecimal). The Key Format drop-down box can also be used to convert key pair values from one encoding format to another.
ES* Algorithms: The Key Format parameter is used to select the encoding format for the ECC public/private key pair. The ECC Private Key and ECC Public Key parameters are used to specify the values of the private and public keys, respectively. Instead of specifying particular key values, the KeyGen button can be used to generate key pair and populate the values for the ECC Private Key and ECC Public Key parameters. The type of the eliptic curve to be used is automaticaly selected based on the selected Algorithm. The Key Format drop down box can also be used to convert key pair values from one encoding format to another.
The result of the JWS signature will be encoded using JWS compact serialisation, producing a representation of the JWS as a compact, URL-safe string. If the input content is a valid JSON object, the produced JWS structure will represent a JSON Web Token (JWT), as defined by the JWT specification (RFC 7519). The difference between the JWT and JWS function is that JWT function only accepts JSON objects as data input (payload) while the JWS function can be used to sign any data payload.
Both JWT and JWS functions use header parameters to depict certain metadata, such as the type of cryptographic algorithm used to sign the payload, the type of the payload, as well as other metadata specified in the JWT and JWS specifications. The JWT and JWS header parameters can be viewed and edited in a dialog box that is invoked by pressing the JWT Header or JWS Header buttons which are shown on the screen when the relevant function is selected.
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area. For signature verification operation, the digitaly signed JWT or JWS token is placed into the input text area and the verification result is displayed in the middle of the application screen as either a green or a red box indicating whether the signature is valid (green) or not (red).
This function enables use of the JSON Web Encryption (JWE) specification (RFC 7516) to encrypt or decrypt input specified in one of the Input/Output text areas. JSON Web Encryption (JWE) represents encrypted content using JSON-based data structures. Cryptographic algorithms the key management scheme to be used. The Encryption parameter is used to select the authenticated content encryption scheme to be applied to either encrypt or decrypt the input. Depending on the Algorithm selected, additional attributes are applicable, as follows.
PBES2* Algorithms: The Rounds parameter is used to specify the number of times the pseudo random function (PRF) specified as part of the key derivation scheme is to be applied to derive a wrapping key. The Password parameter is used to specify the user supplied password to be used to derive the wrapping key. The Salt Length parameter is used to specify the length of the salt (in bytes) to be randomly generated and used as input into the key derivation processing.
A*KW and A*GCMKW Algorithms: The Key parameter is used to specify the AES wrapping key or key encryption key. The drop-down list box next to the Key parameter is used to select the encoding format of the key value. Instead of specifying a particular key value, the KeyGen button can be used to generate pseudo-random value for the Key parameter. The length of the pseudo-random key value generated is automatically determined based on the Algorithm selected.
RSA* Algorithms: The RSA Private Key and RSA Public Key parameters are used to specify the values of the private and public keys, respectively. Instead of specifying particular key values, the KeyGen button can be used to generate RSA key pair and populate the values for the RSA Private Key and RSA Public Key parameters. The bit length of the public key modulus to be generated and the key format drop-down boxes are located next to the KeyGen button. The value of the exponent is always set to "0x01 0x00 0x01" (hexadecimal). The key format drop-down box can also be used to convert key pair values from one encoding format to another.
The result of the JWE encryption will be encoded using JWE compact serialisation, producing a representation of the JWE as a compact, URL-safe string. If the input content is a valid JSON object, the produced JWE structure will represent a JSON Web Token (JWT), as defined by the JWT specification (RFC 7519).
If ▼ button is pressed, the function will use the input in the upper text area and will place the output into the lower text area. If ▲ button is pressed, the function will use the input in the lower text area and will place the output into the upper text area. The input will be decoded from the content format indicated by the selected radio button or a drop-down list box above the input text area, while the output will be encoded into the content format indicated by the selected radio button or a drop-down list box above the output text area.
All functions are fully supported in Chrome 81 and later versions. The File Save feature is not supported in earlier versions of Chrome nor it is currently supported by any of the other browsers. The rest of the functionality is generally supported on all modern browsers that support SubtleCrypto interface of the Web Crypto API. This includes Chrome 37 and later versions, Firefox 34 and later versions, Opera 24 and later versions and Safari 10.1 or later versions. Edge 12 or later versions only have partial support for Web Crypto API, while IE does not support it at all.
ijEncoder Copyright (c) 2020-2021 by Igor Janicijevic. All rights reserved.
CryptoJS Copyright (c) 2009-2013 by Jeff Mott. All rights reserved.
ijEncoder v2.1
Copyright (c) 2020-2021 by Igor Janicijevic. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Last updated on 2nd of August, 2020.
This Privacy Policy describes the collection and use of information by the standalone ijEncoder Crypto Tool application. Please read this policy before using, or submitting information to this application. By using this application, you signify that you agree to this Privacy Policy.
Data Processing
ijEncoder Crypto Tool is a standalone single page application (SPA) entirely written in JavaScript. All data processing is done on the client side, in the device browser. This application does not record or store any data that is entered, generated or loaded by the users and it does not require access to the Internet in order to work.
Cookies and Browser Data
ijEncoder Crypto Tool does not use cookies or any other tracking technology. The only information stored in the browser local storage are the custom application settings, such as colour theme preference, default data encoding formats, etc.