Terms of Service

1. Scope

These terms describe use of ledgesync.com and the official LedgeSync application, maintained through the LedgeSync project repository. By using the website, you agree to the applicable website terms below. Software use, copying, modification, and distribution are governed by the software’s license. If you use the project on behalf of an organization, you must have authority to do so.

LedgeSync is not operated, endorsed, or sponsored by Google, the Apache Software Foundation, or the rclone project. Product names belonging to others remain their respective owners’ trademarks.

2. Open-source license

LedgeSync’s own code is provided under the Apache License, Version 2.0. You may use, modify, and redistribute it under that license, including its notice requirements. Third-party components retain the licenses identified in Third-Party Notices.

These website terms do not replace, narrow, or revoke rights granted by applicable open-source licenses. If these terms conflict with an applicable software license, that license controls use of the software. No trademark permission or endorsement is implied.

3. Your responsibilities

Use the application and website lawfully. Only access accounts, local folders, and cloud files you own or are authorized to use. Respect the rights of other people and the rules of your organization and service providers.

Do not use the website to attempt unauthorized access, distribute malware, disrupt the service, or misrepresent your identity. Responsible vulnerability reporting is welcome through the security reporting process.

You remain responsible for your files, account permissions, configuration, backups, and decisions about any operation. A selection preview is not a backup or proof that a transfer occurred. Review release notes and visible warnings before relying on a build.

4. Google Drive authorization

Google authorization is optional and occurs in your system browser. Google controls sign-in, consent, account availability, and the Google Drive service under its own terms and policies. LedgeSync cannot guarantee continued API access or permission for every account.

Starting with version 0.1.0-alpha.7, LedgeSync requests full Google Drive access (https://www.googleapis.com/auth/drive) so that two-way sync can see files added to a synced folder by other apps; it uses that access only for the folders you choose. Connecting does not start a sync job; syncing starts when you choose a folder to sync. A synced folder and its Drive folder change together: edits become new Drive revisions, items deleted on one side go to the Drive trash or to the folder’s .ledgesync-trash on the other side, and conflicting edits are kept as separate copies. Review deletions carefully; restore items from the trash when needed. You may disconnect locally or revoke authorization through your Google Account. Remote revocation can affect the account’s authorizations for other clients in the same Google Cloud project; review any confirmation carefully.

Our Privacy Policy explains the account information and credentials processed by the app, local storage, website data, and available controls.

5. Developer-alpha limitations and availability

Available features depend on the installed version. Alpha.3 provides local browsing, policy explanations, simulated previews and Google authorization. Starting with alpha.4, desktop and native CLI builds also support approved folder copies into a selected Google Drive destination, with verification and explicit retry after interruption. Active ignore rules apply. Starting with alpha.5, optional automatic copies run only for sync pairs you explicitly authorize, while the desktop app or a CLI command you start is running, and you can restore a copy into a new local folder. Shared-drive support, overwriting and deletion are not enabled. The website describes current downloads; unreleased source changes may not be present in installed versions.

Developer builds may contain defects or incomplete features. Some installers lack publisher signing or notarization; follow platform security guidance and the installation documentation. There is no promise of uninterrupted availability, a support response time, compatibility with every system, or delivery of planned features. Do not rely on this alpha as your only protection against data loss.

The maintainers may update the website, documentation, or available releases and may restrict abusive website access. Removing a hosted download does not revoke rights already granted under its open-source license.

6. Warranties and liability

To the extent permitted by applicable law, the website and software are provided as available, without warranties of accuracy, availability, fitness for a particular purpose, or uninterrupted operation. The software’s specific warranty disclaimer and limitation of liability are set out in its applicable license, including Sections 7 and 8 of Apache License 2.0 for LedgeSync’s own code.

To the extent permitted by law, the maintainers and contributors are not liable for indirect or consequential loss arising from use of the website or software, including loss of data or business interruption. Nothing in these terms excludes liability that cannot lawfully be excluded or limits mandatory consumer rights.

7. Changes and third-party services

Google, GitHub, Cloudflare, and other linked services operate under their own terms. A link does not imply endorsement or control over their availability or practices.

Updates to these website terms will be published here with a revised effective date and apply prospectively. Changes do not rewrite the license of software you already received. Release-specific license files remain authoritative for that release.

8. Contact

For questions about these terms or support, email the LedgeSync maintainer at alex@alexandro.net. You can also use project support. Do not post sensitive information in public issues.