Portal terms

The Mule Portal is where clients follow their projects, talk to Mule, see what their running systems cost and pay invoices. These terms summarize how the Portal works. For clients, the Master Services Agreement (MSA) and Order Form signed with Mule govern; if anything here differs, the signed agreement wins.

1. Who can use the Portal

The Portal is for invited clients and their staff. An organization's owner invites users and assigns roles (owner, billing, staff, viewer). Someone who signs up without an invitation sees a waiting state and a short brief form until Mule connects them to a project.

2. Your account

• Keep your sign-in details to yourself. One person per account.
• Owners and billing roles must use multi-factor authentication.
• Tell us at once at juastins@icloud.com if you think an account has been misused.

3. What the Portal shows

Project phases and a progress bar weighted by milestone, messages and files, approvals and signatures, the usage and cost of each live system as it accrues, invoices and payments, and release notes. Usage figures come from provider bills and Mule's own metering and may be adjusted when final provider invoices arrive.

4. Approvals and signatures

Approving a milestone, a change request or a quote in the Portal, including from a signed link in an email, is a binding instruction from your organization. Electronic signatures and approvals are recorded with the user, time and document version.

5. Payments

Payments are processed by Stripe by card, ACH, SEPA debit, iDEAL | Wero or Bancontact, depending on your region. See Payment terms.

6. Your data

Your organization owns its data. You can export it at any time in open formats, including during a suspension. How Mule processes personal data for you is set out in the DPA.

7. Acceptable use

The Acceptable Use Policy applies to everyone who uses the Portal and the systems Mule hosts.

8. Availability

We aim to keep the Portal available at all times but do not promise uninterrupted service. Planned maintenance is announced in advance where practical. Service levels for client systems are set in each Retainer Schedule.

9. Ending access

Access ends when the organization's agreement with Mule ends, or when an owner removes a user. After the agreement ends, the Exit and Transition Plan in the MSA applies to your data.