Data Storage & PII
Does AIR Kit store our customers’ personal data? Raw source documents remain with the issuer. Encrypted credential payloads may be stored in DStorage, while users control decryption and disclosure. The issuer signs the credential and encrypts it to the holder’s public key before storage. AIR stores and routes opaque ciphertext and metadata, not plaintext issuer data. What does a credential actually contain? The credential contains the attributes defined by its schema. Prefer the minimum claims needed for the use case, such asisOver18: true, kycLevel: "enhanced", or tier: "Gold". These claims can still be personal data. The signed credential payload is encrypted before storage; it is not replaced by a hash or a boolean proof.
Can AIR Kit or Moca Network read our customers’ credential data?
Issuers know the source data and the claims they issue. AIR receives encrypted credential payloads and metadata without the holder’s decryption key. Users control decryption and disclosure. Verifiers receive the claims requested by their Verification Program and approved by the user; a ZK proof can establish a condition without disclosing the underlying value.
Where is data stored geographically?
Source documents remain in issuer-controlled systems. Encrypted credential payloads may be stored with DStorage providers, alongside storage metadata. On-chain records and off-chain verification sessions are separate from those payloads. Confirm provider locations, metadata processing, and any regional commitments with the AIR team when assessing data residency. Encryption alone does not make identifiable data anonymous; see the European Commission’s GDPR guidance.
GDPR
Is this compliant with GDPR Article 5(1)(c) — data minimisation? AIR Kit supports data minimisation through schema design, encryption, and program-controlled disclosure. Choose only the claims needed for your purpose and request only the fields your verifier needs. Compliance depends on your implementation and processing purposes; using derived claims or encryption does not establish it automatically. How do we handle Article 17 data subject deletion requests? Revocation prevents a credential from passing subsequent checks that recognize its revoked status. It does not delete encrypted payloads, metadata, source records, or data already disclosed to verifiers. Handle erasure and retention separately across issuer systems, storage providers, and verifiers, including any applicable retention obligations. On-chain records cannot be removed by revoking a credential. Does issuing credentials constitute international data transfer under GDPR Chapter V? Assess the actual data flow: encrypted credential payloads and metadata may be stored outside the issuer’s systems, and verifiers may receive user-approved claims. Review provider locations, recipients, and applicable transfer safeguards with your data protection team. Do not assume that encryption or ZK proofs remove transfer obligations. Who is the data controller? Issuers control their source data and signing keys. Verifiers determine how they use disclosed claims. Establish controller and processor roles for each processing activity in your agreements, including AIR’s handling of ciphertext, metadata, and verification sessions. The storage architecture alone does not determine every party’s legal role. Does consent need to be obtained to issue credentials? Determine and document the lawful basis for issuance with your data protection team. User controls for decryption and disclosure are separate from that legal assessment. Direct issuance does not remove your notice or lawful-basis requirements.CCPA / CPRA
Does issuing AIR Kit credentials constitute “selling” personal information under CCPA? Assess your actual processing, disclosures, purposes, and contracts. Credential issuance and verification can involve encrypted personal information, metadata, and user-approved claims; it is not a blanket exemption from sale or sharing rules. See the California Attorney General’s CCPA guidance. How do we handle opt-out requests? Apply the opt-out to the relevant processing and sharing activities. Revocation can stop future use of a credential, but it does not retract data already disclosed or replace your opt-out and deletion procedures.Security & Breach Liability
What is the breach liability for verifiers accepting AIR Kit credentials? A proof-only program can reduce the data a verifier receives. Successful verification returns a Verifiable Presentation that can contain user-approved claims and optional proof material. Verifiers must protect any disclosed claims, identifiers, and session records they retain. Exposure depends on the program and the verifier’s data handling. What is the breach liability for issuers? Issuers hold source data and signing keys and prepare the credential before encrypting it to the holder. AIR’s storage and routing layer handles ciphertext and metadata. Assess exposure across source systems, issuer keys, encrypted storage, metadata, and any disclosed copies; encryption does not eliminate every breach risk or liability. Is there an audit trail for credential issuance and verification? AIR Kit uses verification sessions for usage and reporting. Whether a verification proof is submitted on-chain depends on the Verification Program. Do not assume every issuance or verification event appears in a single on-chain audit log; confirm the records available for your integration.Credentials & Revocation
How quickly does credential revocation take effect? Revocation is checked during verification. The effect depends on the issuer’s revocation mechanism and when the updated status is available to the verifier. Do not assume a universal one-block or instant propagation guarantee. What happens to credentials if a user closes their account? Include credential revocation in your account-closure process and handle source records, encrypted payloads, metadata, and previously disclosed data under your retention and deletion procedures. Account closure or revocation does not by itself erase all copies. Can a user hold credentials from multiple issuers in one AIR Account? Yes. An AIR Account can hold credentials from any number of issuers. The user controls which credentials to present at any given verifier. Can credentials expire? Yes. You set anexpirationDate in the credential subject. After expiry, the credential returns NON_COMPLIANT. You can re-issue with a new expiry at any time.