Bark Privacy Policy
Last updated: 2026-06-19
Bark is a Chrome extension that renders the changed Markdown files of a GitHub Pull Request and lets you review them with comments and Suggestions, similar to Google Docs. This document explains exactly what data Bark handles and where it goes.
Summary
- Bark has no backend server. The developer operates no servers and receives no data from you whatsoever.
-
Bark talks to GitHub only (
github.comandapi.github.com) to read the Pull Request and to create or update your reviews, comments, and Suggestions. - Everything Bark stores — your GitHub access token and any draft (pending) comments — is kept locally in your browser and is never transmitted anywhere except to GitHub's own API on your behalf.
- Bark contains no analytics, no tracking, no advertising, and no third-party network calls. It uses no remote fonts or remote code.
What data Bark handles
GitHub authentication token
To act on your behalf, Bark authenticates you through GitHub's official
GitHub App device flow. You authorize the app on
github.com and choose which repositories Bark may access. GitHub then issues a
user access token.
-
The token is stored in
chrome.storage.local(local browser storage) on your device. -
It is sent only to
api.github.com/github.comin the standardAuthorizationheader to perform the actions you request (reading the PR, posting comments, submitting reviews, etc.). - It is never sent to the developer or any third party.
Draft (pending) review content
Comments and Suggestions you draft before submitting are saved locally in
chrome.storage.local, keyed by Pull Request, so you can continue a review
later. When you submit a review, that content is sent to GitHub and becomes part of the Pull
Request. Drafts never leave your browser until you submit them to GitHub.
GitHub content you view
When you open a Pull Request in Bark, Bark fetches the PR's metadata, the changed Markdown files, and existing review comments from GitHub's API to render them. This content is processed in memory in your browser and is not collected, retained off-device, or shared by the developer.
Where data goes
| Data | Stored | Sent to |
|---|---|---|
| GitHub access token | chrome.storage.local (your browser) |
github.com / api.github.com only |
| Draft comments & Suggestions | chrome.storage.local (your browser) |
github.com / api.github.com only (on submit) |
| PR content you review | In-memory in your browser | Not sent anywhere by Bark |
Bark's network access is restricted by its manifest to
https://github.com/* and https://api.github.com/*. It cannot send
data to any other host.
Data the developer collects
None. The developer does not collect, store, sell, or share any of your data. Bark has no telemetry and no servers.
Permissions
-
storage— to keep your token and draft comments locally on your device. -
scripting— to add the "Open in Bark" entry point on GitHub Pull Request pages. -
Host access to
github.comandapi.github.com— to read the Pull Request and submit your reviews to GitHub.
Removing your data
- Your local data (token and drafts) is removed when you sign out in Bark or when you remove the extension / clear the extension's storage in Chrome.
- Content already submitted to GitHub lives in your GitHub account; manage or delete it there. To revoke Bark's access entirely, remove the authorization from your GitHub Settings → Applications.
Children
Bark is a developer tool and is not directed at children under 13.
Changes to this policy
If this policy changes, the updated version will be published at the same URL with a new "Last updated" date.
Contact
Questions about this policy can be sent to contact@nownabe.dev.