How namohub protects your community's data.

Encryption

All traffic to and from namohub is served over HTTPS with TLS terminated at the edge. Customer data is encrypted at rest in PostgreSQL using full-disk encryption on the underlying volumes. Backups carry the same encryption.

Access control

Permissions are enforced at the query layer, not just the UI: every database read is scoped to the authenticated member's tenant, and every write goes through a role-permission check. A platform-admin role exists for namohub support, and every action a platform admin takes is recorded in a separate cross-tenant audit log.

Audit log

Every administrative action — member changes, permission grants, financial transactions, data exports — writes an append-only row that your tenant superadmins can read in /admin/audit. Rows are not editable or deletable by anyone, including namohub engineers.

Authentication

Passwords are stored as Argon2 hashes. Sessions are rotated on login, locked to a single device cookie, and expire on inactivity. Optional MFA (TOTP) is available per-tenant. Magic-link logins use single-use tokens with short expiration.

Reporting a vulnerability

Found something we should know about? Email security@namohub.com. We acknowledge within one business day and keep researchers updated until the issue is fixed. We don't pursue legal action against good-faith security research.