Legal

Terms of Use

Effective 13 October 2026. Applies to this website and to the published SFDT builds.

1. Who these terms are with

SFDT is published by Hallows Group LLC, a limited liability company organised in Texas, United States (“we”, “us”). These terms cover your use of this website at sfdt.dev and of the builds we publish: the @sfdt/cli command-line tool on npm, the browser extension “SFDT for Salesforce” on the Chrome Web Store, and the VS Code extension sfdt.sfdt-devtools on the Visual Studio Marketplace.

There are no accounts and no fees. Using the site or installing a build means you accept these terms; if you do not, do not use them.

2. The software is open source — the licence governs it

SFDT’s source code is public at github.com/scoobydrew83/sfdt and is licensed to you under the Apache License, Version 2.0. That licence — not this page — is what grants and governs your rights to use, copy, modify and redistribute the software.

Third-party components are listed with their own licences and attributions in THIRD_PARTY_NOTICES.md, and those licences continue to apply to those components.

3. Your use of the tools and the site

SFDT operates on Salesforce orgs you already have access to, using credentials you supply through Salesforce’s own tooling. You are responsible for:

• having authority to run these tools against the orgs you point them at, and complying with your own organisation’s policies and with your agreements with Salesforce;
• what you run. Some features change or delete data in your org — deploys, rollbacks, record and bulk deletes, data imports, permission writes. The destructive ones ship off by default or require a typed confirmation, but the decision and the consequences are yours. Validate against a sandbox or scratch org first, and keep your own backups;
• the data you choose to route elsewhere — to an AI provider, a notification channel or a webhook you configure. The Privacy Policy describes exactly what each path sends;
• your own credentials and API keys. We never receive them, so we cannot rotate or revoke them for you.

As for this website: use it lawfully. Do not attempt to break, overload or probe it beyond ordinary use, do not use it to distribute malware, and do not scrape it in a way that degrades it for others. Security research is welcome — report findings through GitHub’s private security advisories rather than publicly.

4. Availability and changes

The site and the tools are provided free of charge and with no service commitment. We may change, break, deprecate or withdraw any feature, endpoint, page or published build at any time, and we do not promise any uptime, retention or backwards compatibility. Content on this site may be incomplete, out of date or illustrative rather than live, and is not advice you should rely on without checking it.

5. No warranty

The software and this website are provided “AS IS” and “AS AVAILABLE”, without warranties or conditions of any kind, either express or implied. This includes, without limitation, any implied warranties or conditions of title, non-infringement, merchantability, fitness for a particular purpose, accuracy, or uninterrupted or error-free operation. This mirrors section 7 of the Apache-2.0 licence and extends the same disclaimer to the website.

In particular, SFDT’s audits, quality scores, security and field-impact analyses, deployment test selection and AI-generated output are aids to your judgement, not substitutes for it. They can be wrong, incomplete or out of date. Nothing SFDT produces is legal, security or compliance advice, and a passing check is not a guarantee that a deployment is safe.

6. Limitation of liability

To the maximum extent permitted by applicable law, and in no event, whether in contract, tort (including negligence), strict liability or otherwise, will Hallows Group LLC or any contributor be liable to you for any damages arising out of or relating to the software or this website. This includes, without limitation, any direct, indirect, special, incidental, exemplary or consequential damages, and any loss of or damage to data, metadata or Salesforce configuration, loss of profits, revenue, goodwill, or business interruption — even if advised of the possibility of such damages. This mirrors section 8 of the Apache-2.0 licence and extends it to the website.

Where liability cannot lawfully be excluded, our total aggregate liability relating to the software and this website is limited to the greater of the amount you paid us for them (which is zero) or US$100.

Some jurisdictions do not allow the exclusion of certain warranties or the limitation of certain liabilities. In those jurisdictions the exclusions and limitations above apply only to the extent the law allows, and nothing here affects rights that cannot lawfully be waived.

7. Trademarks and independence

Salesforce^®, Salesforce Platform, Flow Builder, Apex, Lightning, Trailhead, Trailblazer, Agentforce, Salesforce DX and related names, marks and logos are trademarks or registered trademarks of Salesforce, Inc. or its affiliates. They are used on this site and in SFDT’s documentation and interface nominatively — that is, only to describe the products SFDT interoperates with and the features it works on. No sponsorship or endorsement is claimed or implied, and no right in those marks is asserted.

Google Chrome, Microsoft Visual Studio Code, Microsoft Teams, Google Chat, Slack, Cloudflare, GitHub, npm, Grafana Loki, Anthropic Claude, Google Gemini and OpenAI are trademarks of their respective owners and are likewise referred to nominatively. Those companies do not sponsor or endorse SFDT.

Your rights to SFDT’s own name and logo are limited to what the Apache-2.0 licence says: section 6 of that licence grants no trademark rights. You may of course state factually that your work uses or builds on SFDT.

8. Third-party services

SFDT interoperates with services operated by other people: your Salesforce org, the npm registry, AI providers, notification platforms and GitHub, among others. Your use of those services is governed by their terms and their privacy policies, not by these. We are not responsible for what they do, what they charge you, or what they do with content you send them through a path you configured.

9. Governing law and venue

These terms, and any dispute arising out of or relating to them, this website or the builds we publish, are governed by the laws of the State of Texas and the federal laws of the United States applicable there, without regard to conflict-of-laws rules. You and Hallows Group LLC agree to the exclusive jurisdiction of the state and federal courts located in Texas for any such dispute, and each waives any objection to venue there.

The United Nations Convention on Contracts for the International Sale of Goods does not apply. If you are a consumer resident elsewhere, this clause does not deprive you of the protection of mandatory consumer-protection law in your place of residence.

10. General

• Changes. We may update these terms; the effective date above changes when we do, and the full edit history is public in git. Continuing to use the site or the builds after a change means you accept the updated terms.
• Severability. If a provision is held unenforceable, the rest stays in force and the unenforceable part is limited to the minimum extent necessary.
• No waiver. Not enforcing a provision is not a waiver of it.
• Entire agreement. For the website and the published builds, these terms together with the Privacy Policy are the whole agreement between us — except that the Apache-2.0 licence remains the agreement covering the software itself.

11. Contact and notices

Privately, and for anything legal. Email sales@hallowsgroup.com, or write to us:

Any notice required under these terms — a legal notice, a trademark or copyright complaint, a dispute, or anything you would rather not put in public — should go to one of those two addresses, and we will treat a notice as given when it reaches either. Notices to you may be given through this website or the repository.

Publicly, if you would rather. A question about these terms, or anything that looks wrong on this page, is also welcome as an issue in the public repository — often the faster route for anything that is fine in the open. Security vulnerabilities go privately through GitHub’s security advisories, per SECURITY.md. Privacy and data-subject requests are handled through the contact routes in the Privacy Policy, which are the same ones.

Hallows Group LLC, Texas, United States.