Synchrome · Garduc

Privacy Policy

Effective date: 5 October 2026

This policy explains how the Synchrome browser companion and its macOS application handle information when you connect browser profiles and synchronize selected data across your Macs.

Who to contact

Synchrome is provided by Xavier Ramon Nicolau. Questions about privacy, support or data deletion can be sent to xavirn.me@gmail.com.

What the browser companion handles

The companion reads and applies changes only as part of connecting the selected browser profile to Synchrome. The application plans synchronized changes; the companion does not independently choose conflict resolutions. Some extension actions require an additional browser confirmation.

How information moves

The companion communicates with the installed Synchrome native connector on your Mac. It does not directly call a cloud service. Once linked, bookmark and extension information is transferred to the macOS application, which stores local synchronization state and sends selected synchronization data to the cloud service associated with your Synchrome account. Other Macs linked to your shared profiles can receive that information.

The desktop application uses Supabase services for account authentication, database and file storage. Account email, account identifiers, device and shared-profile relationships, and selected synchronization data are processed there to provide the service. Cloud transfers use HTTPS. This policy does not claim end-to-end encryption of synchronized content.

Optional desktop features

The desktop application can synchronize supported extension settings and allowlisted browser preferences when you explicitly opt in and applicable browser/version requirements are met. These features are separate from the companion's bookmark and extension inventory permissions. Synchrome does not synchronize arbitrary browser files.

Information we do not access for this purpose

The companion does not read visited-page browsing history, webpage contents, passwords, cookies or login sessions. Saved bookmark titles and URLs are processed even when they contain personal information. The companion contains no advertising or analytics code and does not download executable code.

Account passwords and cloud authentication credentials are handled by the native application and authentication service, not by the browser companion. The app stores its local authentication session in macOS Keychain. The companion's local pairing token is a separate connection credential.

Why we use information

We use this information to authenticate and maintain your selected connections, synchronize supported data, apply your requested changes, detect conflicts and provide connection status and recovery. We do not sell user data, use it for advertising or use it to determine creditworthiness.

Synchrome's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Transfers are limited to providing the disclosed functionality, complying with applicable law, or circumstances allowed by that policy. Human access to synchronized content is limited to user-authorized support and applicable security or legal requirements.

Storage and your choices

The companion keeps its pairing token and connection status locally in the browser profile. Session storage keeps acknowledged snapshot hashes; pending events exist in worker memory. The macOS application keeps its own local synchronization queue and state. Cloud synchronization records remain while needed to provide your shared profiles.

Disconnect a browser in Synchrome to stop its link. Disconnecting preserves that browser's bookmarks, profile and files. Deleting a shared Synchrome profile removes its associated cloud relationships and files through the app's deletion workflow, while retaining local browser data. Sign-out pauses synchronization on that Mac and does not itself delete cloud profiles or browser data.

You can uninstall the companion or contact us about account access, correction or deletion. Backup and security records may be subject to the service provider's retention requirements; a deletion request does not promise immediate removal from every backup. Do not send passwords or pairing tokens in support messages.

Changes

We will update this page when the data handling described here changes, and update the effective date. Material changes requiring consent will be presented before the changed feature is enabled.