Feedback & Privacy
The feedback system is designed for useful bug reports without uploading your JSON payloads.
Report an Issue
Click the Report issue bug icon in the workbench header. The dialog lets you describe the problem and optionally include safe diagnostics.
Safe diagnostics can include:
- Current route.
- Browser and operating system.
- App version metadata when available.
- Theme and viewport details.
- Error message and stack summary when a crash is detected.
Safe diagnostics do not include:
- JSON, YAML, XML, CSV, Mermaid, or JFDG source content.
- Query result data.
- Workspace file contents.
- Secrets, tokens, cookies, or local storage values.
Crash Reports
Automatic crash reports are off by default. If you enable them in Preferences > Privacy, JSONFiddle can send a safe error summary when a recoverable app error happens. The goal is to capture what broke without capturing the data you were working on.
If a bug depends on a specific payload, create a reduced sample or synthetic payload before sharing it.
Where Feedback Goes
Submitted reports are stored in JSONFiddle cloud storage and can trigger an admin notification email when email integration is enabled.
The feedback pipeline is separate from workspace save and share snapshots. Reporting an issue does not save your workspace or upload source files.
Raw browser user-agent strings are minimized before storage. JSONFiddle stores browser and operating-system labels plus a short hash for dedupe, not the full raw user-agent header.
For deployments, admin notifications can be sent through SMTP (SMTP_HOST, SMTP_USER, SMTP_PASSWORD) or an optional Resend fallback. Keep these values server-only in Vercel environment variables; never expose SMTP passwords or service-role keys through NEXT_PUBLIC_ variables.
Good Bug Reports
Helpful reports include:
- What you were trying to do.
- Which view or tool was active.
- The smallest safe sample that reproduces the issue.
- Whether it happens in a fresh browser tab.
- A screenshot if the problem is visual.
Avoid adding production payloads, API tokens, customer records, or credentials.