Applications, like Discord, may make deciphering user data more tedious because they aren’t using SQLite databases as the mechanism for storage. Even without the relational database structure, examining the STORE_MESSAGES_CACHE stored in the path: USERDATA/data/com.discord/files/STORE_MESSAGES_CACHE_V21, was relatively straightforward.

The image above is from a Rooted Samsung Galaxy device. Keep in mind, non-rooted Androids and non-Jailbroken iOS devices likely will not provide access to these files.

For each message, the text or image/video file is preceded by the sender’s Discord username (where @leec and @mcacevent are the two users communicating above). It is of note that for every other field of interest, (ID number, username, message body, and timestamp) the last byte is missing.

The #607 that follows @leec refers to that user’s discord user ID, which is actually 6071. The username is repeated after that minus the trailing “c”, then the message, and, finally, the timestamp.