A QR code that holds a real secret
Every QR code looks the same to a casual observer. QR Agent makes the difference matter: the payload behind the code is encrypted at rest, never public, and revealed only to the right person at the right time.
// 01 · mission
Turn a public-looking code into a private, encrypted payload
The product exists to close one gap: the assumption that what a QR code points to is accessible to anyone who scans it. That assumption is usually correct — and that is the problem we solve.
QR Agent replaces the raw destination with an opaque URL on our own domain. The content behind that URL is encrypted with AES-256-GCM under a per-tenant key, wrapped by a hardware-backed KMS master key. A viewer must be authenticated and authorized, or present a valid access link. There is no way to read the payload without clearing one of those gates.
// 02 · thesis
Encrypted, then revealed
// encrypted state
What the world sees
A scannable QR code. An opaque URL with no visible connection to the content it protects. A gate page that reveals nothing about what is behind it.
// revealed state
What the right person sees
The decrypted payload — a URL, a note, a file, a contact card — delivered immediately, with full audit trail and revocable access. The experience is seamless; the protection is not optional.
// 03 · principles
What guides every decision
Fail closed, not open
When in doubt, the product reveals nothing. A gate page shows no content, no hints, no clues about what is behind it. Exposure is the failure mode we optimize against.
Encryption is the foundation
Access controls are layered on top of encryption, not instead of it. Even if access logic had a flaw, the underlying ciphertext remains useless without the key hierarchy.
Minimal surface, minimal exposure
The system stores only what it needs. IPs are HMAC-hashed, never raw. Email addresses are encrypted at rest. Access link IDs are hashed in the database. Less stored means less exposed.
Designed for teams, built for trust
Every tenant has isolated keys. One tenant's compromise cannot affect another. Roles limit what each user can create, view, or share. The access model is auditable by design.
// 04 · what we do not claim
Honest about what we are
QR Agent is a product with a strong encryption model, not a certified compliance framework. We do not hold SOC 2 or HIPAA certifications at this time. We do not claim zero-knowledge or end-to-end encryption in the current release — the server holds and manages keys on behalf of tenants, which is the trade-off that makes seamless sharing possible.
What we do claim: every payload is encrypted at rest with AES-256-GCM under hardware-backed keys, plaintext keys never touch persistent storage, tenant data is isolated by key and by row, and the access model is stateful and revocable. Those claims are backed by the design, the code, and the architecture documentation.