Security
Clarity is part of protection.
Understand how access works, what information belongs in the simulation and where the limits are. Security should be understandable—not a collection of unsupported promises.
Account-scoped access to private records
Email confirmation and protected sessions
Never enter real bank or government ID details
01
Account access
Email and password sign-in uses managed authentication. Email registration requires confirmation before sign-in. Social sign-in is also available. Choose a unique password and keep control of the email address connected to your account.
02
Private records and simulated balances
Account records are scoped to their owner. Clients cannot directly edit balances or transaction records. A checked database function handles simulated transfers so the amount and available balance are validated together.
03
Protect yourself while exploring
Use fictional recipient details and sample financial figures. This simulation does not need a government identifier, Social Security number, passport, real card number or bank statement.
- Never share passwords or confirmation links
- Log out on shared devices
- Do not treat simulation references as payment confirmations
- Use the privacy notice to understand collected information
04
Know the current limits
This prototype does not provide card freezing, credit bureau checks, identity verification, fraud guarantees or deposit protection. Those capabilities and the corresponding disclosures would require an appropriate licensed partner and verified production processes.