Terms of sale

Version 2026-10-23.1. These terms cover buying tools at dominares.org.

Please read the Disputes section. Disputes go to binding individual arbitration instead of court, and class actions and jury trials are waived, unless you opt out within 30 days of buying.

Who you're buying from

Dominares Tools is run by Joseph Linares, a sole proprietor based in San Diego, California (“we”, “us”). Contact: support@dominares.org.

Who can buy

You must be at least 18, or the age of majority where you live if that is older. If you buy for an organization, you confirm that you're authorized to accept these terms for it, and “you” then means the organization, as it does in the license.

The tools sold here are subject to US export-control and sanctions laws. You may not buy or use them if you are located in a country or region under comprehensive US sanctions, or if you are on a US government list of restricted or blocked parties, and you may not use them in breach of those laws.

What you're buying

Each purchase is a license to use one tool: the tool named at checkout, at the price shown there, with everything its repository includes (such as crawl's bonus pack). In these terms that tool is “the Software”. The license is the Dominares Tools Commercial License, and the Software is delivered as read-only access to that tool's private GitHub repository under github.com/dominares-tools, for the GitHub account you choose before paying. Each purchase covers one GitHub account and one tool.

Price and payment

Each tool's price is shown on its page and at checkout, in US dollars, and is paid once, plus any sales tax, VAT or GST that applies where you live. Checkout shows the total before you pay, and Stripe may show it in your local currency. Payment is sold through Link, Stripe's merchant-of-record service, which calculates and collects that tax and sends your receipt. Link's terms apply to the payment.

Delivery

GitHub sends the invitation to the tool's repository right after your payment completes. Sign in as the account you bought for and accept it within 7 days. If it expires, request a new one at dominares.org/access. To move access to a different GitHub account, email us.

Updates

Your access includes every version of the Software published to its repository. If a tool is ever discontinued, you keep the right to use the versions you already have under the license.

Refunds

You can get a full refund of a purchase within 14 days of buying. See the refund policy.

Chargebacks

If you dispute a payment with your card issuer, access to the repository of the tool it paid for is paused while the dispute is open. If the payment is reversed, that access and that tool's license end as they would after a refund; if the payment stands, access returns. A question from your card issuer that isn't a dispute doesn't affect access.

Support

Email support@dominares.org. Every buyer of a tool shares its repository, so support happens by email rather than in GitHub issues.

Using the tools responsibly

You decide what you use the Software on and what happens to its results, and you're responsible for both. That includes complying with copyright, privacy and data-protection law, with laws about accessing computers (such as the US Computer Fraud and Abuse Act and California Penal Code section 502) and with the other laws that apply to you. For some tools, that means in particular:

• crawl fetches whatever sites you point it at, and you decide which sites, how often and what happens to what it collects. Crawl only sites you're allowed to crawl, and follow each site's terms of use, robots.txt and rate limits. Its social-post fetchers use your own YouTube, X and Facebook credentials: you're responsible for those credentials and for following each platform's terms.
• inbound: receive and process only mail you're entitled to receive, and follow anti-spam law.
• canary: probe only chatbots and endpoints you operate or have permission to test. Its optional phone-call alerts go through your own Twilio account to the numbers you set, so you're responsible for those numbers, for Twilio's terms and for its charges.
• statepath: use it on your own data, and back that data up before you migrate it.
• pagepatch: use it on pages you control, and review the edits an AI model makes before you publish them.
• pdfedit: edit only documents you have the right to edit, and never use it to forge or falsify a document or to impersonate anyone.
• cleartosend is not legal advice, and it does not make your messages or calls compliant. You get and record consent, honor opt-outs, register your numbers (for example, for A2P 10DLC) and follow telemarketing, anti-spam and privacy law, such as the US Telephone Consumer Protection Act (TCPA).
• replysplit: process only mail you're entitled to process, and handle the personal information in it lawfully.
• deadroutes reports what it observed, not what is safe to remove. Use it on applications you operate, and check its findings before you remove anything.
• llmledger: its figures are estimates, not bills. Check the prices it uses against your providers' current prices.
• answergrade: test only chatbots and data you operate or have permission to test. An AI judge can be wrong, so review its verdicts.
• callrelay: you're responsible for the calls it answers. That includes telling callers they're talking to an AI where the law requires it, getting consent to record where the law requires it (California requires every party's consent), and never placing AI-voice calls without the prior express consent the law requires (such as under the TCPA, which the FCC applied to AI-generated voices in 2024).
• notehaul: export and publish only notes you're entitled to. Its Mac exporter asks macOS for permission to control Notes.app and reads only the folders you name. Stripping [bracketed] text removes brackets, not secrets, so review what you publish before it reaches an endpoint.
• truthpatch repairs only what the facts you give it let it check, and it can be wrong. Keep your facts true, and review what it changes before a customer relies on it. It is not a substitute for reviewing your chatbot's answers.
• lifeskiff calls no AI vendor itself. It decides that a vendor account is broken from the wording of the vendor's errors, which a vendor can change, and its alerts go to the endpoint you choose. You're responsible for your vendor accounts, their terms (including sending a request to a different vendor) and what you send them.
• asgiwarden reduces risk and does not make an application secure. Set trusted_hops to the number of proxies in front of your app, because a wrong value can let a visitor forge their address. Use it on applications you operate.
• uploadwarden: its SVG check is a refusal list, not a sanitiser, and is one layer of defence. It does no virus scan, sign-in, CSRF protection or rate limiting. You remain responsible for the files your application accepts and serves.
• dumpdrill: a plain pg_dump is SQL, a script that runs on your machine. Its scan for psql commands is a tripwire, not a sandbox, and by default the dump runs as the superuser of a throwaway server it starts, so check only dumps you trust (for one you don't, use --unprivileged inside a disposable container or VM). It checks only what your manifest asks, so a pass does not promise a restored backup is complete.
• gatedraft drafts replies and sends nothing; a person reads each draft before it goes, and an AI draft can be wrong. With no opt-out list there is no opt-out check, so pass one. You're responsible for who you write to, for honoring opt-outs and for anti-spam and privacy law.
• prodwalk: walk only sites you're entitled to test. It stops the writes a browser sends, but a GET that changes data is a read to it. It signs in with real credentials you supply, and screenshots of signed-in pages can show real data.
• knobspec reports whether a variable is set and how long it is, never its value. It cannot tell you that a secret is correct or that a deploy is safe.
• botcandor is not legal advice. Whether the EU AI Act, California's bot disclosure law or any other rule applies to you, and whether its wording or log satisfies it, is for you and your lawyer. Its log shows a disclosure was produced, not that anyone heard it, and its English pattern checks can miss an unusual phrasing.
• chatbaton makes promises on your behalf, such as that someone will follow up. You're responsible for the follow-up times you configure, for who reads its alerts and for acting on them. It is a grammar classifier, not a model: it misses some requests and fires on a few odd ones. It sends no message itself, and its reference server stores transcripts and the contact details visitors enter, so deleting that data is up to you.
• hookout sends requests to the addresses you give it, including addresses your customers typed in. Its address guard reduces the risk of reaching your own network and does not remove it; you remain responsible for your network's egress controls, for storing secrets, and for retries and replay protection. It makes one attempt per delivery and does not guarantee that a webhook arrives.
• chatperch fetches the pages you ask it to check and puts a script on other people's websites. Check only sites you're allowed to check, and add the line only to sites whose owners agreed. Host the chat page on a different origin from the sites that embed it, because chatperch cannot enforce that: the chat frame is sandboxed with allow-scripts and allow-same-origin together, and on the same origin as the embedding page that pair removes the sandbox. Popups the chat opens, such as a link or a policy page, are not sandboxed. Its load ping is evidence, not proof, and its ping store keeps only the 1000 most recent sites, so someone can push older ones out. Strict-Transport-Security is off unless you turn it on, and it binds your whole domain to HTTPS for a year.
• briefbook assembles a prompt and calls no model. You're responsible for what your bot says, for the content of your own safety text and facts, and for checking an assembled prompt before it goes live.
• cleanfork runs the gate commands you configure and git, with your permissions, and its --push uses your git credentials. It changes the repositories you point it at. A clean merge can still be wrong, and its brand scan finds only the words you list, so the gates and your review are the check.
• replyneed ranks and sorts texts with rules and can be wrong. A text it files away is not proof that nothing needed an answer, so review what it files, and keep honoring opt-outs and any message you are legally required to act on. Handle the personal information in the messages lawfully.
• vanityhost calls the hosting services you connect it to (Railway and Cloudflare) with your own credentials. You're responsible for those accounts, for their terms and charges, and for what the domains you register there serve. Its adapters are tested against stand-ins, not the live services, so try them with a throwaway domain first. A matching ownership record is a technical check, not legal proof that a customer owns a domain.
• proposeapply applies only the changes your registered handlers perform, and its undo is only as good as the inverse you write. You decide which changes a model may propose, which a person approves and what runs. Its spend figures are estimates from prices you supply, not a bill from your model vendor.
• whoanddo reduces risk and does not make an admin panel secure. You're responsible for the rules table you write, for your session secret and account files, and for how you run it. Its scanner finds only the patterns it knows, so a clean scan is not proof that no audit row can be forged.
• releasetrail runs the commands in a project's .releasetrail.json, including its gates when it plans and its deploy and rollback commands, with your permissions. Use it only on projects you trust and are allowed to deploy. Its checks cover only what you configure, and you're responsible for what you release.
• shortgate runs your test suite, and whatever your tests run, with your permissions, in the repositories you point it at, and it decides which tests not to run from what it recorded of an earlier run. A selection can miss a dependency its rules do not see, so a green selected run is not a green full run: you decide which changes always run everything (always_full), how often the whole suite runs, and what you release.
• pingrules sends messages through your own Telegram, Resend or SMTP accounts, and you're responsible for those accounts, their terms and charges, for whom you message, and for anti-spam and privacy law. It does not guarantee that an alert is delivered or that anyone reads it.
• blockflyer drafts flyers with a model you connect (your own OpenAI-compatible or Anthropic account) and can get a fact or a word wrong. Review every flyer before you print or post it. You're responsible for what it says, for the right to use the logos and photos in your brand kit, and for any notices the law requires on what you advertise.

Indemnity

To the extent the law allows, you will defend, indemnify and hold harmless Joseph Linares (Dominares Tools) and anyone working for us against third-party claims, and the resulting losses, damages, liabilities and reasonable costs, including attorneys' fees, to the extent they arise from how you use the Software or its output (including the sites, mail, messages, calls, endpoints, data, pages and documents you use it on, and what you do with the results), or from your breach of these terms, the license or the law. This does not apply to the extent a claim is caused by our gross negligence or willful misconduct. We will tell you promptly about a claim and let you control its defense with counsel we reasonably accept; we may take part at our own expense. You may not settle a claim in a way that admits fault for us, requires us to pay, or puts obligations on us without our written consent.

No warranty

Except as these terms expressly say, the Software, everything its repository includes and the repository are provided “as is” and “as available”. To the fullest extent the law allows, we disclaim all warranties, express or implied, including warranties of merchantability, fitness for a particular purpose, title and non-infringement, and any warranty that the Software will be error-free or will work with every site, service, system or file. The license says the same.

Limit of liability

To the fullest extent the law allows: (a) neither side is liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or goodwill; and (b) our total liability for all claims relating to the Software, your purchase of it or these terms is limited to the amount you paid for the Software. Part (a) does not limit your obligations under the Indemnity section, or your liability for sharing, publishing or reselling the source in breach of the license. Some places do not allow these limits; where they do not, they apply only as far as the law allows. This is the same limit as in the license.

Governing law

These terms, and any dispute about the Software or your purchase, are governed by the laws of the State of California, without regard to its conflict-of-laws rules. The Federal Arbitration Act governs the arbitration agreement in the Disputes section. If you buy the Software as a consumer, nothing in these terms takes away a protection that the law where you live gives you and does not allow a contract to waive.

Disputes

Please read this section carefully. It requires individual arbitration and waives class actions and jury trials, unless you opt out within 30 days of buying.

Talk to us first. Before starting an arbitration or a court case, each side sends the other a written notice describing the facts, the legal basis and what it asks for, and both try in good faith to resolve the dispute for 30 days. Send yours to support@dominares.org; we send ours to the email address you gave at checkout. Any deadline for bringing the claim is paused during those 30 days. This step does not apply to small-claims cases or to requests for temporary or emergency court orders.

Binding individual arbitration. Any dispute or claim between you and us arising out of or relating to the Software, your purchase or these terms that is not resolved that way will be decided by binding arbitration administered by the American Arbitration Association (AAA), not by a court. If you bought the Software as an individual for personal, family or household use, the AAA's Consumer Arbitration Rules apply; otherwise, its Commercial Arbitration Rules apply. Both are published at adr.org. One neutral arbitrator decides the dispute. The arbitration takes place in San Diego County, California, unless the AAA's applicable rules or the law require another place. The AAA's rules and the law decide who pays the fees; we will pay any fees they require us to pay. The arbitrator may award the same individual remedies a court could, including any remedy the law does not allow to be waived.

No class actions, no jury. You and we each waive the right to a jury trial and agree to bring claims only individually, not as a plaintiff, claimant or class member in any class, collective, consolidated, mass or representative action or arbitration. The arbitrator may not hear or combine more than one person's or organization's claims. A court, not the arbitrator, decides any dispute about whether this paragraph can be enforced.

What isn't arbitrated. Either side may bring an individual claim in small-claims court if it qualifies. Either side may ask a court for a temporary or emergency order to protect intellectual-property rights, before or during an arbitration. Nothing in this section waives a right or remedy that the law does not allow to be waived, including the right to seek public injunctive relief; if such a request cannot lawfully be arbitrated, a court decides it while the arbitrable claims go ahead separately. If the class-action waiver cannot be enforced for a particular claim, that claim goes to court, not to class arbitration, and everything else stays in individual arbitration as far as the law allows.

Where court cases go. Any court case these terms allow, including a claim after a timely opt-out, a claim that cannot lawfully be arbitrated, a decision about the class-action waiver, and a case to confirm or enforce an arbitration award, will be brought only in the state or federal courts located in San Diego County, California, and both sides consent to those courts' jurisdiction. Small-claims cases may be brought wherever the claimant qualifies.

30-day opt-out. You can opt out of this arbitration agreement by emailing support@dominares.org within 30 days after you buy. Say that you opt out of arbitration, and include your name, the GitHub username you bought for and the email address you used at checkout. Opting out affects only this arbitration agreement; the rest of these terms still apply, and disputes then go to the courts named above.

Changes

If these terms change, the version number changes. Your purchase stays under the version you agreed to at checkout. The version you agreed to is recorded with your purchase in Stripe.

General

• Entire agreement. These terms, the license and the refund policy are the whole agreement between you and us about the Software and your purchase, and replace anything said about it before. If the license and these terms conflict about what you may do with the Software, the license controls; otherwise these terms control.
• Severability. If part of these terms cannot be enforced, it is enforced as far as it can be, and the rest still applies. The Disputes section has its own rules for this.
• No waiver. If we don't enforce part of these terms right away, we haven't given it up.
• Assignment. You may not transfer your purchase or these terms to someone else without our written consent. Moving access to a different GitHub account of your own is covered under Delivery. We may transfer these terms to whoever takes over Dominares Tools, and we will tell you if we do.
• Notices. We send notices to the email address you gave at checkout. Send notices to us at support@dominares.org.
• Things outside our control. We aren't responsible for delays or failures caused by events beyond our reasonable control, such as outages at GitHub, Stripe or an internet provider.
• What continues. The Indemnity, No warranty, Limit of liability, Governing law, Disputes and General sections still apply after your license ends, for example after a refund.