Trust, Security, and Privacy at NexArt
NexArt helps teams create tamper-evident, independently verifiable execution records for AI and software workflows, while reducing the need to expose sensitive underlying data.
NexArt is an evidence layer, not a compliance certificate.
NexArt records and verifies what executed. It does not certify that an AI output was correct, fair, lawful, unbiased, or compliant with any particular regulation.
What NexArt helps prove, and what it does not prove
Helps prove
- A protected execution record existed at a specific point in time.
- The protected fields of that record have not changed without detection.
- The record was signed by the attestation node.
- Verification can be checked independently of NexArt.
- Confidential mode can support verification without exposing raw input or output in the public proof.
Does not prove
- That the AI output was correct, fair, or unbiased.
- That the execution was lawful in the relevant jurisdiction.
- The quality of the underlying model.
- Customer compliance with any regulation.
- Legal admissibility in any specific proceeding.
- That the customer had the right to process the submitted data.
Independence model
Trust in a NexArt record does not depend on trusting NexArt. Three independent layers establish record integrity, each verifiable on its own.
Integrity (hash match)
Every record contains a fingerprint computed from its protected fields. Recomputing that fingerprint and comparing it to the stored value confirms the record has not been altered. This check runs locally. It does not require any network call.
Node receipt (signature)
An independent attestation node signs the record with its private key. The signature confirms that the node saw the record at a specific time and that the record matched the fingerprint at the moment of signing.
Verification envelope (full record integrity)
The verification envelope wraps the record, the fingerprint, and the node receipt into a single portable artifact. A verifier checks all three: fingerprint match, signature validity, and structural completeness.
Confidential mode
In confidential mode, raw AI input and output are replaced with hash-bound commitments before permanent proof storage. This allows NexArt to certify integrity while minimising exposure of sensitive content in proof records.
Customer configuration matters. Full-content mode, or customer-submitted raw content, carries higher data exposure and should be assessed separately under the applicable agreement and data-handling configuration.
Public verifier minimisation
The public verifier at verify.nexart.io is designed to expose only the information required to confirm record integrity.
- Exact-hash lookup only. No browsing, listing, or searching of records.
- Minimal response payload containing certificate hash, execution identifier, protocol version, node attestation, and runtime hash.
- Raw prompts, raw inputs, and raw outputs are not exposed by default.
- Account email, API keys, and internal operational metadata are not exposed.
- Hidden or deleted project bundles are suppressed from public lookup.
Public key system and offline verification
Every NexArt attestation node publishes its public key at a well-known URL:
https://node.nexart.io/.well-known/nexart-node.jsonOnce a verifier holds a record and the node's public key, fingerprint recomputation and signature checks run locally. Previously issued records remain verifiable even if NexArt's servers are unreachable.
Protocol integrity
Versioning
Every record carries a protocol version identifier. The rules for computing fingerprints and validating signatures are defined per version.
Backward compatibility
A record created under a given protocol version is verified using that version's rules, regardless of the current version. Past records remain verifiable.
Vendor independence
Records remain verifiable independently of NexArt. The record is self-contained, the fingerprint computation is documented in the protocol specification, and the node's public key can be cached, archived, or distributed.
Governance and audit support
NexArt operates internal governance registers to support customer due diligence and evidence review. These registers are operated by NexArt and surfaced to customers under the applicable agreement.
- Sub-processor and international-transfer register.
- Incident register.
- Access review register.
- DSAR register and request workflow.
- Compliance document library.
- Canonical Node retention enforcement and legal-hold handling for proof records.
These records support audit and evidence-review workflows. They do not by themselves constitute a compliance certification.
Customer due diligence (available under NDA)
The following customer-facing documents are available under NDA to qualified prospects and customers. Several items remain subject to legal review before external reliance.
- Technical and organisational measures summary.
- Sub-processor summary.
- Data retention summary.
- Public verifier and proof visibility policy.
- AI governance position note.
- Incident response summary.
- DPA draft or outline (subject to legal review).
Request access via security@nexart.io.
Current limitations
- NexArt does not currently hold SOC 2, ISO 27001, or ISO 42001 certification.
- Some compliance documents require legal review before external reliance.
- Customer configuration affects what data is processed and how it is retained.
- Full-content mode, if explicitly enabled, carries a higher data-exposure profile than confidential mode.
- Vendor transfer documentation and DPA terms may require legal review for specific jurisdictions.
- Verification proves record integrity. It does not prove output correctness or regulatory compliance.