Security
Reviewed 16 October 2026. This page describes the website’s current baseline and the controls considered for project delivery. It is not a certification, penetration-test report, or guarantee.
01
Website Security Baseline
The website is a static application. Enquiry forms use browser-side required-field and email-format checks and send submissions directly over HTTPS to Web3Forms. Its browser-visible access key identifies the form; it is not a server-held secret. Browser checks do not replace server-side validation or abuse protection. The website does not implement its own server-side validation, request throttling, or hidden anti-bot field. Provider protections depend on the Web3Forms service and account configuration. Google Analytics is initially loaded only after analytics consent.
02
Hosting Controls
Deployment files include proposed security headers and HTTPS redirects for supported hosting environments. Their presence in the source does not establish that the live host applies them. HTTPS, headers, access controls, logging, backups, dependency updates, and release procedures must be verified on the production deployment. No independent security certification or penetration-test result is claimed.
03
Project Security
Project controls depend on the agreed scope and risk profile. They may include threat modelling, authentication and authorization, encryption, audit logs, dependency review, environment separation, testing, incident procedures, and supplier assessment.
04
Data Handling and Suppliers
Client and enquiry information is limited to a defined purpose and should be accessible only to relevant personnel and approved providers. Supplier access, transfer locations, retention, backups, and disposal must be reviewed for the applicable project and jurisdiction.
05
Incident and Breach Management
Suspected incidents should be contained, investigated, documented, risk-assessed, and escalated to the responsible entity. Where applicable law requires notification, the entity will notify the relevant regulator, affected organization, or individuals within the required period and maintain required breach records.
06
Vulnerability Reporting
To report a suspected vulnerability, email contact@techbrainnetworks.com with the affected URL, impact, reproduction steps, and safe supporting evidence. Do not access other users’ data, disrupt services, use social engineering, or publicly disclose an unresolved issue.
07
Response Expectations
Reports are intended to be acknowledged, triaged by severity, investigated, and remediated according to risk. This page does not create a bug-bounty programme, safe harbour, or guaranteed response time. A project contract may define stronger service levels.
These public pages provide general transparency information. They do not replace project-specific contracts, regulatory filings, or advice from qualified counsel in the relevant country.