Feedback, Error Reports and Privacy

Send feedback

You can send suggestions, bug notes, or questions directly from inside the application. The composer sheet validates character limits live against the server's validation rules and posts straight to our server.

Only what you type into the feedback sheet, along with your application version and operating system platform, is submitted. Your documents are not.

Error reports and crash prompts

If a critical failure occurs, Tessamark does not quietly send diagnostic dumps behind your back. When the Enable Crash Reporting switch is on under Settings → Privacy (in Section Telemetry), the app presents an error review sheet.

You can review the error message, type an optional description of what you were doing, and choose Send Report or Don't Send. If you dismiss it, nothing is transmitted.

What an error report contains

Error reports contain only diagnostic metadata and technical error details. No personal data is sent. Only the message and system/app version info are included, consisting exactly of these fields from the core error report struct:

• report_id: unique generated identifier (such as mde-<hex timestamp>).
• timestamp_unix: Unix epoch seconds when the error occurred.
• error_type: error classification (for example, IoError, SwiftException, or SignalCrash).
• error_message: sanitised error string, stripped of document content and keys.
• stack_trace: optional stack trace if captured.
• app_version: application release version string.
• os_info: operating system name and version (such as macOS 15.1 or iOS 18.0).
• user_description: optional text you typed into the report prompt.
• component: originating subsystem (rust_core, swift_ui, or monaco_editor).

Privacy principles

Tessamark is built on one simple rule: we cannot read what we never hold. There are no tracking pixels, no advertising analytics, and no third-party trackers on our website or inside our apps.

Read our complete commitment on the Privacy Policy page.