Privacy
I don't look at your code.- bugsTweet never gets access to your app's code.
- Nothing leaves the phone until the tester taps Send. Passwords and private fields are blurred first.
- The service keeps no copy of reports or pictures. “Delete my account” removes everything at once.
Leaves the phone, when the tester taps Send
- The note.
- The marked-up pictures, private fields already blurred.
- The facts the report holds: the taps, the screen names, the phone facts.
Never leaves the phone
- Your app's code. bugsTweet never gets access to it.
- Passwords, and any part the developer marks as private: blurred before a picture leaves.
- Anything at all, until the tester taps Send.
Your code stays yours
bugsTweet never gets access to your app's code. Reports go to a separate, private reports repository, and there the bugsTweet service allows only its own actions: post a report, comment, close or reopen, add a picture.
On the tester's phone
Nothing leaves the phone until the tester taps Send. The first time the app opens, the tester is asked before bugsTweet keeps small pictures of the last 30 seconds and the last 30 taps. Password fields, and any part the developer marks as private, are blurred before a picture leaves the phone, and the developer can also hide text such as email addresses. Store builds never contain bugsTweet; only tester builds do.
What reaches GitHub
Each report becomes an issue in the developer's reports repository on GitHub: the note, the marked-up pictures, and the facts the report holds. The report and its pictures then stay in that repository and its history, and in any copy an AI agent downloads. Anyone who can see that repository can see the reports, which is why bugsTweet picks a private repository and warns before reports go to a public one.
What the bugsTweet service sees
It depends on how reports are sent. With your own GitHub key or your own relay, reports go straight from the app to GitHub or to your relay; they never pass through the bugsTweet service. With Pro, each report passes through api.bugstweet.com on its way to GitHub. The service checks the key, the plan and the repository, and reads the report's facts (taps, screen names, marks and app facts, already cleaned by the developer's hiding rule, never pictures) to write the Pro parts. It takes those facts out before the report reaches GitHub, and keeps no copy of the report, its text or its pictures.
What the service keeps
For each developer who signs in, the service keeps only what it needs to work: the GitHub account number and name; the names of the repositories bugsTweet is installed on; each project's app name, reports repository, plan and settings; and simple counters, such as how many reports were sent this hour. For Pro projects, it also keeps two lists from the latest tester build: the app's widget names with their file and line, and the names of the code files that changed since the tester build before, with that build's commit. Names and places only, never code. Each new build replaces both lists, and deleting the project deletes them. Keys and sign-ins are kept only as scrambled fingerprints, never the key itself. bugsTweet keeps no logs and no IP addresses. “Delete my account” on api.bugstweet.com removes all of it at once.
Who else helps
bugsTweet uses a few services to work, each under its own privacy policy. GitHub stores the reports, in your own repository. Cloudflare runs this website, the bugsTweet service, and the @bugstweet.com email addresses. Paddle, our reseller, handles payments for Pro; we never see your card. Google Fonts serves the website's fonts, so your browser asks Google for them.
Your choices
You choose how much goes through bugsTweet. With your own GitHub key or your own relay, nothing passes the bugsTweet service. Testers can say no when the app first asks to keep the last 30 seconds. The developer can hide text, such as email addresses, before a report leaves the phone. You can remove the bugsTweet GitHub App from a repository at any time in your GitHub settings. “Delete my account” on api.bugstweet.com removes everything the service keeps, at once.
This website, changes, and contact
bugstweet.com sets no cookies. Cloudflare Web Analytics counts visits to its pages without cookies and without following you to other sites. Signing in at api.bugstweet.com uses cookies only to sign you in safely and keep you signed in; none of them track you. If we change this page, we post the new version here with its new date. For questions about privacy, or a request about your data, write to support@bugstweet.com.
Questions? Write to us, we answer in plain English too.