Skip to content

The Fair Terms pledge

Nine promises, and which of them we can keep today.

Every line on this page was written against something a shop owner has actually been done to — a thirty-day cancellation notice, an account locked over an expired card, a platform migration nobody asked for, data deleted ninety days after leaving. They are not aspirations and they are not marketing copy. They are the terms, in the words we would use if you asked us across a counter.

4 of the nine work in the product right now. The other five are policy waiting on machinery or activation — chiefly subscription payment processing and the deliberately unarmed trial-expiry switch. No shop has ever been charged for Torqix. Each one below says which it is. A pledge page that renders nine confident promises when five of them have no code behind them is the exact behaviour this page exists to sell against.

The commitments

  1. Promise 1 of 9

    Policy, not yet mechanical

    You pay by the month, and you can stop by the month.

    Monthly is the default and the price you see is the price for that month. An annual term exists only if you go looking for it and want the discount attached to it; nothing auto-enrols you into one, and no plan quietly renews for another full year because you missed a window.

    Written against
    Auto-renewing annual terms that restart in full the day before you meant to leave.
    Not yet because
    Billing is not switched on yet — no shop has ever been charged for Torqix.
  2. Promise 2 of 9

    Working today

    Cancelling takes two clicks, inside the app, at two in the morning if you like.

    Cancel is a button in your own settings, next to everything else about your account. It is not an email address, not a form that opens a ticket, and not a phone number that only answers between nine and five in a timezone you do not live in.

    Written against
    Cancellation by written notice to an address that is answered slowly, if at all.
  3. Promise 3 of 9

    Working today

    There is no notice window, and there is no retention call.

    You cancel, it takes effect at the end of the period you already paid for, and that is the end of the transaction. Nobody from Torqix rings to ask what went wrong unless you would like them to — and if you would, say so, because that conversation is worth more to us than the month.

    Written against
    A thirty-day cancellation notice, so leaving in March means paying for April.
  4. Promise 4 of 9

    Policy, not yet mechanical

    The trial is fourteen days and takes no card.

    You do not hand over a card to find out whether the software works. Signup records a date fourteen days out, but the expiry switch is not armed today: nothing is charged, the shop remains writable after that date, and the trial does not yet end mechanically. There is no sales call in front of it.

    Written against
    A card up front, a trial that silently converts, and a demo you have to book.
    Not yet because
    No card is taken, signup records an end date fourteen days out, and the billing screen counts it down. Trial enforcement is deliberately unarmed: the date does not end the trial today, and there is no warning-email engine.
  5. Promise 5 of 9

    Policy, not yet mechanical

    Your export works in one click, with nobody's permission.

    The current CSV/JSON archive is self-serve and has no subscription check, but it is not the whole shop yet. Its manifest names the missing families, and it does not contain media bytes. Access works on a trial, after a failed payment, and after cancellation.

    Written against
    An export you have to ask for, that arrives in a fortnight, missing the photos.
    Not yet because
    The self-serve, never-gated mechanism is live. The full-export claim is not: frozen approvals, time/payroll, assistant threads, trash and media bytes still have to be added.
  6. Promise 6 of 9

    Working today

    After you leave, your shop stays readable and exportable for twelve months.

    Your history does not evaporate ninety days after you go. A warranty claim on a job you did last spring is exactly the moment you need a record from software you no longer pay for, so that record is still there and still exports.

    Written against
    Data deleted ninety days after termination, with no export path out.
  7. Promise 7 of 9

    Policy, not yet mechanical

    We will never hold your shop's data over a bill.

    If a payment fails, the account goes read-only and export keeps working. It does not lock, it does not go dark, and your customer list is not leverage. A card expires because cards expire; that is a billing problem, and billing problems get solved by talking, not by taking a shop's history away from it while it is trying to run a Tuesday.

    Written against
    Locked accounts on a failed payment, with the data behind the lock.
    Not yet because
    Nothing can fail to pay until billing exists. The export half is live today.
  8. Promise 8 of 9

    Policy, not yet mechanical

    Nothing you rely on disappears with less than 90 days' notice.

    When we replace something, the old way keeps working for at least ninety days and the notice is published on the changelog with a date on it. You are not going to open Torqix on a Tuesday morning and find the screen your advisors learned has been replaced by a better one you did not ask for, with no way back.

    Written against
    A forced platform migration with features missing on day one, and an accounting sync cut with four days' notice.
    Not yet because
    The policy is real and the changelog that carries the notices is live — but no version of Torqix has ever been deprecated, so the promise is untested.
  9. Promise 9 of 9

    Working today

    You will never be made to use our card processing.

    Recording a payment you took some other way — cash, a check, the terminal already sitting on your counter — is free at every tier and always will be. There is no module fee for writing down that a customer paid you. When our own processing goes live the rate will be printed on the pricing page rather than quoted on a call, and using it will be a decision you make on the numbers.

    Written against
    A payments module at hundreds a month, or processing you are locked into and cannot price-compare.

The two you can count.

Two of the promises above are numbers rather than sentiments — two clicks, and fourteen days — and a number is something you can hold us to. Cancellation is Working today: an owner can perform both clicks now. The trial remains Policy, not yet mechanical: signup records and displays the date, but the switch that ends the trial is not armed.

Leaving, click by click

Working today
  1. Click 1: Settings, then Plan and billing, then Cancel

    The button is on the page with the rest of your account, in plain sight, not at the bottom of a long one and not behind a link that says Manage. An owner can reach it; nobody else can, because cancelling the shop's software is not a service advisor's decision.

  2. Click 2: Confirm — on a page that already tells you your last day

    Before you press it, the page states the exact date service ends, that it is the end of the period you have already paid for, and what your data does afterwards. The button itself carries the date, so nobody clicks it without knowing. There is a box for anything you want to tell us; it is optional and the form submits empty.

  3. After the two clicks: Then nothing. That is the whole transaction.

    No confirmation call, no offer, no exit survey with required fields, no thirty days of notice you did not know you owed. You keep working normally until the date on the button, and the same screen shows a one-click way back if you change your mind — undoing should be easier than doing.

What is deliberately not in the way

  • A notice window. Leaving in March does not mean paying for April.
  • A retention call, or a discount produced at the last second — if the price was worth having, it should have been the price.
  • A required reason. The box is there because we want to know, not because you owe us an answer.
  • Typing your shop's name to prove you meant it.
  • An email address, a support ticket, or a phone number that answers between nine and five somewhere else.
  • Anything at all happening to your data on the day you go.

After the last day the shop stays readable and exportable for twelve months — promise six — and both cancellation and export work today. Export has no plan check on it of any kind.

What fourteen days looks like

Policy, not yet mechanical

Signing up records the end date, fourteen days out, and the app now counts it down: the quiet line is there, and your plan screen shows the date in full. There is no warning-email engine, and the deployment switch that would advance an expired trial is not armed. Nothing is switched off when the date passes today.

Day 0
You create the shop and start using it. Nothing asks for a card, because there is nothing to ask with, and no salesperson is assigned to you.
Days 1 to 10
One quiet line in the app tells you how many days are left. It does not follow you around, it is not a modal you have to dismiss to write an estimate, and it does not appear on a screen a customer can see.
Day 11
Three days out, the line in the app gets louder. There is no trial-warning email engine and no sales call.
Day 14
The recorded end date arrives. Trial enforcement is not armed, so the date does not end the trial or switch the shop to read-only. Nothing converts, charges or deletes itself.
After
The shop remains writable while enforcement is unarmed. The built clock requires an explicit deployment switch; its first armed pass records notice and changes nothing, and only a later pass can make the shop read-only. Export remains outside that gate.

If trial enforcement is armed, read-only is the floor and there is nothing below it. An expired trial will not be a locked or deleted account — the same rule as a failed payment, for the same reason: your customer list is not leverage.

Signed, and dated

This pledge was last changed on 2026-08-28. If it ever changes in a way that takes something away from you, that change is published on the changelog with a date on it, at least ninety days before it takes effect, and the version you signed up under keeps applying to you for that whole window. A promise that can be edited quietly is not a promise.

On behalf of to be decided— registered legal entity name has not been decided yet:

to be decided— who signs the Fair Terms pledge publicly — founder name and title as it should appear has not been decided yet

The long version

The same things, at greater length.

None of this is only on a marketing page. The terms of service say them as clauses, the privacy policy covers what happens to your customers’ information, and both are honest drafts that a lawyer has not read yet — which they say at the top rather than in a footnote.

What is not finished is listed on the home page under a heading that says so, and what shipped is dated on the changelog.