Guide
Vendor-safe File Sharing Workflow
Prepare files, screenshots, JSON, logs, and extracted text for vendor support without exposing unnecessary private data.
Last updated: 2026-07-27
Define the support question
Before sending files to a vendor, write the exact problem in one sentence. A clear question helps you choose the smallest useful sample instead of attaching a full export, full email thread, or full production payload.
Remove unrelated records
If one row, one document section, or one API object demonstrates the issue, use that sample. Keep enough structure to reproduce the problem, but remove unrelated customers, messages, pages, and attachments.
Redact by category
Look for names, emails, phone numbers, addresses, account IDs, tokens, internal URLs, timestamps tied to customers, and private notes. Replace values consistently so the vendor can understand relationships without seeing the real data.
Preserve technical shape
A sample must remain useful. JSON should still validate, CSV columns should remain present, timestamps should keep their original units, and filenames should remain representative if the bug depends on naming.
Keep a review note
Document which fields were removed, which values were converted, and which tool produced the output. This helps the vendor interpret the sample and helps your team audit the sharing decision later.
Use secure channels for necessary secrets
Sometimes support legitimately needs a request ID or account identifier. Share sensitive values only through the vendor's approved secure channel and avoid posting them in public forums, screenshots, or chat threads.