Third parties that process data on our behalf when you use BugCapture. Last updated 20 July 2026.
Current
| Subprocessor | What it does | Data it holds | Location |
|---|---|---|---|
| Google Cloud / Firebase (Google LLC) | Everything: authentication, database, file storage, server functions, dashboard hosting | Account details, workspace membership, bug report metadata, screenshots and report files, integration credentials | asia-south1 — Mumbai, India |
That is the entire list. There is no analytics provider, no error-tracking service, no email provider, no AI or model vendor. Nothing you capture is sent anywhere else.
Not subprocessors: your integrations
Jira, GitHub and ClickUp receive data only when you connect them and file an issue. That transfer happens at your instruction, using a credential you supplied, to an account you control.
They are your vendors, not ours. We list them because data does travel there and you should know:
| Service | Sent when you file an issue |
|---|---|
| Jira | Title, description, QA metadata, screenshots (as attachments), a share link |
| GitHub | Title, description, screenshots (uploaded into your repository), a share link |
| ClickUp | Title, description, screenshots (attachment and an inline image URL), a share link |
Once filed, that data is governed by your agreement with them and their retention rules, not ours. Deleting a BugCapture report does not remove an issue you filed.
Planned, not yet in use
| Service | For | Status |
|---|---|---|
| A payment processor | Card payments | None in use. Upgrades are arranged by email and paid by invoice, so no card data has ever been collected, stored or processed by us. If we add a processor, card details will go directly to it and never touch our servers. |
| An email provider | Invitations and service notices | None in use. Invitations are copy-and-paste links; we send no automated email at all. |
This table will move to the list above when either goes live, with notice as described below.
Changes
New subprocessors are announced to workspace admins by email at least 30 days before they start processing data, so you have time to object or leave.