Ripplebug Privacy Policy
Last updated: July 3, 2026 · Applies to the Ripplebug browser extension and the Ripplebug Board service at board.coderippletech.com.
The short version
Ripplebug exists to move bug reports from your browser to the places you choose — and nowhere else. The extension has no analytics, no tracking, and no servers of its own. The Board service stores only what you put on it.
The extension
- Credentials (Azure DevOps PAT, GitHub/GitLab/Trello tokens, Jira/Linear API keys, Slack/Teams webhook URLs, board device tokens) are stored in your browser's local extension storage. They are sent only to the service they belong to, directly from your browser. They never touch our servers.
- Captures (screenshots, screen recordings, console and network logs) stay on your device until you file a report — at which point they are sent only to the destination(s) you selected for that report.
- Console & network capture runs via a lightweight page logger on tabs you browse; the data is kept in a small in-memory buffer and is discarded unless you attach it to a report.
- The extension contains no analytics, no ads, and no third-party trackers.
The Board service (board.coderippletech.com)
- Account data: your email address (or GitHub identity if you sign in with GitHub) and a password hash. We do not sell or share it.
- Content: captures, media files, comments, and board structure you create are stored on our backend infrastructure (Convex) so they can sync in real time across your devices.
- Guest reports: if you share a guest link, reports submitted through it (including the reporter's name if they provide one, and their browser / viewport details) are stored on your board. Guest links are revocable at any time.
- Share links: content behind a share link is visible to anyone who has the link, until you disable it.
- Send-to connections: if you connect a tracker for exporting cards from the board, those credentials are stored in the service database to perform exports on your behalf. Disconnect at any time to remove them.
Data deletion
Deleting a capture removes its media from storage. Deleting a board removes all of its content. For full account deletion, email us and we will remove your account and all associated data.
Permissions the extension requests
- Access to sites — required to screenshot the visible tab and to talk directly to the tracker APIs you connect.
- Tab capture / scripting — required for screen recording and the console/network logger.
- Storage — for your settings and drafts, locally.
Contact
Questions or deletion requests: dan.negoescu4@gmail.com