Security Architecture & Account Protection
Gold AH protects account and financial state through layered, server-enforced controls rather than decorative security claims. Credentials, sessions, requests, accounting records, and audit events each have a defined control boundary.
Financial state
Behind layered, server-enforced controls
Credentials
Hashed before storage
Sessions
Remain server-revocable
Requests
Rate-limited, replay-protected
Accounting records
Balanced journal posting
Audit events
Login attempts are audited
Identity & Session Security
Protection begins before a request reaches financial state.
Authentication endpoints are rate-limited, login attempts are audited, member credentials are hashed before storage, and active sessions remain server-revocable.
Salted Password Hashing
Passwords are transformed with PBKDF2-HMAC-SHA256 using a unique salt and 390,000 iterations before the hash is stored.
Hashed Bearer Sessions
Login creates an opaque bearer session. The server keeps only a token hash, with a configured lifetime, never the raw token.
Session Revocation
Members can revoke the current session or all sessions. A successful password change revokes all active member sessions.
Defense in Depth
Security controls and responsibilities
Platform-owned controls remain separate from the security actions members must perform themselves.
Shared protection
Platform owns server controls, members their credentials
Salted password hashing
PBKDF2-HMAC-SHA256 · 390,000 iterations
Opaque bearer sessions
Server-side token hash · configured TTL
Rate-limited auth operations
Register · login · password-change limits
Idempotent request handling
Duplicate payment protection on retries
Balanced journal posting
Debits = credits · append-only records
Credential hygiene
Unique password · verified domain · no secret sharing
Controlled Session Lifecycle
A session can be issued, bounded, and revoked.
The member authentication service creates opaque bearer sessions on the server. Session records are tied to configured expiry, while logout-all and successful password rotation remove active server-side sessions.
Session record
Issued, bounded and revoked by the server
Credential verification
Checked against a salted server-side hash
Session issuance
Opaque token; only its hash is kept
Configured lifetime
Bounded by the configured expiry
Explicit revocation
Logout-all and password rotation end it
Financial Integrity
Security continues into every value-moving request.
Request replay protection, balanced journal posting, and auditability work together so financial operations have traceable server-side evidence.
Retry safety
Request idempotency
Unique request keys prevent duplicate payment execution when a client retries a financial request.
Accounting truth
Balanced journals
Financial value moves through balanced ledger postings where total debits equal total credits.
Traceability
Audit event history
Authentication and account-state changes create server-side audit events for operational review.
Member Responsibility
Platform controls cannot replace safe credential handling.
Account protection is shared: the platform owns server controls while members remain responsible for password secrecy, domain verification, and prompt reporting of suspicious activity.
Use a unique, high-entropy password not used on any other website or service.
Never share verification codes, SMS challenges, or passwords with anyone—including platform staff.
Always verify you are visiting the official Gold AH domain before entering credentials.
Immediately report suspicious activity or unrecognized session alerts to official support.
Anti-Phishing & Official Communications Notice
Security advisory
Never share your password, authentication credentials, verification codes, or session tokens through messages. Always verify you are on the official Gold AH domain before signing in. If you suspect unauthorized access, change your password from the member profile; a successful password change revokes all active member sessions.
Keep control of your Gold AH account.
Sign in to rotate your password or end active sessions. If something looks unfamiliar, use the official security assistance route before continuing account activity.