SECURITY STATEMENTS
Last Updated: May 26, 2026 // Version 1.1.0 // Proprietor: Senthil Kumar P (@senthiltechspot)
⚠️ SYSTEM SECURITY SPECIFICATIONS & LIMITS
- ▪Solo Uptime Constraints: We are a bootstrapped, single-developer startup. If the founder Senthil Kumar P's development PCs, hosting terminals, or network lines face hacking, hardware faults, or power cuts, pipeline uptime might drop below 99% during restore.
- ▪Code Leakage Disclaimer: While we deploy AES-256-GCM encryption and HSM vaults, if third-party exploits, hypervisor escapes, or cyber intrusions result in codebase leakage or access, Senthil Kumar P / Venelx is not responsible or legally liable.
- ▪Compilation Security Limits: We compile your applications, but we are not responsible for securing the internal architecture, credentials, or third-party packages inside your uploaded code. Your code security is your sole responsibility.
1. HARDWARE KEY ENCRYPTION & DATA WASTAGE
All customer certificates, provisioning profiles, and keystore passwords are encrypted immediately at rest using hardware-sealed keys. Access is limited to RAM-cached environments running inside ephemeral Mac minis during compile operations, and all traces are immediately purged when the runner exits.
2. PENETRATION & EXPLOIT CODE CONDUCT
All clients must maintain the decorum of the code of conduct policy. Running network probes, port scans, or exploit payloads against Venelx without explicit legal, written consent from Senthil Kumar P is strictly illegal. Any malicious scanning will result in immediate IP blacklisting and the handover of all connection logs to federal cybersecurity authorities.
3. REFUND LIMITS FOR SECURITY FAULTS
Due to bare-metal hardware constraints and power costs, if resource utilization on your profile has exceeded 50% of the plan limits, we cannot issue any refund under any condition (including security interruptions).