AGAnchorGPU

Trust center

Claims should be backed by evidence, not presentation.

A single place to distinguish documented product behavior from controls that require deployment, monitoring, operational records, or independent verification.

Service scope

This page describes the service design. It does not assert live infrastructure, monitoring, payment processing, certifications, customer activity, or an operating history.

Evidence matrix

What is documented—and what is not.

Unknown does not silently become operational. A production claim needs an owner, source record, effective date, review date, and correction process.

Account workflowInterface behavior documented
Ledger and idempotency modelRepresented in application logic
Live workload isolationNot verified
Crypto custody or settlementNot connected
Availability monitoringNot connected
Independent security assessmentNone claimed
Compliance certificationsNone claimed

Policy library

Review the policy drafts in context.

These policies remain drafts until the operator, jurisdiction, providers, retention rules, and legal review are confirmed.

Data minimization

The current account flow does not request a legal name, email, phone number, or identity document. This interface choice does not override applicable law.

Credential boundaries

Public SSH keys only, one-time recovery codes and API secrets, and stored verifiers instead of reusable secrets. Access-control implementation still requires operational evidence.

Accounting integrity

Idempotency and ledger-derived balances are design properties. They do not establish payment custody, reconciliation, solvency, or an audited financial system.

Not claimed

No badges without evidence.

AnchorGPU does not claim a penetration test, external audit, SOC 2 report, ISO certification, PCI validation, disaster-recovery test, facility assessment, uptime record, or verified response-time history.