Access
Review eligible account data, support context and customer-facing records.
Canon Statement
AEI does not publish data. AEI publishes proof.
Public proof is not public customer data. AEI may expose hash, URN, timestamp, chain ID, transaction hash or verification status when explicitly released. AEI does not expose raw private payloads unless the release policy authorizes it.
Data We Process
Private // Internal
■
Customer Account DataIdentity vectors, contact records, authentication context and customer-level metadata. Private by default.
■
Operational LogsSystem telemetry, runtime events, support traces and internal audit signals used for security, service quality and incident review.
■
Billing & MarketplaceTransaction records, entitlement references, procurement state, usage reporting and marketplace billing evidence.
Public // Evidence
◇
Evidence MetadataCryptographic hashes, URNs, timestamps, verification states and public proof summaries authorized for external validation.
◇
Atlas Ledger RecordsGoverned evidence references, seal metadata and operational proof objects exposed only through approved client-safe surfaces.
◇
Web3 Public AnchorsPublic transaction references, chain identifiers, contract addresses and explorer links only when Web3 anchoring is explicitly confirmed.
Retention & Control
Immutability Warning
Data committed to public Web3 anchors or immutable institutional ledgers cannot be conventionally deleted. Erasure requests apply to off-chain customer account data, support records and isolated operational logs within the limits of policy, contract and law.
| Data Class | Retention Period | Access Controls |
|---|---|---|
| Account Data | Active account duration + 30 days | User authorization / administrative escrow |
| Operational Logs | 90-day rolling window unless otherwise required | System administrator / authorized support |
| Public Anchors | Indefinite where immutable | Universal read after explicit public release |
| Evidence Metadata | Policy-bound by seal type | Client-safe projection only |
What AEI Never Exposes
AEI treats secrets, raw private payloads and cross-customer records as non-public material. These objects are never placed in public pages, client-side components, static scripts or unauthenticated responses.
×Secret credential material
×Service account payloads
×Runtime access headers
×Signing credentials
×Wallet signing credentials
×Non-public customer evidence
×Cross-customer records
×Unverified billing records
×Internal operational secrets
Customer Rights & Requests
Customers may request access, correction, export or deletion of eligible off-chain records. Requests involving billing, entitlement, evidence, account state or operational logs may require validation before processing.
Correction
Request updates to incorrect profile, contact or account metadata.
Export
Receive eligible records in a structured format when validation is complete.
Deletion
Delete eligible off-chain records where contract, policy and law allow it.