Security at Stamps
A practical overview of the controls protecting organization accounts, integrations, and loyalty records.
Effective August 25, 2026 · Last updated August 25, 2026
Tenant isolation
Every dashboard and API operation resolves an organization identity before accessing data. PostgreSQL guards reject balances and transactions whose organization, member, program, or API key do not match.
Credentials
Passwords are managed through Neon Auth. Root administration is separately restricted to the configured Google account. API secrets are generated with cryptographic randomness, stored only as hashes, shown once, rate-limited, revocable, and optionally expiring.
Transaction integrity
Balance changes are atomic, serialized per member and program, require retry-safe idempotency keys, prevent negative balances, and create an append-only ledger entry with before-and-after balances.
Infrastructure
The application and primary database execute in Singapore. Connections use encryption in transit. Production responses apply strict transport security, content-security policy, clickjacking protection, MIME protection, and private cache controls.
Report a vulnerability
Please send a concise report, affected URL, reproduction steps, and potential impact to eddie@dxform.ph. Do not access other customers’ data or disrupt availability. We will acknowledge credible reports and coordinate remediation.