Visitor access & privacy
One sample search is available before visitor access is required. New users Sign Up once with their name and an email address or mobile number. Returning users Log In with only the email or mobile number they previously supplied. No password, email verification or SMS verification is performed. These details are self-reported; they do not establish identity or grant administrator or private-case access. Names, contact details and submitted research query records are stored in the portal database for administrator review, never in public GitHub source files. Search records are retained for up to 90 days; anonymised sample searches cannot reliably identify a person. Names and contacts are not sent to AI search providers as part of visitor authentication. An anonymous expiry marker (no name or contact) allows previously registered visitors to use saved public tools offline; offline access does not grant private permissions. The session cookie is HttpOnly, Secure on HTTPS, SameSite Strict and lasts up to 90 days. Inactive visitor records are removed after 365 days when cleanup runs. A signed-in visit may be recorded for operational analysis. The Log In/Sign Up and Logout controls let you manage the current session. This self-reported contact login is not secure enough for confidential customer cases; private banking and administrator functions have separate authentication. Clearing a session does not immediately delete the retained visitor record. This page describes the implemented visitor feature; it is not a claim of independent privacy certification.
Website analytics
Public pages use Google Analytics 4 to measure visits. Google may process browser and device information, IP addresses and analytics cookies. The portal sends a fixed public page address without query strings or fragments and does not deliberately send names, contact details, search questions or transaction inputs. Private workspaces and transaction tools are excluded. Advertising personalization and Google signals are disabled in this tag. The tag does not load when your browser signals Global Privacy Control or Do Not Track. Learn how Google uses information from partner sites.
Advertising, cookies and Google AdSense
TradeFinanceBD may use Google AdSense on public pages. The public homepage contains the Google AdSense site-verification script. Google and its advertising partners may collect or use cookies, web beacons, IP addresses or other identifiers for advertising delivery, measurement and personalization, depending on your choices and applicable law. Third parties may place or read cookies through Google advertising technology. Learn how Google uses information from sites that use its services and manage Google ad preferences at My Ad Center. Advertising approval and placement are determined separately and are not guaranteed by the presence of verification code.
For users in regions requiring consent, we will configure an applicable consent-management solution before enabling relevant advertising. Private administrator, banking and login pages are not intended to host advertising tags.