Why do I have to add a script to my website?

This is necessary to enable to key benefit of using BugHerd. Bugs logged through your website with BugHerd will have, besides the pin which points to the exact place where the issue is, a lot of additional data captured automatically which you may otherwise have to ask the user for, such as: browser, operating system. We also have browser plugins which allow the user to attach a screenshot without doing any extra work.

I have a staging and production environment. Should I create one or two projects?

It's recommended to create one project in this case since you cannot move tasks between projects. BugHerd will track which site the bug was logged on as part of the tasks's meta data.

Can I install my project's embed script on multiple websites?

Absolutely. Any site which you want to capture feedback on for your project can have the embed script. The actual site that was used will be logged as metadata with each task if you need this information.

Can BugHerd be seen by all visitors of my site or do I have control over who can give feedback?

Whichever is more appropriate for the stage your website is in. BugHerd has both an Invite Only mode and a Public mode.

What is the difference between Invite Only and using the public option?

If you choose to enable Invite Only, then your site will not display the "send feedback" widget to your site visitors and BugHerd will only be seen by people you have proactively invited.

Is BugHerd going to make my site slower?

Since BugHerd does not get loaded until after scripts start running on your webpages, it has no impact on the initial page load and a very negligible impact after that. If you are using BugHerd in Invite Only mode, then users who are not invited will get a minimal response from our server: an empty script.

Is BugHerd secure?

Yes, if your site uses encryption (HTTPS), when you embed BugHerd we will also serve our scripts, images and other assets in encrypted mode.