TrendAI Breach Protocol app privacy
Updated October 26, 2026 · Android, iPhone and iPad companion apps
TrendAI Breach Protocol supports organized cybersecurity simulation events. This notice describes the companion app and its connected event service. The TrendAI corporate privacy policy provides further information about privacy rights and contact options.
Event and account information
Team stations send an installation identifier, app version, station and team names, enrollment and pairing information, display state, and simulated exercise responses to the Breach Protocol service. The service uses these details to authorize the station, synchronize the exercise, process responses, and show results. Hosts can see their event’s station and team information.
Host Mode opens the TrendAI web console in a browser session. TrendAI SSO supplies the host’s work name, email address and account identifier. The service uses that identity and event assignments to control access. The app does not ask for a staff password. Participants use a separate phone interface for their individual roles and decisions.
QR scanning on Android
Android QR scanning uses Google Code Scanner through Google Play services. Camera image processing occurs on the device; Google states that it does not store scan images or results. The app sends the enrollment grant from the selected QR to the event service so it can authorize the station.
Google’s scanner SDK collects device and app information, installation or device identifiers, performance metrics, configuration, feature events and error codes for diagnostics and usage analytics. Enabled auto-zoom also supplies scan-session and zoom metadata. The app includes no advertising SDK or advertising identifier permission. See Google’s SDK data disclosure and Code Scanner documentation.
Security and retention
App API requests use HTTPS. Android station credentials are encrypted on the device using Android Keystore; iOS station credentials use Keychain. Host authorization and exercise results are controlled by the server. Enrollment and device access can expire or be revoked by the event host. Avoid including real passwords, confidential incident details or other sensitive information in simulated exercise responses.
Event access and event data normally expire 30 days after the scheduled start. Historical performance statistics can be retained when historical tracking is enabled. Staff account records and operational records have separate retention. Google handles scanner SDK data under its applicable terms and privacy practices.
Access, removal and support
Ask your event host to revoke a lost station or remove event information. Changing teams detaches the station from its team. Choosing Scan another QR clears its stored station credential; host revocation or expiration also clears it when detected. Uninstalling the app does not by itself delete server records. To request deletion or discuss the data associated with an event, email breachprotocol@trendaisecurity.com. Identify the event and the request, and do not send passwords, pairing links or QR codes. Staff SSO accounts are managed by the organization; this app does not create a separate self-service account.