---
title: "Share diagnostics without sharing the whole project"
description: "Share the minimum evidence that reproduces the issue: version, action, expected result and sanitized visible state."
slug: "sanitized-support-report"
category: "privacy-data"
language: en
editorial_status: published
capability_status: guide
reviewed_at: 2026-10-13
keywords: ["sanitized bug report","CueSpec diagnostics privacy","support screenshots"]
---

# Share diagnostics without sharing the whole project

Share the minimum evidence that reproduces the issue: version, action, expected result and sanitized visible state. A support report rarely needs your complete conversation history.

## Replace content, keep the behavior
Use a short invented sentence for a recognition issue and an unrelated sample image for attachment problems. If the issue depends on formatting, preserve that formatting while replacing private names or account details.

Version and system information can help identify compatibility. Review any copied diagnostic summary before posting it. Do not include credentials, login codes, signing material or unsanitized logs.

## Show the correct stage
For delivery, state whether the original conversation received the message. For task state, show the differing labels. For recording, report whether audio, a raw transcript or a refined draft appeared.

A focused report is easier to investigate and avoids presenting irrelevant private information. The community is a support entry, not a confidential storage service with an implied contractual guarantee. If you cannot sanitize a case, use the documented support contact to discuss an appropriate evidence route before transmitting the material.

## Related reading

- [Get help and report a useful issue](/get-help/)
- [Describe a bug without losing the reproduction steps](/bug-report-by-voice/)
- [Choose a language without assuming a support matrix](/language-support-boundaries/)
- [CueSpec product facts at a glance](/product-facts/)