ARTEMIS credentials and operational information can be sensitive.

Never include any of the following in a public GitHub issue, discussion, screenshot or HAR file:

• ARTEMIS username or password;
• CAS tickets;
• JSESSIONID, MOD_AUTH_CAS_S, CASTGC or other session cookies;
• the ssoSha1 hand-off value;
• personal information about firefighters;
• addresses or details of active operations unless they have been fully anonymised.

If credentials were accidentally included in a HAR or issue, invalidate the session and change the password immediately.

Do not open a public issue containing exploit details or credentials. Contact the repository owner privately through the security contact configured on GitHub, or use GitHub Private Vulnerability Reporting if enabled.

This integration is intended to use only data that the configured ARTEMIS account is already authorised to access. It does not attempt to bypass authentication, access controls, TLS protections or other security mechanisms.

Version 0.2.0 adds an optional one-button personal status cycle. This is a real write to ARTEMIS, not a Home Assistant-only helper. The implementation is intentionally limited to the authenticated user, the IND / DI1 / AS1 cycle, and the preserved next planned status boundary. Do not expose the button or its notification action to untrusted Home Assistant users.

artemis_new_intervention and artemis_intervention_update can contain operational addresses, resource names and states. Treat Home Assistant event traces, automation traces, logs and notification history as sensitive operational data.