[email protected]
Partnerships, media, service enquiries and questions that do not involve an account or security issue.
SUPPORT / PRIVACY / SECURITY
Send the right detail to the right place.
Use the addresses below for non-urgent Layer400 matters. Never send account passwords, receiver private keys, recovery material or unredacted identity documents by email.
- EMERGENCY SERVICE
- NO
- FLIGHT AUTHORISATION
- NOT PROVIDED
- ACCOUNT PASSWORDS
- NEVER REQUESTED
- SECURITY REPORTS
- PRIVATE ADDRESS
CONTACT ROUTES
Choose the right contact.
Include a public track reference, station reference or approximate UTC time only when it is relevant. Do not send raw location evidence unless Layer400 support asks for it through a protected channel.
[email protected]
Account access, receiver commissioning and technical issues. Copy a safe diagnostic report rather than secret-bearing configuration.
[email protected]
Data-protection questions, rights requests and concerns about displayed information. See the privacy and correction pages first.
[email protected]
Potential vulnerabilities or exposed credentials. Follow the coordinated disclosure guidance before publishing technical detail.
[email protected]
Incorrect model associations, duplicated tracks or other map-data concerns. Reports are assessed against the available evidence and the Map data notice.
[email protected]
Formal notices and properly authorised requests. Protected information is disclosed only after the sender's authority and request scope have been verified.