Issue Reporting Terms

Effective date: February 8, 2026
Last updated: March 27, 2026

This document explains the terms that apply when you submit an issue report through the FretPulse Engine (the "Service"). To report a security vulnerability specifically, see the Vulnerability Disclosure Policy instead.

1. Accuracy of Reports

When you submit an issue report, you confirm that the information you provide is accurate to the best of your knowledge. You should describe the issue in good faith and avoid intentionally false, misleading, abusive, or duplicate reports.

2. Attachments and Permissions

If you attach screenshots, logs, audio files, or other materials, you confirm that you are authorized to share them with the Service for support and diagnostic purposes. Do not attach materials that you do not have the right to disclose.

3. Security Review of Attachments

Attachments may be validated, temporarily quarantined, and malware-scanned before they are made available for internal review. Files that fail validation or are flagged as unsafe may be rejected or deleted.

4. Support and Diagnostic Use

Issue reports and their attachments are used only for support, troubleshooting, abuse review, security review, and service improvement. They are not submitted for public display through the Service.

5. Contact and Follow-Up

We may review your report and contact you using your account email address if we need clarification, more context, or confirmation that an issue has been resolved.

6. Retention

Issue reports and related materials may be stored for a limited period to investigate, resolve, and audit support activity. Retention details are described in the Data Retention policy.

7. Abuse and Misuse

We may limit, reject, or investigate issue-report submissions that are abusive, automated, fraudulent, malicious, or otherwise inconsistent with the Acceptable Use Policy and the security of the Service.