Maple is pre-launch: there is no account system, no saved user data beyond the waitlist form, and no connection to real trading capital today. That significantly limits what there currently is to secure, and this page will be expanded into a full security model as those systems are built.
What exists today
The only data this site collects is what's submitted through the waitlist form — name, email, role, and an optional note about intended use. There is no sign-in, no password, and no user dashboard.
What's designed in from the start
As accounts and saved research are introduced, Maple is designed to scope each user's data to their own account at the database level — enforced by the database itself, not solely by application code — and to route any request requiring a third-party provider credential through a server-side layer, so that credential is never exposed in code a browser downloads.
A deliberate scope boundary
Maple is not designed to connect to any brokerage, exchange account, or payment processor for trading purposes, and will not have the ability to place a real trade or move real funds. That removes an entire category of risk that trading-adjacent software normally has to defend against.
Ongoing practice
As an early-stage company, Maple's security posture will be reviewed and documented in more depth as the platform is built — this page reflects where things stand today, not a finished system.