> ## Documentation Index
> Fetch the complete documentation index at: https://learn.biq.li/llms.txt
> Use this file to discover all available pages before exploring further.

# Report messages and understand moderation

> Submit a message or conversation report, understand saved evidence and review possible outcomes.

Report received content when you believe it violates Biqli's rules. Reporting requests review; it does not automatically establish a violation, remove content or block the other participant.

## Submit a report

1. Open the received message's actions and choose the report action. On touch devices, press and hold the message.
2. For a whole-conversation report, use **Report conversation** in the main conversation-options menu.
3. Choose the category and explain the concern clearly, using 10 to 3,000 characters.
4. Review the evidence disclosure.
5. Submit and wait for confirmation.

You cannot use this flow to report your own outgoing message. Explain the issue honestly and avoid including unrelated sensitive information in the report reason.

The public Biolink chat omits the conversation-options header menu, but received messages retain reporting actions. Whole-conversation controls are available through the main Messages interface where supported.

## Evidence shared for review

A message report can include that message and up to two preceding and two following messages. A conversation report captures up to 20 recent messages. Available context can include both participants' messages and recordings.

This is a saved snapshot for authorized moderators. It is not permission for unrestricted browsing of your live inbox. Deleting or editing the original later does not rewrite the captured evidence.

## Retention and unresolved reports

* An unresolved report is flagged for staff attention after **30 days**.
* At **90 days from submission**, it closes as **Expired without review** unless an administrator documents an extension. Each extension sets a later deadline no more than **90 days from the extension date**. Appending new messages does not restart the original deadline.
* Expiry is not a dismissal, rejection of your concern or clearance of the reported content. The outcome email explains that no review was completed.
* Captured message content, recordings and reporter notes remain while the case is open and for **90 days after review or unreviewed closure**, then are erased by scheduled cleanup.
* Limited moderation history remains for **12 calendar months after closure or the end of the case's restriction or suspension, whichever is later**. An early lift uses the actual lift date.
* An active account suspension can retain a minimal enforcement record while it remains active, with annual necessity review. Unnecessary reporter, conversation and evidence information is removed.
* A documented legal obligation, lawful preservation request or actual dispute can preserve necessary remaining case records. Legal holds have a review deadline of **90 days**, with overdue reviews flagged for staff attention. Continuing a hold requires a documented necessity review. They pause erasure, not the unresolved-review deadline. Releasing a hold resumes the original deadlines without starting a new retention period.

Evidence cleanup and backup retention are separate. A later hold cannot restore evidence already beyond its ordinary access cutoff. For the full policy and privacy-request route, see [Data retention](https://biq.li/privacy#data-retention).

## Repeat reports

Trying to report already reported content shows an explanatory toast instead of reopening the form. Reporting new received content in the same conversation can add evidence and your explanation to an existing open report.

That confirmation is not a new moderation decision. Context messages included around a target are distinct from messages specifically marked as reported. If a report reaches its evidence limit, follow the displayed instruction.

## Review outcomes

Biqli can dismiss the report, remove reported content, impose a temporary account-wide messaging restriction or suspend an account when appropriate.

A messaging restriction prevents sending or starting conversations while allowing supported history reading, blocking and reporting. Independent active restrictions can overlap; the latest applicable expiry controls when messaging resumes. Lifting one restriction does not lift another.

Full suspension also affects login and other account access. Unblocking a conversation does not reverse suspension.

## Notices and review requests

The reporter receives a general outcome. The affected account receives applicable enforcement details, including the reason and restriction timing. We do not routinely include the reporter's identity in the affected user's decision email, but cannot promise absolute anonymity or prevent inferences from context.

For an enforcement review request, contact [Biqli support](mailto:contact@biq.li) with the report or decision reference. There is no promise of an automatic exemption. Moderation notices are separate from optional unread-message emails.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.