Transport protection
The preview is served over HTTPS. The application also upgrades insecure requests and restricts framing, browser capabilities, content types and referrer data through response headers.
SECURITY
Reviewed: 17 September 2026
Security is a launch condition, not a marketing label. This page separates controls already active in the private preview from checks that still require production evidence.
The preview is served over HTTPS. The application also upgrades insecure requests and restricts framing, browser capabilities, content types and referrer data through response headers.
Financial inputs remain in this browser unless account saving is deliberately enabled. The current private preview does not expose a WealthWallah simulation API.
The database design denies anonymous access and uses row-level policies so an authenticated user can access only their own profile. Production evidence is required before account saving opens publicly.
Analytics events use a fixed allowlist of flow names and steps. Financial amounts, assumptions, profiles, error objects and form values are not sent to logs or analytics.
There are no public WealthWallah auth or simulation endpoints today. Rate limits must be enabled and tested at the edge before any such endpoint is introduced.
An independent penetration test or third-party security review has not yet been performed. WealthWallah will not describe the service as independently tested until that evidence exists.
Never enter a bank password, card PIN, OTP, account number, Aadhaar number, tax identifier or recovery code into a WealthWallah field. The product is a planning tool and does not need these details.
During the private preview, report a security concern through the same verified channel that granted access. Do not include passwords, tokens, financial inputs or exploit details in an unverified message. A dedicated security contact will be published before public launch.