Security
Current API source assigns four fields directly to Security, covering additional-business registration, app-version verification, and signup email/mobile verification. Historical OTP, reCAPTCHA, login-limit, code-generation, and reset-password labels are not admitted as the current rendered category schema. No category, field, value, policy, or authentication state was requested.
Do not open, capture, copy, disclose, or modify security-policy values, rate-limit thresholds, reCAPTCHA settings, provider IDs, site keys, secret keys, tokens, or private policy data through this workflow.
Source-only boundary
The four catalog associations above are safe capability classes, not deployed controls or values. Do not enumerate or reproduce field keys, thresholds, policies, provider details, credentials, endpoints, tokens, challenge settings, or validation logic. The retained image is navigation-only and does not authorize opening Security.
Security configuration can affect authorization, signup, verification, sessions, business access, recovery, abuse controls, and customer ordering. These are risk classes only; no behavior, coverage, enforcement, deployment, or success is claimed.
Save and capture policy
Selecting a returned category performs authenticated reads, and the shared editor can write sequentially; GET/HEAD and navigation are not safe probes. No Security screenshot beyond the retained navigation-only image is approved. Re-entry requires security-owner approval, a synthetic isolated project, intercepted requests, and immutable non-secret effect receipts.
Related guides: Settings logs · Settings overview