Service Descriptions

Terms of Service | Service Descriptions | Privacy Policy

This Service Description sets out the attributes of some of the Services we may provide you from time to time. In the event of inconsistency, our Terms of Service take priority over the contents of this Service Description.

1. Phishing Alert


1.1. Phishing Alert is a web-based browser extension (plugin) that aims to detect, warn and teach you about common ‘phishing’ techniques.

1.2. To the extent permitted by law, we provide no representations of warranties as to the effectiveness of Phishing Alert in detecting common types of ‘phishing’ attacks.

1.3. The User installs the plugin from the official browser add-on sites. It runs at the top of their screen, and if it detects 1 of 4 types of ‘phishing’ techniques, it will redirect them to a “safe” page where it alerts them to the possible phishing attack, and breaks down the reasoning.

1.4. Payment terms (if any) are set out at the time of download.

1.5. There are 4 common types of ‘phishing’ attacks:

  • Data URI blocks

  • Script tags

  • HTML Tags

  • Large blocks of space

1.6. At the date of this version, Phishing Alert is available for the following web browsers:

  • Google Chrome;

2. Future Pass


2.1. Where available on your operating platform:

2.1.1. A user can download the Future Pass App from the Apple App Store, or create and maintain their account at www.futurepass.com

2.1.2. To the extent permitted by law, we provide no representations or warranties as to the effectiveness of Future Pass in preventing cyber-attacks.

2.1.3. A user can select a basic subscription or upgrade to premium for an additional fee.

2.1.4. Payment terms (if any) are set out at the time of download or within the Future Pass App or website.

2.1.5. When a user creates a Future Pass account, you set a password for your account (“account password”).

2.1.6. The account password should be long and strong, to ensure that it cannot be easily guessed or brute forced by a cyber-criminal.

2.1.7. It is critical that you do not share your account password with anyone, including us, as the encryption process we use to keep your data safe in-part depends on only you knowing your account password.

2.1.8. Our password generator creates complex and long passwords. Although safer and less likely to get hacked than a simple (or reused) password, we make no guarantees of the security of those passwords.

2.1.9. The data that you keep in your secure storage (including passwords, two factor codes and credit card numbers) is encrypted and decrypted on your device. If we need to transmit your encrypted storage data (such as between devices, or to the cloud), we encrypt your data a second time locally on your device before transmission, to further ensure that your data remains as secure as possible. We then further encrypt data when stored in our cloud.

2.1.10. We do not store or transmit your account password in its original plain text form. We instead use techniques such as ‘one way’ derived hashes.

2.1.11. A passcode must be set on the device to use the Future Pass App, as this provides a secure environment to store encrypted data.

2.1.12. “Secure storage” is where your saved passwords, credit cards and two factor codes are stored.

2.1.13. We use industry grade encryption to encrypt your data.

2.1.14. On iOS, we store your important data in the iOS keychain with the “kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly” property enabled. This is considered one of the most secure properties offered by iOS.

2.1.15. As a result of this setting:

2.1.15.1. Your device must be unlocked for the data to be accessible

2.1.15.2. Only the Future Pass App can access the data

2.1.15.3. The data won’t be backed up to iTunes or iCloud, and cannot be restored on another device (making it extra secure)

2.1.16. If you remove the passcode from your device, the data will be automatically deleted from the device.

2.1.17. Under these circumstances:

2.1.17.1. In the near future, all password hashes and encryption keys will be encrypted using private keys stored on the iOS Secure Enclave (p.7) using the “kSecAttrTokenIDSecureEnclave” property.

2.1.17.2. The Secure Enclave is available on iPhone 5s and newer, and is responsible for processing fingerprint data from the TouchID sensor, and other associated cryptographic operations.

3. Additions to this Service Description


If we decide to change this Service Description, we will post the changes on our website. Please refer back to this Service Description to review any amendments.

Page last updated March 1, 2019