Privacy notice

Development draft · 28 August 2026

Who this notice describes

This platform is branded BankU / BankU India. The legal name supplied is BankU (India) Limited. Verified registered-office and privacy-contact details have not yet been supplied for this project.

Information collected in this build

Enquiry forms collect your name, email, business name, selected product and message. Job applications collect your name, email, mobile number, chosen role and cover note. Workspace accounts and operational records are stored separately according to their purpose.

How information is used

Enquiries support business follow-up. Job applications support recruitment review. Workspace records support the operational workflows selected by an organisation. Do not submit OTPs, passwords, identity documents or banking credentials in free-text fields.

Candidate accounts

Creating a BankU Job candidate account stores your name, email address, mobile number and a salted password hash, not your readable password. Separate candidate session records and an essential secure login cookie keep you signed in. Hashed request-limit identifiers and signup, login and logout audit records help protect the service. Registration details are held pending while separate OTPs verify your email and mobile. Only protected OTP checks, expiry and attempt records are stored; the OTPs are sent through the configured email and SMS services. New accounts are created only after both checks pass, and verification times are recorded. Existing job applications are not automatically linked to an account.

Cookies and security records

The websites use essential session cookies. The workspace also uses an authentication cookie. No analytics or advertising trackers are included in this build. Security rate limits use hashed network identifiers, and account actions may generate audit records.

Access and retention

Authorised administrators and operations staff can access records required for their work. Customer workspace access is restricted by role and organisation. Before launch, the operator must define retention periods, deletion procedures, backup retention, processor contracts and a verified contact for data-rights requests.

Development data

This local preview is for synthetic information only. Do not use real customer, candidate or financial data until the privacy and security launch checks have been completed.