Last updated: 26 October 2026
This page explains how Silux Control UK Ltd T/A Silux Mail protects your data, and how to report a security problem.
How we protect you
- Nothing leaves without approval. The Outbound Action Firewall holds every email and external action until you approve the exact content; approvals are locked to that content and logged in a tamper-evident outbox log.
- Encryption. TLS for every connection. Mailbox passwords, sign-in tokens and keys are encrypted at rest. Sync between computers is end-to-end encrypted (AES-256-GCM with keys that never leave your computers), so our sync server holds only ciphertext.
- Accounts. Two-factor authentication, passkeys, step-up checks for sensitive actions, sign-in lockout after repeated failures, device and session management with remote sign-out and erase.
- AI safety. Emails are treated as data, never instructions; prompt-injection attempts are flagged and ignored. AI providers may not train on your data.
- Privacy by default. Tracking pixels in incoming mail are blocked; remote images load through a privacy proxy; our website uses no tracking cookies.
- Least privilege and audit. Staff access is limited and logged. Admin actions, sign-ins and key changes appear in audit logs.
- Testing. An automated test suite, including tests for sign-in, approvals, encryption and sync, runs before each release.
Reporting a vulnerability
Email info@siluxmail.com with the subject "Security". Please include:
- what you found and where (URL, app version, endpoint);
- steps to reproduce, and the impact you think it has;
- your name or handle if you'd like credit.
We will acknowledge your report within 2 working days, keep you informed, and aim to fix critical issues within 7 days and others within 90 days.
Safe harbour
If you act in good faith under this policy we will not pursue or support legal action against you. Please:
- only test against accounts you own or have permission to use;
- never access, change or delete other people's data; stop and tell us if you reach any;
- avoid service disruption (no denial-of-service, spam or social engineering of our staff);
- give us reasonable time to fix the issue before telling anyone else.
Out of scope: reports from automated scanners without a demonstrated impact, missing best-practice headers with no exploit, and issues in third-party services we use (please report those to the provider).
We publish a security.txt file at /.well-known/security.txt.
Silux Control UK Ltd T/A Silux Mail · Registered in England and Wales, company number 11901981 · Registered office: Prospect House, Colliery Close, Chesterfield, S43 3QE, United Kingdom · VAT GB 321 2589 23 · ICO registration 00012813411 · info@siluxmail.com