Legal

Privacy Policy

Last updated: 14 November 2026

This is a simulated environment. Northbridge Bank, as presented here, is a demonstration account interface. It does not hold customer funds, does not provide banking services, and is not connected to any payment network, clearing system or real financial institution. Do not enter real banking credentials, real card numbers, or real account details anywhere in this application.

1. What this application is

This site is an account-interface demonstration. It presents a sample account profile, a displayed balance and a set of illustrative transaction records so that the interface, navigation and security controls can be evaluated. The displayed balance of $412,000.00 USD and every transaction line are account-interface data stored in this application’s own database. They are not real funds, they are not held on your behalf, and they are not redeemable.

2. Information we store

To make the interface work as an application rather than a mock-up, we store a limited set of data:

  • Account credentials: your email address and a salted PBKDF2-SHA256 password digest. The plain-text password is never stored and never written to logs.
  • Profile details you provide: the account holder name, contact number, address lines, city, country and time zone. These are editable in the account profile and are used only to render the interface.
  • Session records: a hashed session token, the session type, browser user-agent string, approximate network address, and issue/expiry timestamps. The raw session token is only ever held in an encrypted-in-transit, HttpOnly cookie in your browser.
  • Sign-in and security events: successful and failed sign-in attempts, verification code issuance, and profile changes, retained to populate the security centre.
  • Declined movement requests: if you submit a transfer or withdrawal form, the amount, beneficiary name, reference and the server’s decline reason are recorded so the attempt appears in payment activity.

3. Email verification codes

Email verification codes are generated by this application and delivered to a development mailbox that is part of the same application. No third-party email provider is used, and no message is sent to an external mail service. Codes are stored as hashes, expire after ten minutes, are single-use, and are never rendered in public pages or written to client-side source.

4. How we use data

Data is used strictly to operate the interface: to authenticate you, to gate the account pages behind a server-side session check, to render your profile and transaction records, and to display security history. We do not sell data, do not build advertising profiles, and do not share data with third parties.

5. Cookies

This application sets three essential cookies. None of them are used for analytics or advertising.

  • nb_session — the authenticated session, HttpOnly, SameSite=Lax.
  • nb_pending — a short-lived pending-session cookie used only between password sign-in and email verification.
  • nb_csrf — a cross-site request forgery companion value.

6. Security measures

  • Passwords are hashed with PBKDF2-SHA256 using 150,000 iterations and a per-user random salt.
  • Only the SHA-256 digest of a session token is persisted, so a database copy cannot be replayed.
  • All state-changing requests require a same-origin check and a per-session CSRF token.
  • Failed sign-ins are recorded and throttled per email address.
  • Verification codes are single-use, expire quickly, and lock after five incorrect attempts.
  • Restricted actions are enforced on the server, not by hiding buttons in the browser.

7. Data retention and deletion

Expired sessions and consumed verification codes are purged automatically. Because this is a demonstration environment, the account and its records may be reset or removed at any time without notice. You can end your session at any time from the security centre.

8. Your responsibilities

Please treat this environment as public-facing software: use only the demonstration credentials provided, choose a unique password if you create an account, and never reuse credentials from an actual financial account. No genuine bank will ever ask you to reuse your online banking password in a third-party interface.

9. Children

This interface is not directed at children and is not intended for use by anyone under 18.

10. Changes to this policy

If the behaviour of this demonstration changes, this policy will be updated and the date above revised.

11. Contact

Questions about this demonstration can be raised through the contact details published by whoever supplied this build. There is no real bank to contact at the Northbridge Bank name used here.