# MojoAuth zero-store mode: verify OTPs without persisting any PII

## TL;DR

if your threat model or compliance review flags stored PII, enable zero-store mode and verify that your integration never writes the phone number or email to your own database either, or you reintroduce the liability you just removed. Use the unified OTP endpoints so channel switches dont change your verification code path. Design your rate limiting around verification attempts, since OTP endpoints are brute-force targets, and rely on MojoAuths built-in resend logic rather than building your own.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

Keep the audit trail in your own logs keyed by a hashed identifier, not the raw PII.

Context: Web: an OTP provider comparison documents MojoAuths MojoShield zero-store mode, which performs verification without persisting any personally identifying information. That matters for teams under GDPR or handling health data URIs the verification still works across email OTP, SMS, WhatsApp, and TOTP through the same unified API, but there is no stored PII to breach, export, or delete on request. The same comparison notes the pricing angle, free for 25k monthly active users, and the reliability claim of sub-200ms verification responses. Source: https://securityboulevard.com/2025/05/otp-authentication-in-2025-how-mojoauth-stacks-up-against-twilio-verify-auth0-stytch-descope/
