SECURITY OVERVIEW

Security is part of the design.

Auth by SoftMaji is designed around short-lived codes, authenticated API requests and private developer access. Security depends on correct deployment and operation as well as application code.

API request signing

Requests use HMAC-SHA256 signatures, timestamp validation and one-time nonces to make unauthorized and replayed requests harder.

Short-lived verification codes

OTP values are valid for 60 seconds, stored as password hashes for verification and encrypted for display in the private approval screen. A code can be accepted only once.

Application separation

Applications have separate credentials and hostname allowlists. Workspace ownership controls which developer account can view its requests.

Operational responsibilities

Use HTTPS, protect API secrets, restrict database access, monitor unusual activity, keep dependencies and server software patched, and test recovery procedures. A hostname supplied in a signed API request is not independent proof of domain ownership.

This page describes implemented design controls, not an independent security certification or guarantee against compromise.