At a glance
Key points
The four things that set myconsentapp apart, and everything else built in. Each point links to the detail.
1. Double protection
Two signatures on every consent record
Every consent event is signed twice over the same hash: once with ECDSA P-256 and once with ML-DSA-65, the NIST post-quantum standard. Forging a receipt means breaking both.
-
ECDSA P-256 for today
Verifiable anywhere today: in the browser on our public verifier, on the phone, offline, or with any standard library.
-
ML-DSA-65 for tomorrow
NIST FIPS 204. Resists attacks by a quantum computer, so records stay trustworthy for their full seven-year life.
-
Keys in hardware
Signing keys are generated and used inside hardware security modules and never leave them.
-
Layered encryption for personal data
Personal data such as mobile numbers is encrypted field by field with AES-256-GCM using a managed data key, then again at the database, storage and backup level.
2. Post-quantum readiness
Records that outlive the quantum computer
Consent records are evidence that must hold up for years. A quantum computer that arrives in that time must not be able to forge or rewrite them, so we prepared now rather than migrate later.
-
Signed with the NIST standard
ML-DSA-65 (FIPS 204), signed in a hardware security module, on every ledger event alongside ECDSA.
-
Public keys published
Both the ECDSA and ML-DSA public keys are published as JWKS, so anyone can check both signatures without trusting us.
-
Hash chain on SHA-256
Events are chained and anchored in Merkle trees on SHA-256, which keeps its strength against known quantum attacks.
-
Crypto-agile by design
Every signature names its algorithm and key, and a key cannot be reused across algorithms. When browsers support post-quantum verification, the switch needs no change to records already issued.
3. Mobile app
Every consent, on the phone
An app for Android and iOS, with everything the web dashboard does: see every consent, withdraw in two taps and use your DPDP rights. Free, with no ads and no tracking.
-
Sign in with a mobile number
One-time code by SMS, then a passkey for fingerprint or face unlock.
-
Withdraw any time
As easy as giving consent. The company is notified by signed webhook and must stop.
-
Receipts verified on device
Signatures and the hash chain are checked on the phone itself, even offline.
-
Alerts that matter
Push notifications for new requests, expiring consents and breach notices.
-
Rights and family
Access, correction, erasure and grievances, plus guardians managing consent for a child.
-
Private by default
Session keys live in the phone’s secure keystore. No ads, no analytics SDKs.
The app is in testing. Until it reaches the stores, everything also works in a web browser.
4. Interoperability
Works with other Consent Managers
People should not need one app per Consent Manager. Our open interoperability profile lets a person see and withdraw consents held at another Consent Manager from one place, only with their explicit approval.
-
The person decides
Nothing is shared until the person signs in at the other Consent Manager and approves, for a chosen duration. They can revoke at either side, at once.
-
Consent records, not personal data
Only the consent record moves: company, purposes, status and dates. Never names, phone numbers or the data a company processes.
-
Withdraw across managers
A withdrawal made in our app is relayed to the other Consent Manager and recorded on its ledger.
-
Strong standards
OAuth 2.0 with PKCE, mutual TLS between partners and records signed as JWS with published keys.
-
Unlinkable identifiers
Each partner sees its own pseudonym for the person, so records cannot be joined across partners.
-
Open profile
The profile is published, so any Consent Manager can implement it, in either direction.
Demonstrated today against a simulated Consent Manager; live links follow partner agreements.
Also built in
-
Verifiable receipts
JSON and PDF/QR receipts anyone can check on the public verifier or with the open-source cmverify tool.
-
Tamper-evident ledger
Append-only, hash-chained, re-verified every 10 minutes and anchored to write-once storage for seven years.
-
Data stays in India
All personal data, backups and logs in India (Mumbai). We hold consent records, not your customer data.
22 Indian languages
Notices in English and every Eighth Schedule language, each consent tied to the exact version shown.
-
Built for the DPDP Act
Itemised notices, per-purpose consent, easy withdrawal, children and guardians, rights and grievances.
-
Easy to integrate
REST API, SDKs for Node.js, Python, Java and Go, signed webhooks, a hosted page and a sandbox.
Want the detail behind any of these?
We walk your team through the design, the cryptography and the interoperability profile.