Corrections and reports

1. What you can report

• a track at an impossible position or time;
• a wrong or misleading model match, label or status;
• a broadcast or public field that appears to expose personal information;
• a receiver location or account detail that should not be public;
• content that encourages harassment, trespass or unsafe action;
• suspected fabricated, replayed or manipulated observations; or
• a decision about your account or station that you want reviewed.

Use the security process for vulnerabilities or compromised credentials.

2. What to include

Email [email protected] with:

• the public track or event reference, if shown;
• the date and time in UTC and the broad map area;
• what appears wrong and why;
• a screenshot or supporting source, if it can be shared lawfully;
• whether the information creates an urgent privacy or safety risk; and
• a contact address for the outcome.

Do not send account passwords, receiver tokens, Remote ID private keys, full identity documents or unrelated packet captures. We will ask for a safer verification method if one is needed.

3. What happens next

We will triage the report, preserve relevant technical records where appropriate, and assess whether to correct a label, restrict a field, quarantine data, contact a contributor or take no action. A visible track can be limited while a credible urgent risk is reviewed.

We may not be able to disclose another user’s information, security controls or the detail of a law-enforcement request. We will provide an outcome or status where it is lawful and practical to do so, but complex cases can require external evidence.

4. Requests about personal data

If the concern relates to personal data about you, say so clearly and read the Privacy notice. We may need enough information to distinguish your request from an attempt to obtain someone else’s data. Privacy rights requests can also be sent to [email protected].

5. Evidence and enforcement

Layer400 observations are network records, not a finding that an offence occurred. We do not identify or accuse an operator from a public report alone. A competent authority seeking non-public data must use an appropriate lawful process and specify the records and time period requested.

6. Good-faith reporting

Do not submit knowingly false reports, impersonate an affected person or use this process to harass a contributor. Reasonable disagreement, an honest mistake or a report we cannot verify will not by itself be treated as abuse.