One canonical authority, treasury and journal connect Numina's app, control room and integrations. Security follows the same system from a proposed action through its recorded outcome.
Check live connections ↗Read the full security document ↗Server-side access checks restrict customer records and owner operations. Requests use bounded inputs, revision checks and replay controls. Private API and payment responses stay outside the app's offline cache.
Payment reconciliation checks provider-confirmed facts. The Numina-native treasury retains one canonical journal; provider observations keep their original source, currency and verification scope.
The full document covers architecture, trust boundaries, threats, access, data handling, keys, financial controls, release verification, incident response and recovery. It distinguishes reviewed protections from operating requirements and evidence still needed.
Financial operations require their applicable licensing, customer rights, custody, reserve and execution evidence. A native balance or an internal policy decision does not establish a settled transfer. Independent security assessments and financial authorization are not established by this documentation.
For a security concern, email skott34@numinalabs.xyz with a minimal description and the affected page. Arrange a secure channel before sending sensitive details.
Document reviewed September 15, 2026. Operator: SK Consulting LLC, Iowa, USA.
Register provider relationships, jurisdiction-specific authority, terms and security evidence in the owner workspace. Stored receipts establish document identity; issuer verification and service approval remain separate.
Open financial evidence ↗