Security Charter
Last Updated: September 18, 2026 • Entity: TRIDEVS (Karjan, Vadodara, Gujarat, India)
Security at TRIDEVS in 30 Seconds
We avoid unnecessary databases and bloated dependencies. What isn't collected cannot be breached.
Enforced TLS 1.3 encryption, automatic HSTS preload headers, strict frame clickjacking protection, and edge DDoS mitigation.
We welcome ethical security researchers. Responsible vulnerability disclosures to hello@tridevs.in receive legal safe harbor.
01.Security Engineering Philosophy
At TRIDEVS, security is not an administrative checkbox or a marketing slogan—it is a core architectural constraint. Our engineering methodology is governed by three non-negotiable principles:
We reject speculative data harvesting. The most secure data store is the one that never needed to exist.
Where possible, computation and state live on user devices (e.g., Room DB), eliminating centralized honeypots.
We strictly audit and minimize third-party runtime dependencies, preventing supply-chain malware contamination.
02.Infrastructure Hardening & Edge Defenses
The production environment for tridevs.in is hosted on a globally distributed edge network backed by hardened infrastructure:
X-Frame-Options: DENY (Anti-Clickjacking)
X-Content-Type-Options: nosniff (Anti-MIME Spoofing)
Permissions-Policy: camera=(), microphone=(), geolocation=()
03.Responsible Vulnerability Disclosure & Safe Harbor
We believe in working cooperatively with the global cybersecurity research community. If you identify a potential security vulnerability on any TRIDEVS digital property, we encourage you to report it to us immediately.
Our Safe Harbor Commitment
If you conduct your research in good faith and adhere to the following principles, TRIDEVS will consider your research authorized, will not pursue legal action, and will work with you to remediate the vulnerability promptly:
- Provide a reasonable amount of time to resolve the issue before disclosing it publicly.
- Do not access, modify, or destroy user data or degrade system performance (no DoS attacks).
- Do not attempt physical attacks, social engineering, or phishing against founders or operators.
- Execute testing strictly against non-destructive proof-of-concept boundaries.
04.How to Report a Security Concern
Please send your vulnerability report directly to our security inbox:
Please include detailed steps to reproduce, affected endpoints, and impact assessment. We acknowledge and thank ethical researchers who help keep our ecosystem secure.
