Spectre security and privacy
Public security boundaries for Spectre Web, Monecuer Identity sign-in, browser sessions, app-only sensitive actions, and information that is intentionally not published.
Web authentication
Spectre Web authenticates through Monecuer Identity rather than implementing a second browser signup system. Browser-facing product credentials are kept in protected server-managed cookies instead of localStorage.
Authentication callbacks are validated before a Spectre web session is established. If a secure connection cannot be verified, the user is returned to a safe sign-in state.
Sensitive actions
The public web surface intentionally does not expose every mobile money action. Holding back sensitive actions until their browser security controls are mature is a security boundary, not a separate financial system.
Private provider credentials, cryptographic material, internal fraud rules, administrative controls, and security thresholds are not part of public documentation because exposing them would weaken the system.
Identity and financial data separation
Monecuer Identity handles the account and trust relationship. Spectre handles Spectre financial data. This separation is designed to make authentication reusable without turning Identity into a warehouse for product-specific financial records.