Common Mistake

To maintain maximum security and avoid accidental data exposure or loss, please avoid the following common mistakes

Not Protecting the Decoy Phrase Generator

Failing to protect the Decoy Phrase Generator on your device is a serious security risk. The Generator should always be protected using at least biometric authentication or a PIN built into the application.

When you create a Mapping Maker project, the system automatically saves your progress to simplify the creation of Decoy Text and Mapping Files. These projects contain your sensitive data. Without proper device-level protection, anyone with access to your device may access your sensitive data.

Not Deleting Mapping Maker Projects After Completion

Leaving Mapping Maker projects on your device after finishing is strongly discouraged, especially when using a non-personal device.

Mapping Maker projects store sensitive information used to reconstruct your original text. If these projects remain on the device, they can become a potential source of data leakage.

Not Clearing Browser Cache When Using a Non-Personal Device

Always clear your browser cache or use Incognito / Private Mode when accessing Permanent Storage on a shared or non-personal device.

Browsers may automatically save usernames, passwords, or session data locally. This can unintentionally expose your Decoy Phrase Permanent Storage credentials to other users of the same device.

Storing Decoy Text and Mapping File in the Same Location

Never store your Decoy Text and Mapping File in the same place.

Both files must be stored in separate locations to avoid a single point of failure. If only one of the files is found, it should remain completely useless.

For example:

• The Decoy Text may be stored as plain text (e.g., notes, social media drafts, or private text storage).

• The Mapping File (JSON format) should be stored securely on a device or protected storage medium.

Not Saving the Mapping File with the .json Extension

Always ensure that your Mapping File is saved with the .json file extension.

If the file name does not end with .json, the Mapping File may not function correctly during recovery.

This commonly happens when users rename the file or change the file name manually in the Save Location dialog, causing the system to fail to recognize the file format.