Onemark
Onemark Privacy Policy
Effective date: 2026-08-25
Onemark is a Chrome extension that organizes your bookmarks, open tabs and downloads, and can optionally sync your bookmarks across Chrome profiles through a GitHub Gist that you own.
The short version
- Onemark has no server. The developer operates no backend and receives no data of any kind from the extension, not your bookmarks, not your browsing, not analytics, not crash reports.
- Everything Onemark processes stays on your device, with one exception you control: if you enable sync, your bookmark data is written to a GitHub Gist in your own GitHub account. Create it as a secret Gist: secret Gists are unlisted, but anyone with the link can read them. Onemark never changes a Gist's visibility; it checks that visibility when you save your settings, and again on every sync, so a Gist that is made public later stops syncing too.
- Onemark contains no ads, no analytics, no tracking. The developer does not receive, sell or share your data. The only transfer that ever happens is the one you switch on yourself: with sync enabled, your bookmarks are written to the GitHub Gist you designate, which is then covered by GitHub's privacy policy.
What Onemark accesses, and why
| Data | Why | Where it goes |
|---|---|---|
| Bookmarks | The core feature: listing, editing, organizing and archiving bookmarks. | Stays in Chrome; written to your own Gist only if you enable sync. |
| Open tabs (title, URL, state) | The side panel lists your tabs and matches them to bookmarks. | Never leaves your device. |
| Recently closed tabs | The undo-close feature restores tabs you just closed. | Never leaves your device. |
| Browsing history | The history view queries recent pages when you open it. | Queried on demand, not stored, never leaves your device. |
| Downloads (file name, status) | The downloads view lists and manages your downloads. | Never leaves your device. |
| Settings | Your preferences for the extension. | Stored in Chrome's local extension storage on your device. |
Sync (optional)
Cross-profile sync is off until you configure it. To enable it you create a Gist and a GitHub personal access token in your own GitHub account, then paste the Gist ID and the token into Onemark's options page. The token is stored in Chrome's local extension storage on your device and is used only to read and write that one Gist.
Create the Gist as a secret Gist. A secret Gist is unlisted, not access-controlled: it does not appear in searches or on your profile, but anyone who has the link can read it. Onemark writes to whichever Gist ID you give it and never creates a Gist or changes its visibility. It reads that visibility at two points. When you save your settings: if the Gist is public, or if the check cannot be completed, nothing is saved and you are told why. And on every sync afterwards: if the Gist reports itself as public, that sync stops there and no bookmark data is written to it.
The developer never sees the token or the Gist. GitHub's handling of your Gist is governed by GitHub's own privacy policy. You can delete the Gist and revoke the token from your GitHub account at any time.
Data retention and removal
Uninstalling the extension removes everything Onemark itself stores: your settings, your sync token and the extension's local caches, all of which are stored locally by the extension and go away with it.
Your bookmarks are not part of that. They live in Chrome's own bookmark tree, so anything Onemark filed there stays in Chrome after the extension is gone, including the archive folders it created. Delete those folders in Chrome if you no longer want them.
If you used sync, the Gist remains in your GitHub account under your control; delete it there if you no longer want it.
Changes
If this policy changes, the updated version will be published at this same address with a new effective date. Material changes will be noted in the extension's release notes.
Contact
Questions about this policy: hello@jetto.ai