Security and access
Customer records are separated by workspace at the API and PostgreSQL row-security layers. Sensitive platform operations use permission checks, MFA and audit events.
Learn how NexaCard separates customer data, handles storage and recovery, and communicates service or security issues.
Customer records are separated by workspace at the API and PostgreSQL row-security layers. Sensitive platform operations use permission checks, MFA and audit events.
Account and card records use PostgreSQL. Durable media and encrypted backups use private Amazon S3 storage. The single-host service does not provide automatic failover.
Some data can be exported or deleted through account controls. Security and audit records may follow different retention rules. Review the published privacy notice before making a deletion request.
Published disclosure documents are versioned by the platform operator and linked from the interactive trust center.
Application-reported state: operational. This application-hosted status view cannot report a total production-host outage while that host is unavailable.
No public release-history entries have been published yet.
Opening your NexaCard workspace…