Terms of Service
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. Future Pass
1.1. Where available on your operating platform:
1.1.1. A user can download the Future Pass App from the official App Store of their device platform, or create and maintain their account at www.futurepass.com.
1.1.2. To the extent permitted by law, we provide no representations or warranties as to the effectiveness of Future Pass in securing your data or preventing cyber-attacks.
1.1.3. A user can select a basic subscription or upgrade to premium for an additional fee.
1.1.4. Payment terms (if any) are set out at the time of download or within the Future Pass App or website.
1.1.5. When a user creates a Future Pass account, you set a password for your account (“account password”).
1.1.6. The account password should be long, strong and unique to your Future Pass account (i.e. not used for other accounts) to ensure that it cannot be easily guessed, or brute forced by a bad actor or cyber-criminal.
1.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.
1.1.8. Our password generator:
188.8.131.52. generates unique, random passwords based on the configured generator settings;
184.108.40.206. is configurable by the user, which may impact the overall quality of the generated password;
220.127.116.11. can generate passwords up to 128 characters in length.
1.1.9. Any password analysis or scoring:
18.104.22.168. is dependent on the accuracy and completeness of the data entered by the user;
22.214.171.124. analyses multiple characteristics of the password; and
126.96.36.199. is provided for informational and guidance purposes only and should not be solely relied upon.
1.1.10. The data that you keep in your secure storage (which may include notes, passwords, two factor codes and 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 further encrypt data before its stored in our cloud.
1.1.11. 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.
1.1.12. A passcode must be set on the device to use the Future Pass App, as this provides a secure environment to store encrypted data.
1.1.13. “Secure storage” is where your saved notes, passwords, cards and two factor codes are encrypted and stored.
1.1.14. We use industry grade encryption to encrypt your data.
1.1.15. On iOS, we make use of the iOS keychain property “kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly”. This is considered one of the most secure properties offered by iOS.
1.1.16. As a result of this setting:
188.8.131.52. Your device must be unlocked for the data to be accessible
184.108.40.206. Only the Future Pass App can access the data
220.127.116.11. The data won’t be backed up to iTunes or iCloud, and cannot be restored on another device (making it extra secure)
1.1.17. If you remove the passcode from your device, the data will be automatically deleted from the device.
2. Phishing Alert
No longer available for new downloads
2.1. Phishing Alert is a web-based browser extension (plugin) that aims to detect, warn and teach you about common ‘phishing’ techniques.
2.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.
2.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 rationale.
2.4. Payment terms (if any) are set out at the time of download.
2.5. There are 4 common types of ‘phishing’ attack methods:
Data URI blocks
Large blocks of space
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.
June 15, 2020