Limiting HTML report generation with Gatling’s --no-reports flag

When running Gatling simulations, teams often enable the --no-reports flag to prevent the automatic creation of the HTML report directory and reduce the chance of exposing test results through a misconfigured web server.

The flag is known to suppress the target/gatling folder while still writing the simulation.log file, but it is unclear whether other artifacts such as stored request/response bodies (via storeBody) are also omitted, and whether the log file retains full request/response payloads that could constitute a data leak.

Does --no-reports affect the generation of stored request/response bodies? Is the simulation.log produced with the same level of detail as when reports are enabled? Are there additional configuration options needed to fully sanitize or disable these artifacts when report generation is turned off?