Skip to content

Demo environment · sample data

Data Consent Manager

Security and trust

Built to be trusted by people, companies and regulators

A Consent Manager holds the record of what people agreed to. We designed every part of the platform so that record is private, provable and cannot be quietly changed.

How we protect it

Six layers, each one checkable

  • Hosted in India

    Every service, database and backup runs in the AWS Mumbai region (ap-south-1).

    • Isolated private network, no public database
    • Encrypted at rest with AWS KMS keys
    • TLS 1.2 and 1.3 only, modern ciphers
  • Signed by us, verifiable by anyone

    Consent records, webhooks and ledger checkpoints are signed with ES256 keys held in AWS KMS.

    • Private signing keys never leave the hardware security module
    • Public keys published at /.well-known/jwks.json
    • Any system, auditor or court can verify a record
  • Tamper-evident ledger

    Every consent event is chained to the one before it, so no entry can be changed or removed without detection.

    • Hash-chained, append-only entries
    • Signed checkpoints written to write-once (Object Lock) storage
    • Kept for at least 7 years in production
  • Data-blind exchange

    When one company shares data with another, it is sealed for the receiver. We carry it and check consent, but cannot open it.

    • X25519 key agreement, HKDF and AES-256-GCM
    • Only the receiving company holds the private key
    • Every transfer tied to an active consent and recorded
  • Minimal, encrypted personal data

    We keep only what the service needs. Contact details are encrypted and searched only by a keyed hash.

    • E-mail addresses encrypted with AES-GCM
    • Sign-in by one-time code, no passwords to steal
    • A different ID for each company, so companies cannot link people
  • Watched and answerable

    Alerts on failures and unusual activity, and a written plan for incidents.

    • Structured logs and alarms on every service
    • Incident runbook with CERT-In and Board notification steps
    • Signed, retried webhooks with acknowledgement

Before production

Independent checks we commit to

The demo you see runs on the same architecture as production. Before we serve real people, these independent checks are completed.

  1. 1

    Independent security test

    Vulnerability assessment and penetration test by a CERT-In empanelled auditor, before production and every year after.

  2. 2

    Controls mapped to ISO/IEC 27001:2022

    Our internal audit plan maps every control to Annex A, so one set of evidence serves the Board and any future certification.

  3. 3

    Accessibility audit

    Every major release of the screens people use is checked against WCAG 2.2 AA.

Responsible disclosure

Found a problem? Tell us.

If you believe you have found a security issue, tell us through our contact form and start your message with “Security”. We reply within 2 working days, keep you informed, and never take action against good-faith research.

Please do not access other people's data or disrupt the service while testing.