This document is a draft and is not in force.
What it says about the software is written from the software and is accurate. What it
cannot say is the contracting legal entity, the governing jurisdiction, an address for legal notices, an address for privacy requests and an effective date — none of which is
knowable from the code. Until those are set in marketing/src/site.ts, no
agreement is formed by this page and nothing on it should be relied on. This notice
removes itself once they are.
Terms
What you are agreeing to
Including the parts that are easy to leave out. Superior CRM does not move money, and its processor connectors have not been run against a live acquirer — both are stated below rather than discovered later.
The agreement, and who it is with
These terms are between Superior Payments and the business that subscribes to Superior CRM — the customer. They cover the application at crm.supmp.com , its API, and this website.
Superior CRM is for business use. The customer creates logins for its own staff, and is responsible for what those people do with them — including any merchant-portal login it issues to one of its merchants, which is the one kind of account held by somebody outside the customer's own business.
A signup creates nothing that works on its own: a new organisation lands awaiting review and its first login is inactive, and neither can produce a session until approved. Access is granted, not self-issued.
Three things this product does not do
It does not move money
Superior CRM calculates residuals, assembles payout runs and produces invoices. It does not hold funds, initiate transfers, debit an account or disburse to a partner. A payout marked paid is a record that somebody paid it somewhere else. An invoice payment recorded against a subscription is likewise a record of a payment taken elsewhere — no card is charged by this product. The customer remains responsible for actually paying its partners and for anything that follows from a figure being wrong.
Its processor connectors are unproven
Connectors for six acquirers exist, with credential handling, field mappings and signature verification written from each processor's published documentation. None has been run against that processor's sandbox. They are marked unverified in the product and live mode is refused, and until a connector has been exercised against a real endpoint we make no representation that boarding through it will succeed. Mappings written from documentation are a hypothesis about an API, and the difference only shows up when a real application is sent.
It does not file your tax forms
Superior CRM generates 1099-NEC recipient copies and can produce the IRS electronic filing layout. That layout has never been submitted, to the test system or otherwise, and filing requires the customer's own Transmitter Control Code. The customer is the filer of record and remains responsible for the accuracy and timeliness of what is filed.
Screening is a screen, not a compliance programme
The product screens against the OFAC Specially Designated Nationals list and holds a possible match for human review. It does not perform identity verification, business verification, MATCH or TMF enquiries, or credit checks, and it does not check the national do-not-call registry — that seam answers "unknown" rather than "clear", by design, so that an unscreened number is never mistaken for a cleared one.
The customer remains responsible for its own obligations under anti-money-laundering, card-network, telemarketing and consumer-protection rules. Where the product refuses an action — a cold call to an unscreened number, an approval on a file with an unresolved screening result — overriding that refusal is a decision the customer makes and records, and the responsibility travels with it.
Your data stays yours
Everything a customer puts into Superior CRM remains the customer's. Superior Payments holds it to run the service and for no other purpose: it is not sold, not used to train anything, not aggregated into a product sold to somebody else, and never made visible to another customer. Isolation between customers is enforced in the data layer rather than by convention.
How that data is handled, what an erasure reaches and what it deliberately does not, is set out in the privacy policy, which forms part of these terms.
A customer can export its data while its subscription is active. On termination we will make it available for a reasonable period before deletion, subject to the retention obligations described in the privacy policy — some records, such as signed agreements and the audit trail, are kept because deleting them would destroy evidence somebody may need.
Fees, add-ons and suspension
Subscription fees, any per-seat component and any usage-based component are agreed in writing with each customer rather than published here. Text messaging, outbound dialling and live chat are chargeable add-ons enabled per organisation, and they cost money per use — that is why they are switched off until asked for.
Third-party costs are the customer's own. Twilio usage runs on the customer's account, processor relationships are the customer's, and nothing here is resold.
An organisation may be suspended for non-payment or for use that breaches these terms. Suspension blocks access; it does not delete data, and it is reversible.
Availability, and what we do not promise
There is no service level commitment. We do not offer an uptime percentage, a support response time or a credit for downtime, because none is currently built or measured, and publishing one that nothing enforces would be a number with nothing behind it. If a customer needs a committed level, that is a separate written agreement.
The service is provided as it is. To the extent the law allows, Superior Payments disclaims implied warranties of merchantability, fitness for a particular purpose and non-infringement, and does not warrant that the service will be uninterrupted, error-free, or that any figure it produces is correct for a purpose the customer has not verified it against.
That last clause is meant literally and is worth reading twice. Superior CRM computes money — residual splits, partner statements, tax forms. Those figures should be reconciled against the customer's own records before they are relied on to pay somebody or to file anything.
Liability, changes and governing law
Neither party is liable for indirect, incidental or consequential loss, or for lost profits or lost data, arising out of these terms. Each party's total liability is limited to the fees paid by the customer in the twelve months before the claim — with the usual exceptions for death or personal injury, fraud, and anything else that cannot lawfully be limited. The customer indemnifies Superior Payments against claims arising from data it put into the service or from its own use of it.
We may change these terms. Material changes will be notified in advance to the account's administrators, and continuing to use the service after they take effect is acceptance. A customer that does not accept a material change may terminate before it applies.
No governing law has been chosen, so this page does not state one. Naming a jurisdiction nobody selected would be an invention on the one clause that decides where every other clause is argued — the last place to guess.