Security & trust
An honest approach to security.
Our disclosure model
Security claims are only useful when they are accurate. We do not publish certifications, audit results or controls that have not been formally verified.
Each product-security area below is labelled either Principle — the standard we design towards — or Implemented, once the control has been verified for the relevant product. Detailed, product-specific documentation is provided to customers during evaluation on request.
Product security
Security areas and principles.
Data privacy
PrincipleCollect only the personal data a feature needs, use it only for the stated purpose, and be transparent about it in each product's privacy policy.
Authentication
PrincipleEvery user must be reliably identified before accessing a platform, using established authentication mechanisms rather than custom schemes.
Encryption
PrincipleData should be encrypted in transit using modern TLS, and sensitive data protected at rest.
Infrastructure security
PrincipleProduction environments should be isolated, access-controlled and configured from reviewed definitions rather than by hand.
Backup & recovery
PrincipleBusiness-critical data should be backed up and recovery procedures tested, so an incident does not become data loss.
Vulnerability management
PrincipleDependencies should be monitored and patched, and reported vulnerabilities triaged and fixed according to severity.
Incident response
PrincipleSecurity incidents should be identified, contained, investigated and communicated to affected parties as required.
This website
Controls implemented on this website.
HTTPS & HSTS
The website is served over HTTPS with HTTP Strict Transport Security.
Security headers & CSP
A Content Security Policy, clickjacking protection, MIME-sniffing protection and a restrictive permissions policy are applied to every page.
Validated, rate-limited forms
Enquiry forms are validated on the server, protected against automated spam and rate-limited per client.
No tracking by default
No analytics or third-party tracking scripts run unless an operator enables them and the visitor consents.
Secrets kept server-side
Email and CMS credentials are read from server environment variables and are never shipped to the browser.
Protected administration
The content management interface is unavailable in production unless authenticated GitHub-based editing is configured.
Responsible disclosure
Report a vulnerability.
If you believe you have found a security vulnerability in this website or in one of our products, please tell us privately so we can investigate and fix it before it is disclosed publicly.
- Include enough detail for us to reproduce the issue.
- Do not access, modify or delete data that does not belong to you.
- Do not run tests that degrade service for other users.
- Give us reasonable time to respond before any public disclosure.
Email support@zyroteck.com or use our contact form and mention “Security report” in your message. Please do not include exploit details in public channels.
Need security documentation?
Enterprise customers evaluating our platforms can request product-specific security and data-handling information.
