Trust center / Controls and boundaries

How sensitive fields are protected

See where tokens, ciphertext and short-lived plaintext appear. Review the controls demonstrated in integration and the items to validate before deployment.

Data protection

Three controls across the data lifecycle

01 / Tokenization

Link records using tokens

Applications reference fields with opaque tokens. Authorized services can still retrieve values, so tokenization alone does not make the data anonymous.

02 / Encryption

Encrypt each stored field

The vault uses AES-256-GCM envelope encryption and authenticates context such as the tenant and field. An independent Key Broker controls decryption capability for workload types.

03 / Authorization

Authorize each use

A request must satisfy service identity, processing basis, purpose and workload conditions. Only fields approved for that request are released.

Verification scope

Demonstrable controls and deployment prerequisites

Documented in the test environment

Purpose-bound field access

  • Tenant isolation, type policies and whole-request denial when a field fails authorization.
  • Independent Key Broker control over workload field decryption.
  • Audit records and usage export for successful access. Export events omit raw values and field tokens.

Environment-specific validation

Hardware evidence and deployment

  • Real CPU/GPU remote attestation is pending. Types requiring attestation are denied without a working verifier.
  • Production identity provider, key-service availability and recovery testing must be reviewed at deployment.
  • Industry certifications, jurisdiction and customer compliance requirements need project-specific verification.

Technical FAQ

What happens at each boundary?

Which fields can be released to AI?

Only explicitly workload-enabled custom types that pass purpose policy are eligible. Built-in names, phone numbers, addresses, email addresses and national IDs, as well as types requiring a second approver, are ineligible.

What if one of two requested fields is ineligible?

The request fails as a whole and neither field is returned. The protected VISCOR job stops instead of continuing with incomplete input.

Does plaintext appear during inference?

Approved jobs can use values temporarily in controlled memory and must clear them after use. Integrators must keep raw values out of logs, indexes, usage ledgers and other persistent stores.

What information supports audit and reconciliation?

A successful access has an ID associated with its tenant, service account, workload, model version and purpose. VISCOR records refusal reasons internally. Only successful accesses count as vault-request usage.

What happens after a backup restore?

MemberGo records deletion in a ledger before clearing data. Recovery must replay the ledger so deleted data stays deleted when service resumes.

Scope security review around your workflow

Start with data categories, authorized roles and expected retention. Real sensitive data is not needed for scoping.