Your data. Your device. Your rules.
Everything stays in your own folder. No accounts. No cloud. No tracking.
Nothing is stored by us — not your keys, not your DID. They are rebuilt from your passkey each time. Ways to reach you come after, in Settings.
What Q is
Q keeps the proof of what happened.
Whenever something happens between people — a lesson, a job, a payment, joining a club — Q writes a receipt. Both sides sign it. Both sides keep it. Nobody in the middle holds your data, and nobody can quietly change the record.
Two people. Two computers.
Ana and Ben each have Q, and their own folder. There is nothing in the middle.
Something happens.
Ana teaches Ben a lesson — or does a job, or pays him back.
Q writes a receipt.
What happened, and when — signed with Ana’s passkey.
Ben agrees.
He checks it and signs too. Now it is both of theirs.
Each keeps a copy.
The same receipt, in Ana’s folder and in Ben’s. No server holds it.
Proof that holds.
Years later, either can show it. Change one word and the signatures no longer match.
What people use it for
-
Proof of learning
Courses and study, recorded as you go — yours to show, not locked in someone else’s system.
-
Clubs & federations
Joining, consent and membership, run fairly — from a camping club to a co-op.
-
Your own website
Write and publish pages from
Q. Every release is a signed receipt. -
Work & payments
Jobs done, agreements made, money moved — evidence both sides hold.
-
Community festivals
Volunteers, stallholders and tickets, with a clear record for everyone involved.
-
Calls & messages
Talk person to person. A receipt keeps the facts — who, when, how long — never what was said.
How secure is this?
Q is built on open, published standards — the ones the security world checks its own work against. In plain words:
-
No password to steal.
Your passkey never leaves your device, and it only works on this site — a lookalike site gets nothing.
- FIDO2The FIDO Alliance’s standard for signing in without a password, using a key kept on your own device. Passkeys are FIDO2.Find out more
- W3C WebAuthnThe W3C web standard that lets a browser make and use passkeys. The browser only lets a passkey sign in to the site it was made for.Find out more
- ICANN domainWeb addresses are allocated through the system ICANN coordinates.Find out moreQ’s passkeys belong to inqbeta.com, which a lookalike site cannot own.
-
-
Nothing stored by us.
Your keys are rebuilt on your device from your passkey, every time. There is no copy of them anywhere else.
- WebAuthn PRFAn extension to WebAuthn: the passkey hands the page a secret for this site alone, without revealing itself.Find out moreQ builds your keys from it.
- HKDF-SHA-256 · RFC 5869An IETF standard (RFC 5869) for turning one secret into separate keys. Each ofFind out moreQ’s keys is derived this way, so one never gives another away.
-
-
Your identity is yours.
A decentralised identifier made from your own key — not an account on our server.
- W3C DIDDecentralised Identifiers: a W3C standard for identifiers you make and control yourself, with no central register.Find out more
- did:keyThe simplest kind of DID: the identifier is the public key itself, so anyone can check a signature without looking anything up.Find out more
- Ed25519 · RFC 8032A widely used digital-signature scheme (RFC 8032).Find out moreQ signs every receipt with it.
-
-
Locked before it leaves.
Every file is encrypted on your device before it is synced or backed up.
- AES-256-GCMThe encryption that locks your files: AES with a 256-bit key, in GCM mode, which also detects any tampering.Find out more
- NIST SP 800-38DThe US National Institute of Standards and Technology’s specification of GCM, the modeFind out moreQ uses with AES.
- ISO/IEC 19772The international standard for authenticated encryption — keeping data both secret and tamper-evident. GCM is one of its methods.Find out more
- X25519 · RFC 7748Key agreement on Curve25519 (RFC 7748) — howFind out moreQ seals something so that only the people it is meant for can open it.
-
-
Any change shows.
Every receipt is named by its own fingerprint. Change a single byte and the name no longer matches.
- SHA-256A hash function from NIST’s Secure Hash Standard (FIPS 180-4). Change a single byte of a file and its fingerprint is completely different.Find out more
- CIDA Content Identifier: a name made from the content’s own hash, so the name itself proves what the content is.Find out more
- DAG-CBORA strict, canonical way of encoding data (from IPLD): the same receipt always encodes to the same bytes, and so to the same fingerprint.Find out more
-
-
Permissions anyone can check.
Who may do what is a signed token, checked against the specification’s own test vectors.
- UCAN 1.0User-Controlled Authorization Networks: signed tokens saying who may do what, which anyone can check without asking a server.Find out more
- VarsigA small label saying which signature scheme was used, so a signature is always checked the right way.Find out more
-
-
Rules decided by a proven engine.
Q’s rules run in Cedar, the policy language built and open-sourced by Amazon Web Services, with a formally verified core.- CedarA language for writing permission rules, open-sourced by Amazon Web Services.Find out moreQ’s rules are written in Cedar.
- AWSAmazon Web Services built Cedar and uses it in its own services, such as Amazon Verified Permissions.Find out moreQ runs Cedar on your device; nothing is sent to AWS.
- Formal verificationCedar’s core is backed by machine-checked mathematical proofs of how it behaves — not only by tests.Find out more
- WebAssemblyA W3C standard for running compiled code safely in the browser. Cedar runs inside your browser as WebAssembly.Find out more
-
-
Leave no trace.
One button clears everything
Q kept in the browser. Cloud copies can only touch the folder Q made.- W3C Clear-Site-DataA W3C header that tells the browser to delete what a site has stored.Find out moreQ’s Leave no trace uses it.
- OAuth 2.0 + PKCE · RFC 7636HowFind out moreQ connects to Google Drive without ever seeing your password. PKCE (RFC 7636) stops an intercepted sign-in code being used by anyone else.
- drive.fileThe narrowest Google Drive permission:Find out moreQ can reach only the files it made or that you open with it — nothing else in your Drive.
-
These are the standards Q is built on, not a certificate. Q is in beta and has not had an independent security audit yet.
Built with love
Free to give — never free to take.
Designed by Darren Knipe, Dark Olive CIC.
With thanks to
- Svelte & SvelteKit the app
- Skeleton design system
- Tailwind CSS styling
- Dgraph graph database
- Vercel hosting
- TypeScript language
And to the engineering teams behind
And the wider community — the languages, the standards, and everyone who gives their work away.
- JavaScript
- TypeScript
- Go
- Rust
- C
- WebAssembly
- Node.js
- HTML
- CSS
- Lean
- W3C
- IETF
- FIDO Alliance
- Decentralized Identity Foundation
- UCAN Working Group
- IPLD & Multiformats
- MDN Web Docs
- every open-source contributor
Stay in touch
Only used to tell you about Q. It goes to Dark Olive’s admin inbox, nowhere else.
Keep it free
Q is free, and it will stay free — no adverts, no investors, nothing sold about you. It is built by Darren Knipe, a working parent, through Dark Olive CIC, a small community interest company. If Q is useful to you, or to someone you care for, a contribution keeps it growing and keeps it free for everyone.
Contributions open soon
Contributions go to Dark Olive CIC. It is a community interest company, not a charity, so they are not tax-deductible and there is no Gift Aid.