# Lockally security contact, per RFC 9116. # # Expires is REQUIRED by the RFC and must be under a year out. A stale file # is treated as no file, so this needs renewing before the date below. # # This file is served byte-identically at every location in the Canonical # list. Keep the three sources in step when editing: # website/public/.well-known/security.txt this file (lockally.com) # deploy/nginx/security.txt app. / mail. / autoconfig. # internal/api/wellknown.go api. (Expires is dynamic) Contact: mailto:security@lockally.com Expires: 2027-10-21T00:00:00Z Preferred-Languages: en Canonical: https://lockally.com/.well-known/security.txt Canonical: https://api.lockally.com/.well-known/security.txt Canonical: https://app.lockally.com/.well-known/security.txt Canonical: https://mail.lockally.com/.well-known/security.txt Canonical: https://autoconfig.lockally.com/.well-known/security.txt Policy: https://lockally.com/security#disclosure Acknowledgments: https://lockally.com/security/acknowledgements # There is no bug bounty programme. Stated here as well as in the policy, # because finding that out after doing the work is worse than knowing first. # We read every report, and we will credit you if you want to be credited.