how did you get that? through a sniffer and protocol analyzer?
What part of the code are you showing us here? What actions triggered this?
I don't access the information on my phone, but on an network firewall / intrusion detection system.
You would do this on your smartphone with a packet sniffer app. Or on a PC with an emulator and Wireshark, for example.
If you're interested, you're sure to find a number of json or zip(json) files there.
My screenshot is from the response to sync user attack history. But other json also contain similarly extensive facts.
In order to know which actions trigger the packet, you would have to reverse engineer the app code. I have not done that. But based on the request name, I would guess that this is either part of the login or when you tap on the envelope (because there is the defense log shown first)
Why is it so easy to view? Because it is transmitted as http (without s). Every browser would light red lights without transport encryption like TLS.
A while ago, BHG encrypted individual packets as part of an anticheat; I noticed this immediately because the ids reported a new mime type.
@BHG the solution cannot (only) be to encrypt all traffic. You should also check why you have the data, whether you really need it, whether you really need to share it with us and if not then delete it.