bug: Limit the information displayed with errors and avoid displaying internal application traces.

The current implementation includes the use of Log.e and other logging mechanisms that expose internal application traces and sensitive information. This can lead to security vulnerabilities, especially if these logs are unintentionally left enabled in production builds.

**Code Reference:**
Example from the file:

```
**java**
Log.v(TAG, "Error: exportToJson " + e.getMessage());
```
The above logs directly expose internal exception details (e.getMessage()), which could contain sensitive information about the application's internal state.

**Impact:**
Exposing internal traces could aid attackers in understanding the application's architecture and identifying vulnerabilities.
This practice violates secure coding principles by disclosing unnecessary information.