Hema Sai Mallampati logo

Security Policy

How this Site, its visitors and their data are protected.

Version 1.0 · Last updated: 2 October 2026 · Dallas, Texas, United States

Encryption in Transit & at Rest Multi-Factor Administrator Access Web Application Firewall

1. How the Site Is Protected

The Site is built on defence in depth and least privilege. The main safeguards are:

Edge protection

Traffic passes through a content delivery network with a web application firewall, managed rule sets, rate limits and a country allowlist before it reaches the application.

Administrative access

The administration area requires multi-factor authentication, is limited to approved network addresses, separates owner and editor roles, signs administrators out after inactivity, and records every change.

Encryption in transit

Plain HTTP is redirected to HTTPS, the edge accepts TLS 1.2 or newer, and HTTP Strict Transport Security is enforced.

Encryption at rest

Stored data is encrypted with AWS storage encryption, and contact and download details are additionally encrypted at the application level with authenticated encryption. Authorised services can decrypt data to do their work; this is not end-to-end encryption.

Application safeguards

Input is validated and sanitised on the server, forms are protected against cross-site request forgery, a restrictive content security policy and other security headers are sent on every response, and uploads are checked against their declared file type.

Software supply chain

Each release is built from reviewed source and checked by automated tests, dependency and static analysis scans, secret scanning and a licence inventory. Scan results describe the release at that time; they cannot guarantee the absence of vulnerabilities.

How personal data is collected, kept and shared is described in the Privacy Policy.

2. Reporting a Weakness

If you find a security weakness, please tell us privately. What you may test, the safe harbour for good-faith research and how to report are set out in the Vulnerability Disclosure Policy.

Maintained by Hema Sai Mallampati · Version 1.0 · Last updated: 2 October 2026 · Dallas, Texas, United States