Skip to content

Trust centre

Security at Danphe Council

What protects your documents today, what we have not done yet, and who processes your data.

Certifications

Where we are

No security certifications yet

Danphe Council does not hold SOC 2, ISO 27001 or any other certification today. We will list a certificate here only once it is issued, with the report available on request.
  • SOC 2 Type IIPlanned
  • Independent penetration testPlanned
  • ISO/IEC 27001Under consideration

Controls

What is in place today

  • Encryption per tenant

    Data is encrypted in transit (TLS) and at rest. Stored files and sensitive fields use a separate encryption key for each organisation, managed in AWS KMS, so deleting an organisation's key makes its data unreadable.

  • Isolation between organisations

    Every organisation's data is separated by PostgreSQL row-level security, forced on every tenant table. Automated tests try to read across organisations and must fail.

  • Tamper-evident audit chain

    Each answer's audit record is hash-chained to the previous one and anchored with an asymmetric signing key. A verifier detects any later change to a record.

  • No training on your data

    Your files, questions and answers are not used to train models, by us or by the model providers we use under their enterprise terms.

  • Upload checks

    Uploaded files are quarantined and scanned for malware before they are read. Files that fail are rejected.

  • Roles and least privilege

    Workspace roles limit who can change models, policies and settings.

  • Vendor controls

    Workspace rules can restrict which model vendors may be used and require providers that do not retain prompts or outputs.

  • Secrets

    Credentials are never stored in code. Model output is rendered without scripts or remote images.

Audit record

Proof you can check, and that can't be quietly changed

Every finished question gets one evidence pack. Records are hash-chained, so changing any past record breaks the chain from that point and the verifier reports it.

Inside one evidence pack
  • Inputs

    Hash of the question and of every document, with the passages that were read.

  • Every model's answer

    Which model was asked, which actually answered, and its tokens and cost.

  • Every check

    Each statement with every verdict: who checked it, in which round, agree or not.

Audit record

One per finished question, as JSON or a printable page

prev_sha256 · 9f2c…41ab

record_sha256 · 03d7…e810

Signed daily anchor

  • Quotes

    The exact passage behind each verdict, with document and page; invalid quotes are marked.

  • Fairness and dissent

    Proof that no model judged itself, plus the points the models disagreed on.

  • Settings and cost

    Prompt bundle and settings version, depth, rounds and the run's total cost.

The answer text and quotes are stored encrypted with your organisation's key; the hashes link each record to the one before it.

Try it: change one past record

  1. Record 1, link intact

    Run 1 · Standard · 9 statements · 7 agreed

    prev …

    hash …

  2. Record 2, link intact

    Run 2 · Quick check · 4 statements · 4 agreed

    prev …

    hash …

  3. Record 3, link intact

    Run 3 · Thorough · 12 statements · 2 disputed

    prev …

    hash …

  4. Record 4, link intact

    Run 4 · Smart · 6 statements · 6 agreed

    prev …

    hash …

  5. Record 5, link intact

    Run 5 · Full report · 31 statements · 3 disputed

    prev …

    hash …

Chain intact: every record's hash matches the link stored in the next one.

Real SHA-256 hashes, computed in your browser. Danphe's records are also signed with a key and anchored daily.

Sub-processors

Who processes your data

Sub-processors
CompanyPurposeData
Amazon Web ServicesHosting, storage, encryption keys; AI models through Amazon BedrockAccount data, documents, questions and answers
Microsoft AzureAI models through Azure OpenAI and Azure AI FoundryQuestions and the document passages needed to answer them

The full list with locations is on the sub-processors page. We give 30 days' notice of changes to customers with a DPA.

Report an issue

Responsible disclosure

Report a vulnerability

Found a vulnerability? Email [email protected] with the details and steps to reproduce. Please give us reasonable time to fix it before disclosure, and do not access other customers' data. We do not run a paid bug bounty yet.

Security reviews

Security questionnaires and the AI system card: see AI system card or contact us.