Encrypt via QR code!
QRS proposes open software infrastructure for building E2EE applications that encrypt data on the client-side without using passwords. Instead of entering passwords, users scan QR code displayed by the E2EE application. QR code opens a "door" into encrypted tunnel between E2EE application and QRS mobile app. QRS mobile app uses its Master Key (KEK) to WRAP / UNWRAP data keys (DEKs) used by E2EE application to encrypt data. This works with terminal / command line as well as GUI - please see the demo video below:
How does it work - Part 1
How does it work - Part 2
Why use QRS encryption?
Easier than passwords
Scanning QR codes is easier compared to entering passwords.
More secure than passwords
QRS uses randomly generated AES 256-bit KEK and DEK keys that cannot be brute-forced. Other encryption software often use keys derived from passwords that would usually have LOWER ENTROPY and can be brute-forced if password is weak. Even the strongest of manually managed passwords would have MUCH LESS entropy compared to random keys used in QRS.
No risk of keyloggers
Keyloggers may steal your passwords while being typed. With QRS, keyloggers are of less concern b/c nothing is typed while unlocking (decrypting) your data.
Quantum Safe AES-256
QRS uses AES encryption with 256 bit keys, which is considered quantum safe.
Authenticated Encryption with Associated Data (AEAD)
QRS uses AES in GCM mode which provides the ability to cryptographically bind the metadata (Associated Data) describing the encrypted data. For example, Password Manager application might want to use 'website' and 'username' as Associated Data (AD) attributes. QRS uses AEAD extensively, for example, Client Application Name is a mandatory AD attribute. QRS also provides API for Client Applications to define custom AD attributes to be attached to wrapped DEK keys. Before unwrapping the DEK key, QRS application displays AD attributes to user and waits until user confirms the operation.
Flexible API to support future Client Applications
QRS is intended to be flexible to support existing and also not yet developed Client Applications. The goal is to completely avoid changes in QRS mobile app when developing new Client Applications.
Free and Open Source
QRS is Free and Open Source software with a permissive MIT licence.
Cross-Platform
No more platform lock-in! QRS uses modern cross-platform C#/.NET stack and so it runs on IOS, Android, Windows, Mac OS, and Linux. Switching mobile platforms by Backing up your Master Key on Android and restoring it on IOS, or vice-versa, is super easy!
No cloud accounts
Having Apple, Google or Microsoft account is NOT required to use QRS. On Android, we completely disable cloud backup. On IOS, KeyChain is used to securely store your Master Key on device. With that said, the officialy supported way to backup your Master Key(s) is to create a password-encrypted Backup Image via QRS app. This gives you 100% privacy, vendor independence, and ultimate control over your encryption keys. We will also publish QRS source code so you will be able to build QRS apps from source and run it on your platform of choice.
Nothing is stored server-side
There is NO risk of server-side data loss. However, you absolutely MUST backup your randomly generated Master Key (KEK) or you will lose your encrypted data on QRS app re-install or mobile OS update!
Privacy
QRS mobile app does not collect any PII (personally identifying information) about you. However, if you use public Tunnel Servers provided by QRID.COM, the servers will do some basic logging expected from HTTPS server, including logging of your IP address. Also, it would log an Application Name and Application InstanceId which is a unique anonymous randomly generated identifier that QRS app creates and stores on your device. InsanceId is only available to QRS app and it is not available to other apps on your device. InsanceId and Application Name are included to every request that is being sent to the Tunnel Server. We use these data to monitor service stability and performance, to rate-limit API requests, and to derive basic retention metrics used to improve the service. The web server logs are stored for the period of 90 days. The InstanceId and derived metrics are stored for the period of 2 years after last use.
What software is using QRS encryption?
Cross-platform Password Manager (Windows, Mac OS, Linux). To try a BETA version, please download a ZIP file below, extract all content, then run the EXE file (QrsPasswordManager.exe)
Command Line utility that uses encrypted YAML config to set environment variables and then launch the process. Great for running CI/CD scripts, loading encrypted SSH keys into SSH Agent, running AWS CLI, Azure CLI, and many other admin scripts that take sensitive parameters via environment variables
Windows Application to encrypt arbitrary files
Cross-Platform Notes Application (Windows, Mac OS, Linux) where notes are encrypted with QRS
QRS encryption could be integrated into any web, mobile, desktop or command line
application. Learn more at DEVELOPER.QRID.COM (coming soon)
Free QRS mobile app is required
in order to use QRS encryption
in order to use QRS encryption
Early Access - download and install APK file on Android:
1) In your Android Settings, search for "unknown" keyword to find something like "Install unknown apps" setting
2) Allow installation of "Unknown Apps" from "Chrome" and then download the APK file using the link below
3) Ignore all "Blocked App" warnings and look for an option to "Install Anyways"
To get notified about our launch
please send us EMAIL to
please send us EMAIL to