Email admin@bugdump.com.
That address reaches us for anything: technical problems, billing, account questions, feature requests, or security reports.
What to include
A message with these takes one reply instead of four:
Your project slug — the identifier in your dashboard URL
What you expected, and what happened instead
The exact error, if there was one, copied from the browser console rather than described
Your plan — Free, Pro, or Ultra, since several limits differ by plan
The task's public ID (
#42) if your question is about a specific bug
For SDK problems, the configuration you passed to Bugdump.init() — with the API key removed — is usually the single most useful thing you can send.
Reporting a bug in BugDump itself
Use the widget on our own site. It captures the console, network log, and session replay from your session automatically, which is considerably better evidence than a description.
That is, after all, the entire premise of the product.
Security issues
Email admin@bugdump.com and say clearly in the subject that it is a security report.
Please do not open a public issue or post details anywhere public until we have had a chance to respond.
If you believe a widget key or an MCP token has leaked, or see a connected app you do not recognize, revoke the key or disconnect the app first (account settings → Security → Connected apps) — that is faster than any reply we can send — and then get in touch. See Managing API keys safely for what each one exposes.
Feature requests
Send them to the same address, or use the feedback board where one is available for your project.
Requests describing the underlying problem land better than ones naming a solution. "I need to know which build a report came from" tells us more than "add a version field", and in that particular case the answer already exists — setContext({ buildSha }).
Billing
Billing runs through Paddle. For invoices, payment methods, refunds, or plan changes, email us with your account email and what you need.
Upgrades take effect immediately, so if a project has stopped accepting reports because it hit its limit, upgrading fixes it faster than waiting on a reply.
Faster than emailing
A good share of questions are already answered:
Question | Where |
|---|---|
Something is broken | |
What does my plan include? | |
Which key do I use where? | |
How do I install it in React/Vue? | |
What can this SDK method do? | |
How do I keep data out of reports? |
The help center search covers all of it.
See also
Troubleshooting
Plans, limits, and usage