HeSync is a privacy-focused sync extension for the Helium Browser.
It stores your sync data in your own private GitHub repository and protects it with end-to-end encryption using AES-GCM. Data is encrypted before upload and only decrypted locally with your recovery key.
- End-to-end encrypted sync
- Private GitHub-backed storage
- Local decryption with a generated recovery key
- Bookmark sync
- Browser history sync
- Auto sync at startup
- Auto sync every 5 minutes
Note
History sync is still experimental and may still have a few bugs.
- Start a new sync chain or join an existing one.
- Save your recovery key.
- Add your GitHub token.
- HeSync encrypts your sync payloads and uploads them to your GitHub repo.
- Other Helium installs can sync by using the same recovery key.
Your GitHub repo stores encrypted payloads. The recovery key is required to decrypt them locally.
- Download the latest release from the Github releases page on the right.
- Extract the zip somewhere on your machine.
- Open your Chromium extensions page (web link chrome://extensions).
- Enable
Developer mode. - Click
Load unpacked. - Select the extracted HeSync folder.
- Clone or download this repository.
- Open your Chromium extensions page (web link chrome://extensions).
- Enable
Developer mode. - Click
Load unpacked. - Select this project folder.
After loading the extension:
- Open HeSync from the toolbar popup or settings page.
- Choose
Setup New Sync ChainorJoin Existing Sync Chain. - Save the recovery key somewhere safe.
- Add your GitHub token.
- Finish setup and let HeSync perform the first sync.
Important
If you lose your recovery key, you lose access to the encrypted sync data stored in the repo.
Create a GitHub personal access token and grant these repository permissions:
Contents: Read and writeAdministration: Read and writeif you want HeSync to create the private repo automaticallyMetadata: Read-only
If you create the sync repo yourself first, Administration is not required.
- Sync payloads are encrypted before they leave the browser
- GitHub stores encrypted data, not plain bookmark or history data
- Decryption happens locally using your recovery key
- Your GitHub token is stored locally in extension storage on your device
