Feedback and problem reports

Last updated: 2026-10-26.

Saga uses feedback and bug reports to better understand and resolve issues faster. Because Saga processes personal data, it must be clear when context is included and who can see it.

1. Types of reports

Saga has three types of reports:

2. Chat feedback

For chat feedback, Saga may include relevant chat context, such as:

This context is only included when the user provides feedback or creates a bug report where that context is required. Saga does not include the full chat history or full user databases by default.

3. Technical error messages

Technical errors may be logged for stability, security, and error analysis. Such a report preferably includes:

Technical error reports preferably do not include full chat content, complete contact lists, calendar content, notes, photos, or attachments unless the user explicitly chooses to include them in a bug report.

4. Access

Access to feedback and bug reports is limited to persons who need it for support, error analysis, or security.

5. Retention period

Feedback and bug reports are deleted six months after submission at the next daily cleanup. This period also applies to open reports and is not extended if a report is updated or resolved. The deletion includes the description, attached chat and technical context, device data, and internal notes on the report.

This concerns the reports in the active reporting system. For any back-ups and separate security logs, the retention periods from the privacy statement apply.