Share useful diagnostics without sharing your notes
Review the exact fields before choosing to send technical context.
Begin with a concise description
Describe the task, platform, observed state and what you already tried. You can contact support without uploading diagnostics or supplying private note content.
Use a structured, reviewed payload
Useful candidates include app build, OS, installation channel, stable error category, correlation identifier, queue count or age, protocol version and a coarse key-unavailable state. The exact allowlist needs implementation and privacy review.
Inspect before sending
Read the payload and omit fields you do not want to share. Exclude note text, titles, filenames, paths, attachment contents, keys, recovery secrets, authentication tokens, raw URLs and memory dumps. Ordinary debug logs are not automatically safe.
Keep control of exceptional evidence
An unusually revealing artifact needs a specific explanation and explicit consent, with restricted handling. It should not become a routine request for private notes or secrets. Diagnostics belong to support operations, not acquisition analytics.