Security Model
RANNTA PQ Cloud is designed as a verification service, not a custody service. Customer ML-DSA-65 private keys stay customer-side. The service stores public keys and server-side authorization state required to verify requests and enforce project policy.
Verification uses the project-compatible ML-DSA-65 context and canonical payload format.HybridRequired
The caller performs its existing classical authorization first; RANNTA independently verifies the PQ evidence and project policy.Persistent replay protection
Successful HybridRequired payload hashes are recorded server-side with a project-scoped uniqueness constraint.One-time API secrets
Full API secrets are returned only when created or replaced. The service stores a peppered hash and safe prefix, not a recoverable secret.Server-authoritative quota
Subscription periods and usage live server-side. All active API keys in a project share the same quota.Session revocation
Dashboard sessions use Secure HttpOnly cookies and the active session is removed from server storage on logout.
Payment security
Paid checkout begins with a one-time server-generated wallet challenge. RANNTA recovers the EVM signer from the EIP-191 personal-sign signature before it creates a payment intent. The signature only proves wallet ownership; it is never treated as payment.
Before a paid plan activates, the server independently checks the configured chain, USDT contract, verified payer wallet, canonical RANNTA treasury recipient, exact amount, successful receipt, required confirmations and transaction replay uniqueness.
Customer responsibility
RANNTA PQ Cloud does not replace the customer's business rules, wallet policy, classical authentication or authorization engine. The customer remains responsible for those controls and for the final business decision after the PQ verification result.