ComplyEaze Bridge Terms of Use

Version: 2026-10

Effective: 2 October 2026

Applies to: ComplyEaze Bridge builds that include or link to these Terms (starting with the first build that asks you to accept them), and any Bridge-related service we provide.

1. Agreement

1.1 These Terms of Use ("Terms") are an agreement between you and SPMS Comply Eaze Solutions LLP, a limited liability partnership registered in India ("ComplyEaze", "we", "us", "our"). Our registered office is at S-137, 1st Floor, Sunsquare Shopping Plaza, Plot No. SPL-1/J, RIICO Chowk, Bhiwadi Industrial Area, Bhiwadi, Tijara, Alwar 301019, Rajasthan, India.

1.2 You accept these Terms by ticking "I accept" where a Build asks you to, or by installing or using a Build that includes or links to them. If you do not accept them, do not use Bridge.

1.3 The ComplyEaze Bridge Privacy Policy explains how information is handled when you use Bridge. It is a notice, not part of these Terms.

1.4 If you use Bridge for a firm, company or other organisation, you confirm that you are authorised to accept these Terms for it. "You" then includes that organisation. You must be at least 18 years old and legally able to enter into a contract.

2. Words we use

Tally, Tally Data, AI Assistant, AI Provider, Local Files, Personal Data and Clients have the meanings given in section 2 of version 2026-10 of the Privacy Policy.

3. What Bridge is, and what it is not

3.1 Bridge is software that lets an AI Assistant on your computer read Tally, and prepare voucher files. If you turn posting on, it can also post vouchers into Tally after you approve them, one at a time or, where a Build allows, as an approved batch.

3.2 Bridge is not:

• a product of, or endorsed by, Tally Solutions Pvt. Ltd., Anthropic, any other AI Provider, the GST Network, the CBIC, the Income Tax Department, the Institute of Chartered Accountants of India, or any government body;
• accounting, tax, audit, legal or financial advice (section 10);
• a payment or banking service. Bridge records vouchers in your Tally books; it does not move money or make payments;
• a backup or archive of your books. The Local Files it keeps let you check its own actions. They do not replace your records or backups.

4. Releases and what has been tried

4.1 We check each release before we publish it: the release check confirms that each package launches, lists its tools and parses a synthetic encrypted bank statement. It does not run against TallyPrime, and nothing we can run covers every Tally edition, set of books or setting. Not yet run by us in a controlled test against a real TallyPrime: posting with a published package against a live TallyPrime; the approval window on Windows; posting on TallyPrime Education; posting on TallyPrime Gold with its approval step recorded. What has been run, on which Tally edition and operating system, is listed in the README and each release's notes. Builds are not signed with a verified publisher identity or notarised, so your operating system may warn you before opening them. The extension is published for Windows x64 and Apple Silicon Macs; other platforms are not supported. No installer for the desktop app is published.

4.2 Bridge is still being developed. A release may contain errors, may behave differently between versions, and may be changed, suspended or withdrawn. Some behaviours have been checked only on particular Tally editions and versions, and on particular operating systems. The known limits of each Build are described in the documentation and release notes published with that Build. Bridge refuses some books and requests that it cannot handle reliably.

4.3 Use a new release on real books only after you have tried it on test data and are satisfied with it, and only with current backups (section 8).

4.4 We are not obliged to provide support, updates, security fixes, new versions or anything shown on a roadmap, or to keep any feature available.

5. Licence

5.1 Source Code and Builds. The Source Code is licensed under the Apache License, Version 2.0 ("Apache Licence"). Official Builds are provided to you under the same licence. Third-party components in Bridge are licensed under their own terms. These are listed in the NOTICE and third-party licence files included with the Source Code and each Build.

5.2 What these Terms do not change. Nothing in these Terms limits any right the Apache Licence gives you in the Source Code or a Build. If these Terms and the Apache Licence conflict about your rights to use, copy, modify or distribute the software, the Apache Licence governs. The Apache Licence's own disclaimer of warranty and limitation of liability (its sections 7 and 8) apply in addition to sections 13 and 14 of these Terms.

5.3 Modified builds. You may modify and redistribute Bridge as the Apache Licence allows. A build that is modified, or that is not an Official Build, is not provided by us. We are not responsible for it. It must not be presented as an Official Build or as provided by ComplyEaze (section 6).

6. Our names and logos

6.1 ComplyEaze, ComplyEaze Bridge and the related names, logos and product marks are the names and marks SPMS Comply Eaze Solutions LLP uses to identify its products. They are not registered trade marks. The Apache Licence does not grant permission to use them, except to describe where the software came from and to reproduce the NOTICE file (Apache Licence, section 6). These Terms grant no further right, except as section 6.2 allows.

6.2 You may:

• refer to ComplyEaze Bridge by name to describe it accurately, for example to say that your software works with it; and
• reproduce the NOTICE file and describe where the software came from, as the Apache Licence requires.

Otherwise, you may not use our names or logos in a way that suggests we made, endorse, support or certify something we did not, or that confuses people about who runs a website, build or service. A fork or modified build must use a different name, must not use our logos, and must show clearly who maintains it.

6.3 Tally, TallyPrime and related marks belong to Tally Solutions Pvt. Ltd. Claude and related marks belong to Anthropic. Other marks belong to their owners. We use them only to describe compatibility.

7. Software and services that are not ours

7.1 To use Bridge, you need software and services that we do not provide or control. These include Tally, your AI Assistant, your AI Provider and your operating system. Each is governed by its own terms. You are responsible for any licence or subscription they need, and for any fees they charge.

7.2 You are responsible for making sure your Tally licence and Tally's terms permit your use of Bridge with Tally. The same applies to your AI Assistant's and AI Provider's terms.

7.3 We are not responsible for the availability, behaviour, security, outputs or data handling of any third-party software or service. This includes how your AI Provider stores or uses what your AI Assistant sends it. A change to third-party software, such as a new Tally release, may stop Bridge working.

8. Your responsibilities

You are responsible for:

a. Authority. Having the right to access each Tally company you connect Bridge to. Where the books belong to a Client, you need the Client's authority to do so and to share their data with your AI Provider.

b. Data protection and confidentiality. Complying with the law that applies to you and to your Clients' data, including the Digital Personal Data Protection Act, 2023 where it applies. This includes any professional duty of confidentiality that applies to you, such as under the Chartered Accountants Act, 1949 and your professional body's code of ethics.

c. Your settings. Choosing whether to turn on posting and which masking setting to use, and choosing your AI Provider and its settings.

d. Backups. Keeping current, tested backups of your Tally books before you turn posting on, and regularly while it is on.

e. Checking results. Checking any figure, report or voucher from Bridge or your AI Assistant against Tally and the underlying records before you rely on it. This applies especially before you use it in advice, a filing, a report to a Client or a posting.

f. Security. Keeping your computer, your Tally installation, your AI Assistant account and your Local Files secure. Download Builds only from the Official Release Page or the Bridge website, and check their published checksums.

g. Your firm. Making sure anyone who uses Bridge on your behalf follows these Terms.

9. AI assistants, posting and approvals

9.1 AI output can be wrong. Your AI Assistant decides which Bridge tools to use and how to read the results. It can misread figures, pick the wrong company, period or ledger, leave things out, or state things that are not true. Bridge reports some limits and refuses some requests. It does not check your AI Assistant's reasoning or conclusions.

9.2 Posting. Posting is off by default in new installations. If you upgraded from an earlier version, check the setting. If you turn posting on, you accept the known limits described in the extension settings and in the documentation published with your Build. These include:

• Wrong company or ledger. If a company or ledger is renamed, replaced or loaded in Tally at the moment of posting, the voucher could land in a different company or ledger than the one Bridge checked. Do not change companies or ledgers in Tally while a posting is waiting.
• Other changes. Bridge cannot stop changes made directly in Tally, or by other software, while it works.
• Tally slowdowns. Bridge's requests can make Tally slow or unresponsive, sometimes until Tally is restarted. This can affect other users of a shared Tally.
• No undo. Bridge has no tool to delete, reverse or undo a voucher it has posted. You must correct a wrong posting yourself in Tally.

9.3 Your approval is your instruction. Each posting waits for your approval in a separate window on your computer. The window shows what will be posted: for a single voucher, its entries; for a batch (where a Build allows batches), a summary. An approval is used once and stays valid for up to 15 minutes after you give it.

When you approve, you instruct Bridge to post what the window showed. For a batch, you instruct Bridge to post every voucher in the batch that the summary describes. You are responsible for that decision and its accounting consequences, whoever proposed the voucher: you, your AI Assistant or anyone else. This does not apply to any difference between what the window showed and what Bridge actually posted. Do not approve a voucher you have not read and understood.

9.4 Safeguards. Bridge gives your AI Assistant no way to approve a posting. Approving postings automatically, or otherwise getting around the approval window or other safeguards, removes their protection. If you, or software acting for you (including software that can control your screen), do so, we are not responsible for the result.

9.5 Checking after posting is not an audit. After posting, Bridge reads the voucher back from Tally and reports what it found. A match means the details Bridge compared were the same. Bridge does not compare every detail. A match does not mean the entry is correct, complete, properly classified or compliant.

10. No professional advice

Bridge is a technical tool. Nothing from Bridge, from your AI Assistant, or in our documentation or website is accounting, tax, audit, legal, investment or other professional advice. None of it replaces your own professional judgement. You remain responsible for your work, your filings, your opinions and your advice to your Clients.

11. Acceptable use

You must not use Bridge or the Services:

a. to access Tally books, or other data, that you are not authorised to access;

b. in breach of any law, including data-protection, tax, professional-conduct, export-control and sanctions law, or in breach of Tally's or your AI Provider's terms;

c. to create false, misleading or fraudulent accounting entries, or to hide or falsify records;

d. to interfere with, overload, probe or attack our Services or anyone else's systems. Good-faith security research reported to us privately (section 19) is allowed; or

e. to misrepresent your relationship with ComplyEaze, or to use our names or logos except as section 6 allows.

12. Feedback and contributions

12.1 If you send us ideas, suggestions or feedback about Bridge, including votes or reactions on our public issues or roadmap, we may use them without any obligation to you. Votes help us understand what users want. They do not oblige us to build anything, in any order or by any date.

12.2 Contributions to the Source Code are governed by the contribution terms in the Bridge repository (CONTRIBUTING.md). Under those terms, contributions are provided under the Apache Licence.

12.3 Do not include real client data, passwords or other confidential information in issues, bug reports, logs or screenshots that you share with us or post publicly.

13. No warranty

13.1 To the maximum extent permitted by applicable law, Bridge, Official Builds, the Source Code, the documentation and the Services are provided "as is" and "as available", with all faults. We give no warranty, condition or representation of any kind, whether express, implied or statutory. In particular, we give none:

a. of merchantability, satisfactory quality, fitness for a particular purpose, accuracy, completeness or non-infringement;

b. that Bridge will be uninterrupted, error-free or secure; or

c. that Bridge will work with your version of Tally or your AI Assistant.

13.2 Any statement that a release or feature has been tested, checked or tried describes our own checks at the time. That applies whether the statement is in these Terms, the Privacy Policy, the README, release notes or anywhere else. It is not a warranty, or a promise that Bridge will work for you.

13.3 We do not warrant that anything Bridge reads, reports, prepares or posts matches what is recorded in Tally, is complete, or is correct for any accounting, tax or legal purpose.

14. Limitation of liability

14.1 To the maximum extent permitted by applicable law, none of ComplyEaze, its partners, employees and agents, or the contributors to Bridge, will be liable for:

a. any indirect, incidental, special, consequential, exemplary or punitive loss or damage;

b. any loss of profits, revenue, business, goodwill, clients, contracts or anticipated savings;

c. any loss or corruption of data, including your Tally books, or the cost of restoring or re-entering it;

d. any tax, interest, penalty, fee or late fee imposed on you or your Clients, or the cost of correcting a return, filing or set of books;

e. any claim by your Clients or any other third party against you; or

f. any loss caused by your AI Assistant, your AI Provider, Tally or other third-party software.

This applies to loss arising out of or in connection with Bridge, the Services or these Terms, however it is caused. It applies whether the claim is in contract, tort (including negligence), breach of statutory duty or otherwise, and even if we were told the loss was possible.

14.2 To the maximum extent permitted by applicable law, our total liability to you for all claims arising out of or in connection with Bridge, the Services or these Terms is limited to the total amount you paid us for Bridge in the twelve months before the event giving rise to the claim.

14.3 If a court or other authority decides that the limit in section 14.2 cannot apply, our total liability for all claims together is limited to INR 1,000, to the maximum extent permitted by applicable law.

14.4 Nothing in these Terms excludes or limits liability for fraud, wilful misconduct or gross negligence, or any liability that cannot be excluded or limited under applicable law.

14.5 These limits reflect that Bridge is still being developed, that each release says what has not yet been tried, and that you control its use, settings and approvals. They form part of the basis on which we make it available.

15. Indemnity

To the extent permitted by applicable law, you will indemnify ComplyEaze and its partners, employees and agents against third-party claims. "Claims" here means any claim, demand, loss, cost or expense (including reasonable legal fees) brought by a third party, including your Clients. The indemnity covers claims to the extent they arise from:

a. your breach of these Terms or of the law, or of Tally's or your AI Provider's terms;

b. a voucher you approved, or data you accessed or shared, without the authority required by section 8; or

c. your breach of any duty you owe your Clients.

It does not apply to the extent a claim results from our breach of these Terms or our negligence or wilful misconduct. It does not cover any penalty imposed on us for our own breach of the law.

16. Suspension and termination

16.1 You may stop using Bridge at any time by uninstalling it. Uninstalling may leave Local Files on your computer; see section 7 of the Privacy Policy.

16.2 We may stop publishing Builds, withdraw a Build, or suspend or end any Service at any time. Where practical, we will say so on the Bridge website. This does not affect rights you already have under the Apache Licence in software you have received.

16.3 Sections 5.2, 6, 9, 10 and 12 to 20, and any other provision that by its nature should continue, survive the end of these Terms.

17. Changes to these Terms

17.1 The version of these Terms included in or linked from a Build governs your use of that Build. Each version has a version number and date at the top, and is kept in the public history of the Bridge repository.

17.2 We may publish new versions, for example when Bridge gains or loses features or the law changes. A new version applies:

a. to Builds that include or link to it; and

b. to the Services, from the date we publish notice of it on the Bridge website or in release notes.

It does not apply to events before it takes effect. If you do not agree to a new version, do not install the Builds that carry it, and stop using the Services.

18. Governing law and disputes

18.1 These Terms are governed by the laws of India. So is any dispute or claim arising out of or in connection with them, Bridge or the Services.

18.2 Before starting any proceedings, the party raising a dispute will notify the other in writing, at the contact address in section 19. Both will then try in good faith to resolve it within 30 days. This does not stop either party from seeking urgent interim relief.

18.3 Subject to any right you have under mandatory law, the courts at Alwar, Rajasthan, India, have exclusive jurisdiction over any such dispute. If those courts do not have jurisdiction, the courts having jurisdiction over our registered office have exclusive jurisdiction instead.

19. Contact

• General questions and notices: [email protected], SPMS Comply Eaze Solutions LLP, at the address in section 1.1.
• Grievances: our Grievance Officer, the Designated Partner of SPMS Comply Eaze Solutions LLP. Email [email protected] with "Grievance" in the subject. Response times are in section 16 of the Privacy Policy.
• Security vulnerabilities: [email protected], or GitHub private vulnerability reporting for the Bridge repository. We aim to acknowledge a report within seven days. Please do not report a vulnerability in a public issue.

We may send you notices by publishing them on the Bridge website or in release notes, or by email if you have given us your email address.

20. General

20.1 Entire agreement and precedence. These Terms and, for the software itself, the Apache Licence are the entire agreement between you and us about Bridge. They replace any earlier understanding about it. For your rights in the software, the Apache Licence prevails (section 5.2). Otherwise, these Terms prevail. Other ComplyEaze products and services have their own terms, which do not apply to Bridge.

20.2 Severability. If any part of these Terms is found invalid or unenforceable, it will be enforced as far as the law allows, and the rest of these Terms stays in effect.

20.3 No waiver. If we do not enforce a right, we have not given it up.

20.4 Assignment. You may not transfer your rights or obligations under these Terms without our written consent. We may transfer ours to an affiliate or to a successor to our business.

20.5 Events beyond our control. We are not responsible for any delay or failure caused by events beyond our reasonable control, including failures of third-party software, networks or services.

20.6 Relationship. Nothing in these Terms creates a partnership, agency, employment or fiduciary relationship between you and us.

20.7 Language and headings. These Terms are written in English. Headings and the summary at the top are for convenience only, and do not affect how these Terms are read.