简体中文
EnglishDoes utterances involve tracking, ads, or lock-in?
Updated
No. According to the utterances site, the widget has no tracking, no ads, and is always free. It also has no lock-in because all comment data is stored in GitHub issues rather than in a proprietary database. These conditions apply to the hosted utterances widget as described on its site; they are not a separate promise about GitHub itself or about any third-party analytics you might add to your own page.
What “no tracking, no ads, always free” covers
The site describes utterances as a lightweight comments widget built on GitHub issues and states three related properties:
- No tracking and no ads — the widget itself does not include analytics or advertising.
- Always free — the site presents the widget as free to use.
- Open source — the code is open source, so you can inspect what it does.
These are statements about the utterances widget. They do not describe GitHub's own data practices, and they do not prevent you from adding your own analytics elsewhere on your site.
Why there is no lock-in
The key mechanism is where comments live. When utterances loads, it uses the GitHub issue search API to find the issue associated with the page, based on url, pathname, or title. If no matching issue exists, utterances-bot creates one the first time someone comments.
Because every comment is a GitHub issue in your repository, the data is not held inside a separate commenting service. The site summarizes this as “No lock-in. All data stored in GitHub issues.” In practice, that means:
| Concern | What the site says | What it implies for you |
|---|---|---|
| Tracking | No tracking | The widget does not profile readers |
| Ads | No ads | No ad slots or ad scripts from the widget |
| Cost | Always free | No paid tier is described for the widget |
| Lock-in | No lock-in; data in GitHub issues | Comments remain as issues in your repo |
A concrete example
Suppose you run a blog post at a fixed URL and add the utterances script. A reader arrives and wants to comment. utterances searches GitHub issues for one matching that page. If none exists, the bot creates an issue on the first comment. The comment then appears both in the widget and as an issue in your repository.
If you later remove the widget, those issues still exist in GitHub. That is the practical meaning of “no lock-in”: the conversation is not trapped in a vendor's database.
What to check before relying on these claims
- Commenting requires GitHub authorization. To comment through the widget, users must authorize the utterances app to post on their behalf via the GitHub OAuth flow. Alternatively, they can comment on the GitHub issue directly. So “free” and “no tracking” do not mean “no account needed to comment.”
- Your repository settings matter. Because comments are issues, the visibility and permissions of your GitHub repository affect who can read and write comments.
- The claims are the site's own. The page states these properties; it does not publish a separate audit. If tracking or cost is a hard requirement, verify against the current site and your own setup rather than treating this as a guarantee about every deployment.
In short: utterances itself is presented as ad-free, tracking-free, free to use, and not lock-in, with the lock-in answer resting on comments being stored as GitHub issues in your repository.