Flutter Security

Use Ansight only in approved development variants and on a trusted local network. Enrollment uses clear-text UDP and ws://.

• Guard initialization with kDebugMode or an explicit developer flavor.
• Keep tool access deny-all in protected builds.
• Prefer read-only tools.
• Do not place enrollment payloads in Dart constants or public assets.
• Configure only the native QR and local-network privacy descriptions the app actually needs.
• Revoke a registration in Studio or clear app data when the installation should no longer reconnect.
• Keep cellular host connections disabled unless the workflow intentionally uses mobile data or a personal hotspot.
• Treat Dart/native crash messages, stacks, breadcrumbs, and metadata as sensitive. Disable crash capture or handoff when policy requires it.

Native crash reports are bounded and stored in app-private files until delivery or expiry. See Crash Capture.