Privacy policy for PixSync | Private Bookmark & Tab Sync
PixSync | Private Bookmark & Tab Sync by DonPedroTV
PixSync privacy policy
Last updated: 7 October 2026
PixSync does not operate a server, user account system, analytics service, or telemetry endpoint. Browser data travels directly between the extension and storage configured by the user.
Data accessed
PixSync accesses bookmarks for its core sync feature. Tabs, browsing history, and the installed-extension list are accessed only after the user enables the corresponding feature and grants the optional browser permission.
Storage and encryption
PixSync stores encrypted packets in a secret Gist owned by the user's GitHub account or, if the user chooses it, in the user's own Koofr account over WebDAV (HTTPS only). Every browser-data payload is encrypted locally with AES-256-GCM before upload. The encryption key is never uploaded. Secret Gists are unlisted rather than private in the strict access- control sense, which is why the Gist backend blocks plaintext packets.
Every device that syncs with the same storage must use the same encryption key. The setup wizard and Settings check an entered key by downloading encrypted files from the user's own storage and trying to open them locally; the key itself is never sent anywhere. On request, the wizard can also delete PixSync's sync files from that storage so the user can start over. Bookmarks in the browsers are not touched by this.
Signing in with GitHub uses GitHub's device flow: PixSync asks github.com for a short code, and the user approves it on GitHub. PixSync does not see the user's GitHub password. The resulting token is requested for the gist scope only and goes straight to the browser's extension storage. Pasting a personal access token manually is also possible.
With Koofr, the user enters their Koofr address and an app password. They are sent only to Koofr, as HTTP Basic authentication over HTTPS, to read and write the sync files.
The GitHub token, Koofr app password, encryption key, settings, sync state, and local caches are stored in the browser extension's local storage. If the user downloads the optional recovery file, it is saved only on their own device. Browser extension storage is not an encrypted vault; anyone with access to the browser profile may be able to recover locally stored secrets.
Third parties and retention
GitHub processes requests and stores the Gist under its own terms. If Koofr is used, Koofr processes requests and stores the files under its own terms. PixSync sends no data to the PixSync maintainer. The user controls retention by deleting the Gist or the files, revoking the token or app password, disconnecting PixSync, or uninstalling the extension.
Contact
Security and privacy reports can be filed at the support address: pomoc@pixalis.pl