Where your users' feedback goes
A hosted feedback tool works by receiving what your users report (screenshots, logs, the page they were on) on its own servers. That's the design, and each of these vendors says so openly. Here's where, in their own words, with a link to each source.
Checked 24 September 2026 against each vendor's published pages. Something out of date? Write to [email protected] and we'll correct it.
Comparison
| Tool | Where reports are stored | Console and network capture | Self-hosted option | DPA and subprocessors |
|---|---|---|---|---|
| Marker.io | Vendor's cloud: AWS, eu-west-1 (Ireland) source | Yes, through its SDK source | Not published | DPA source; subprocessor list source |
| BugHerd | Vendor's cloud: Heroku on AWS, us-east-1 (N. Virginia) source | Not published | Not published | DPA on request; subprocessor list source |
| Userback | Vendor's cloud: AWS, United States source | Yes source | Not published | DPA source; subprocessor list source |
| Jam | Vendor's cloud: Google Cloud, Central US source | Yes source | No: recordings can't be sent to your own storage source | DPA in its terms source; subprocessor list source |
| FasterFixes | Hosted tier: EU, Frankfurt source | Yes source | Yes, free: run its dashboard, database and storage yourself source | DPA not published; a short list of services in its privacy policy source |
| quibble | Your issue tracker. quibble runs inside your app and has no servers details | Yes, off until you turn it on details | Nothing to host: it's a package in your app and a script tag | No additional DPA or subprocessor: quibble never receives your data |
Every row is a statement the vendor publishes. Where we couldn't find one, it says not published, which means we didn't find it, not that it doesn't exist. Plans and features change; the linked pages are the authority. The evidence behind this table is kept with the site's source.
Rather keep it in your own tracker?
quibble is in early access. See it work first, or write to [email protected].