Terms

Software Licence Agreement

The agreement, in plain English.

Last updated 27 May 2026

What we commit to, what we count on from you, and how risk gets shared. In plain English.

Our posture

Four things we hold to.

  1. Liability cap, both ways.

    Capped at the fees you paid us in the prior 6 months, for both sides.

  2. Mutual indemnity.

    If our software infringes a third party’s IP, we cover you. If misuse on your side triggers a claim, you cover us. Both protections, both directions.

  3. What we don’t check, we name.

    Three things our eligibility check doesn’t cover. Named in section 7 of the agreement and surfaced on every response where they apply.

  4. No commitments. Cancel anytime.

    One email ends the subscription whenever it suits you. Access runs to the end of the cycle you’ve paid for, and there’s no exit fee.

What this agreement is

RebateRight is governed by 3 dated PDFs:

This page is the plain-English read of the first. The pricing agreement has its own at /legal/pricing, and the privacy policy at /legal/privacy.

One thing to set up front: the agreement is a licence, not a transfer of ownership. You get access to the Software for the length of your subscription, scoped to your organisation. All rights in the Software stay with us. RebateRight is a registered trademark. Using our name or branding needs written consent.

What we commit to

Past the licence itself, 3 commitments you can hold us to.

Reasonable safeguards on your account data. Encryption in transit and at rest, access on a need-to-have basis, Microsoft Azure in Australia. The architectural detail lives on the Security page.

No AI on your data, ever. We don’t train AI on your account data or any patient data. Our eligibility engine itself isn’t AI either. It runs rule-by-rule against the published Medicare Benefits Schedule, so every decision traces back to a published rule.

No surprises on third-party dependencies. Services Australia and others run systems we depend on. When those are down, features that depend on them may not work as expected. The agreement names the dependency directly.

Limits we name up front

Our eligibility checking has 3 limits. They’re named in section 7 of the binding agreement and shown on the check result wherever they apply.

Medicare-unverified items. Services Australia doesn’t verify every MBS item online. For the items it doesn’t, we run our own checks and label the result indicative. That result is our own assessment, not confirmed with Services Australia. The eligibility check coverage guide lists those items and what indicative means for each.

Clinical eligibility. Our checks confirm Medicare eligibility based on claim history and patient data. They don’t assess whether a patient’s clinical circumstances, symptoms, or diagnosis satisfy the MBS requirements for a given item. That call is yours.

Regulatory change lag. Medicare rules and MBS requirements change from time to time. We reflect changes as soon as practicable, but a check returns the rules in force at the moment of the check; recently introduced or modified requirements may not yet be reflected.

What we count on from you

The agreement runs in both directions. Four commitments on your side.

Use it for what it’s for. The Software helps your practice claim what you’re entitled to under the Medicare Benefits Schedule. Don’t reverse-engineer it, probe underlying systems, or use it to misrepresent eligibility or sidestep regulatory obligations.

Patient consent before each check or claim. Services Australia requires it. You’re responsible for confirming each patient has authorised your practice to submit on their behalf.

Keep your credentials safe. API keys and login credentials are scoped to your organisation. If you suspect any compromise, email security@rebateright.com.au and we’ll revoke and re-issue promptly.

Use the Software from within Australia. Per Services Australia’s integration requirements, the Software is reachable only from inside Australia. We may suspend access if we have reasonable grounds to think this is being breached.

Bringing in outside help

Most clinics work with at least one outside team: your IT contractor setting up the integration, a development team building against the API, a billing-service partner running daily eligibility checks. The agreement makes the permission explicit.

You can let third parties use the Software under your account. Contractors, development teams, integration partners alike.

You stay responsible for what they do. Anything they do, or fail to do, is treated as your own. If they make a request without patient consent, you have breached the obligation. If they leak a credential, it’s your credential to revoke and re-issue.

Their use must meet the same obligations you owe us. Acceptable Use (section 3 of the binding text), Patient Consent (section 8), Credentials (section 9), and the Australian-access requirement (section 15). Section 10 sets out the full detail.

If something goes wrong

What happens if a problem turns into a claim. The agreement keeps protections balanced on both sides.

Liability cap, both ways. Each side’s total liability under the agreement is capped at the fees you paid us in the 6 months before a claim.

No indirect losses, either way. Neither side is liable for indirect, incidental, special, or consequential losses arising from the agreement. Standard mutual carve-out.

Mutual indemnity. If our software is found to infringe a third party’s intellectual property, or if we breach our confidentiality obligations, we cover the resulting third-party claims against you. If your misuse or your breach of law triggers a third-party claim against us, you cover that. Same shape, both directions.

Events outside anyone’s control. Neither side is liable for delays or failures caused by natural disasters, cyberattacks, government action, or third-party-system failures.

Realistic uptime, not perfection. The Software is provided as is. The agreement doesn’t warrant it’ll be error-free, uninterrupted, or fit for purposes outside what we’ve described. Our operating commitments (uptime, security, response) live on the Security page.

ACL rights are untouched. Nothing in the agreement excludes rights you have under Australian Consumer Law that can’t be excluded by contract.

Confidentiality

The agreement covers what each side learns about the other in the course of working together: technical, financial, commercial, product, pricing, Customer Data, the terms themselves. All of it is Confidential Information.

Both sides keep it confidential. Disclosure stays within the people who need it and who are bound by equivalent confidentiality obligations.

Three years past termination. Both sides hold the obligation for 3 years after the agreement ends.

Customer Data is indefinite. The 3-year tail doesn’t apply to Customer Data. It stays protected for as long as it exists.

Legal compulsion is the only out. If a law or court order forces disclosure, the receiving party notifies the other (where permitted) and limits disclosure to the minimum required.

If the agreement ends

Both sides have an exit, with clear notice and a brief cure window for breach.

No commitments. Cancel anytime. One email does it. Your access runs to the end of your current billing cycle, and there is no exit fee.

We can also terminate, with 30 days’ notice. Written notice to your registered email, for any reason. The 30 days are yours to migrate.

Either side can terminate for breach. With 14 days’ written notice, if the breach isn’t remedied in that window.

When access ends. You stop using the Software and delete any confidential materials we’ve shared. Refunds, final invoicing, and what survives termination are set out in the Pricing Agreement (linked at the top of the page).

Changes and versions

Material changes get 30 days’ notice. When we update the agreement in a way that materially affects you, we email your registered address at least 30 days before the change takes effect. Continued use may require accepting the updated terms, which you do in the app the next time you sign in.

Each version stays at its own URL, forever. The dated PDF you accepted is preserved at its original URL, with no renames or replacements. New revisions publish as new dated files alongside the old. This is how you self-verify what you agreed to at any point in time.

The general provisions live in sections 16 and 17 of the binding text: assignment, written notice, dispute resolution, governing law (New South Wales), and the entire-agreement clause. Standard and conventional; we don’t paraphrase them here.

Revision history

27 May 2026

  • Software Licence Agreement. Substantive update. New section 10 Third-Party Access: you may permit contractors, development teams, or integration partners to access or use the Software under your account; you remain fully responsible for their use, and anything they do (or fail to do) is treated as your own. Section 2 Grant of License and section 9 Credentials amended to match. Sections 10–17 renumbered to 11–18.

22 May 2026

  • Software Licence Agreement. Style only. Plain digits replace word + digit form; active voice tightened across the document. No commitment changes.
  • Pricing Agreement. Style only. Section 12 Unexpected Usage Spikes restructured for active voice; same substance, same waiver.
  • Privacy Policy. Substantive update. Scope broadened beyond the Software to the website and direct contact. New section 1 on anonymity and government identifiers. New AI commitment in section 3: no customer or patient data trains AI, and our eligibility engine is rule-based. Section 4 How we protect it now names encryption in transit and at rest, and principle-of-least-privilege access. New section 7 with an explicit Notifiable Data Breaches scheme commitment.

15 May 2026

  • Software Licence Agreement. New bullet in section 7 Limitations of Eligibility Checking: Regulatory change lag. Eligibility results reflect the information available at the time of the check; recent Medicare or MBS changes may not yet be included. Effect of termination clause reworded in a friendlier tone; same legal force.
  • Pricing Agreement. Visual template upgrade. No commitment changes.
  • Privacy Policy. Visual template upgrade. No commitment changes.

March 2026

The earliest revisions in our current dated-URL system. Detailed change notes start from May 2026; the PDFs below are preserved unchanged at their original URLs.