Since /e/-Message is a fork of qksms, it includes the Bugsnag Tracker. In my opinion, by forking qksms /e/ gets responsible for collecting user data by bugsnag. So, there has to be some questions worked out:

• Is bugsnag still activ?
• if it is, does qksms or /e/ receive the data?
• if it is active, either way, collecting user data must have been in the privacy policy.(https://www.iubenda.com/privacy-policy/8072595)
• Best solution, but the most work: remove it from Message.

Bugsnag usage in the code: https://gitlab.e.foundation/search?utf8=%E2%9C%93&search=bugsnag&group_id=&project_id=282&search_code=true&repository_ref=master