Terms

These terms cover this website and the services described on it. A signed proposal or partner agreement always wins over this page where the two differ; this page is the default, not the contract.

Who you are contracting with

EBROTECH LLC, a limited liability company formed in New Mexico, United States, trading as LegacyRail, at 3731E South Dawson Street, Seattle, WA 98118. Invoices, contracts and data processing agreements are issued and signed by the LLC.

What we sell

Professional services, not a software licence. Specifically: reviews of legacy software, custom bridges between that software and a client's CRM and AI assistant, and monthly maintenance of those bridges. Prices are published on the pricing page. The same figure applies in dollars or in euros depending on where you are.

Access to our tooling, where it is granted, is granted for the duration of an engagement. It is not sold, sublicensed or transferred, and it does not survive the engagement.

How the route into a program is chosen

In this order, and we do not skip a step to save time: the vendor's official API; an export the client is entitled to authorise; reading the client's own database under a signed agreement; and last, an agent operating the client's own screen with their permission.

We do not modify, patch, decompile or redistribute any vendor's software. If every route is closed by the vendor's terms or by technical means, we say so in writing, you keep the review, and no build is sold.

You confirm that you, or your client, are entitled to grant the access you grant us. We rely on that, and it is the one thing we cannot verify from the outside.

Payment

Reviews are paid in full before work starts. Builds are paid half at signature and half at delivery unless the proposal says otherwise. Monthly maintenance is billed monthly in advance and is required for every live bridge.

If a monthly payment stops, maintenance stops. What we already delivered stays with you and keeps running until something changes on the vendor's side, at which point it is nobody's responsibility to fix it. That is exactly why the monthly is not optional.

The 30-day guarantee

If a bridge does not work against the client's real data within 30 days of delivery, we refund the build fee. It does not cover a change of mind, a change of scope, or a vendor revoking access after we delivered a working bridge. The monthly is what covers that last one, by moving to the next route down the list at no extra build cost.

What we do not promise

• No SLA with numbers on it. We have not run one long enough to promise uptime or response times honestly, so we do not.
• No promise that a vendor keeps the door open. The integration is the vendor's territory, not ours, and they can close it whenever they like.
• No connector we have not run against the real thing. Where you would be the first on a given program, we say so before you pay.

Confidentiality and your client

Anything we see while building (your pricing, your client list, their data) is confidential and stays that way after the work ends. Where you are an agency, we do not approach a client you introduced, and that obligation is written into the partner agreement with a term attached.

Data protection

Where we handle personal data on behalf of a client, we do it under a written data processing agreement signed before any access is granted, as a processor acting on documented instructions. We do not accept patient health records, or any comparable category of sensitive data, without a specific agreement signed first.

How we handle your data as a visitor or a subscriber is on the privacy page.

Who owns what

You own your data and your client's data. You own the configuration and the automations we build inside your accounts, and they stay with you.

We own our tooling: the connectors, the CLI, the MCP servers, the templates and the platform behind them. Nothing on this site transfers ownership of any of it, and access ends when the engagement does.

Limits

We are liable for what we did. Our total liability for any engagement is limited to the fees paid for that engagement in the twelve months before the claim. We are not liable for indirect or consequential loss, or for a third-party vendor changing or withdrawing their own product.

Ending it

Monthly maintenance can be cancelled with 30 days' notice, from either side, without a reason. There is no minimum term on maintenance and no cancellation fee. Blocks of time under Your Tech Department carry the commitment stated in their proposal.

Which law

These terms are governed by the laws of the State of New Mexico, United States, without regard to its conflict-of-law rules. If you are consumer-protected somewhere else, that protection is not taken away by this paragraph.

Talking to us

info@ebrotech.net, or by post to EBROTECH LLC, 3731E South Dawson Street, Seattle, WA 98118, United States. Before anyone escalates anything, email us: most of it is a misunderstanding that a written answer fixes.