Torspan
Terms.
What your company is agreeing to, and what Torspan is agreeing to. In the words that are the contract — there is no second version of this written in lawyer language.
That matters more than it sounds like it does. When a company hands you a friendly summary and a real agreement, the friendly one is decoration and the real one is the one that counts. This page is the real one. If a sentence here is unclear, that is a defect in our writing, not a gap the fine print fills in.
The privacy half is its own page: what's collected, what never is, and how long it's kept.
The length figure is counted from this page, not typed by hand. A page that prints its own word count is making a claim you can check in one paste.
Two rules, before anything else
These two make everything below worth reading, so they go first.
One. If this page and Your records ever disagree, the reading that's better for you is the one that holds — and the disagreement is a defect we fix, not a trap we sprung. Nobody should have to read two pages of ours and work out which one we meant. When we find one, we fix it and it shows up in What changed with the date.
Two. Anything on this page that's better for you can be improved for everybody. Anything that's worse for you applies only to accounts opened after the change, never to yours. Terms that got worse after you signed are the oldest trick in software, and the fix is one sentence long, so there it is.
Everything from here to the bottom is written to be read by the person it affects: the man who wrote the sentence, the foreman who checked it, the office that pulls the file, and the owner who signs. If any of them needs a lawyer to understand a paragraph, that paragraph is wrong and we want to hear about it at admin@torspan.com.
A plain-English summary that a legal document overrules is not plain English. It's a courtesy. This is not a summary.
Who this is between
Three names, and only one of them signs.
Torspan LLC
A Washington limited liability company, Everett, WA. Sergei Sysoev and Andrei Tcelikov.
Write to admin@torspan.com.
Your company
The contractor who pays for it. The account belongs to the company, not to whoever set it up.
If that person leaves, the account does not leave with him.
The people on the account
The crew, the foremen, the office. They use it under your company's agreement. They did not sign this, and we are not suing them if something goes wrong — that is between your company and us.
Any of them can still write to admin@torspan.com about anything on this page and get an answer from a person.
Signing up, or using the app, means your company agrees to this page. That is the whole formation clause and it does not need to be longer.
What it costs and how it ends
The shape of the price lives on What it costs, and the figure for your company comes in writing when you ask. What follows is the shape of the deal around it.
One price per active jobsite. Never by the head, never a charge for adding the man who started Monday. A jobsite is active on any day your crew wrote into it or you told us it was running, and a job that runs part of a month is billed for the days it was active.
Month to month. No minimum term. No annual contract. No implementation fee. No onboarding fee. No charge to get set up, and no charge to get out.
Billed after the month, never before it. The invoice for a month comes when the month is over and lists each jobsite by name with the days it ran. Due thirty days from the day it is sent. ACH or check.
Cancel in one sentence to admin@torspan.com, any day. It takes effect at the end of the month you already paid for. No phone call, no cancellation form, no "let me get my manager," no retention offer, no thirty-day written notice buried in a renewal clause.
If the price changes, your company gets ninety days' written notice: an email with the new number written in it, not a link back to a page that has quietly changed. You can leave over it, and your export still works.
Your records are yours
Everything your crew writes, says, photographs or uploads, and everything the system makes out of it, belongs to your company. We do not acquire any interest in it.
That is the first sentence of the ownership clause in most agreements in this category, and it is true here too.
The difference is the next sentence, so here it is.
The next sentence is normally the one that takes a great deal back. This is the whole of ours: what we need is narrow. Permission to hold your records in order to run the product for you; to show them to the people on your account; to read, index and assemble them into the documents you asked for — including a person at Torspan reading a plan or a report before it counts; and to email the documents you asked for to you and the people on your account. That is the entire license, and it has four limits written into it.
Limit 03 is the one to check. Search the privacy page for the word training and read what is there.
One more, because it is the clause a foreman thinks of first: the system never writes in a man's name and never signs as him. When it carries a question from one man to another, it says who asked, in its own voice. There is no message anywhere in this product that looks like it came from you and didn't.
Leaving
The export is built for you any day you ask — paid or canceled, current or late. No fee, and no window that starts running on the day you leave. It is delivered within five business days of your asking.
That last clause is the one that matters, and it is worth a sentence of its own. The ordinary shape of this term in field software is a retrieval window — ninety days, or six months, on request, sometimes for a fee. Which means your record has an expiry date that starts counting on the day you leave, and the day you leave is the day you are busiest.
There is no window here, because the record does not expire on the day you leave. It stays readable for twelve months after your last day, and it comes out whole at any point in them.
After you cancel: the account stays readable for twelve months. Sign-in works, export works, nothing new gets written. Then it is erased — sooner if you ask, by the end of the next business day. We do not shut down a company's operational record over an invoice, and no version of this agreement lets us.
Nothing is held back for money owed. An unpaid invoice is a dispute about an invoice. Your safety records are not collateral.
What comes out, and what it opens in, is on Your records. The numbers on the two pages are the same numbers.
If Torspan stops
In this category the file you get sued over sits with a software company, and the question is answered with a procedure for getting it back. Here is ours, and it is in the contract.
- 1. Export is never a favor and never a wind-down step. Ask, any day, and it is built for you — paid, canceled, or thirty days late — with no fee, as ordinary files that open without us.
- 2. If Torspan stops, every account is told ninety days before anything changes — by email, to every address on the account. Not a banner somebody has to notice.
- 3. Every account gets a full export built for it, whether or not anybody asks. Delivered as a link, and on request on physical media mailed to the address on file — so nobody has to be paying attention on the right week to keep his own records.
- 4. The record stays readable for twelve months after that. Read-only, no new writing, sign-in works, export works.
- 5. A written instruction, kept with the company's records, says exactly this and names who carries it out, in what order and with what access, and it is dated.
- 6. None of the five above can be quietly walked back. They are in this agreement, not only on a page. They can be changed for accounts opened later. They cannot be changed for you.
The right way to size up a software vendor is not to ask whether it will last. It is to ask what you are holding on the day it doesn't.
None of that makes Torspan permanent. Nothing makes a company permanent. What it does is make your file independent of this company's luck — which is the only version of the promise worth anything.
What we promise about it working
We will keep it running, fix what breaks, and tell you when it is broken before you have to ask.
No uptime percentage is printed here. This space carries the number and the period it covers, or it carries nothing. An empty space is a claim too.
Support is in writing, Monday through Friday, Pacific time. Every message is read the business day it arrives and answered in writing by the end of the next business day.
"Before it counts" means this: the pre-task plan is on the crew's phones as soon as it is written. It enters the record — and the daily report goes to the office — after a person at Torspan has read it. The plan's own page in the app says whether it has entered the record yet, and the plan the crew acknowledged is never rewritten: a correction is a second version with a time on it. Every opening of a customer's record by a person at Torspan is written down with the date, the person and the reason, and the customer can ask for that record and get it.
When something of ours is down: you hear it from us by email, from a person, with what happened and when it came back. Not a status badge nobody watches.
If a fault on our side keeps you from working for more than twenty-four hours in a calendar month, that month is free, applied on our side without your asking for it. A credit you have to claim is a credit designed not to be claimed.
Three words in that sentence, defined. "A fault on our side" is the service we run, including the companies we buy from to run it — not your phones, your carrier or your building's network. "Keeps you from working" means your crew cannot open the app, cannot send or read messages, or asks for a pre-task plan and does not get one. The twenty-four hours add up across the calendar month; they do not have to be in a row. The month's subscription comes off that month's invoice, or the next one, and if there is no next one it is a refund.
Not measured.
A percentage means something only when it covers a stated period that was actually measured.
What we don't promise
Said flat, with no "yet" on the end of it.
This does not make your company compliant with anything. Not with a federal recordkeeping rule, not with a state safety regulation, not with a prequalification checklist, not with your GC's requirements. It makes records, keeps them, and hands them over. Whether those records satisfy an inspector, an auditor or an attorney is a question about your work and your judgment. Any vendor who tells you their software makes you compliant is selling you a feeling.
A safety document is signed by a person, and the person is responsible for it being right. The app assembles it out of what the crew said. It does not know whether the plan is a good plan. Nobody has been relieved of reading the thing they signed.
The assistant can be wrong. It reads what it is given and it can misread. What we have built is not accuracy — it is visibility of the wrongness, and there is a difference.
- It quotes exactly, because the quoted words are cut from the stored message by the server, character by character. It cannot supply the words inside quotation marks.
- It names the sheet and the revision every answer came from, so you can go look.
- It refuses to answer about a document it has not read, and it names the document instead of guessing.
- Where nobody said it, it is blank and it says so. It does not fill in a day nobody described.
It is not payroll, accounting, estimating, scheduling, project management, invoicing or bidding, and it will not become those. It hands the daily report and the pre-task plans to the people who need them.
We do not guarantee that a record produced here will be accepted by any particular court, agency, insurer or prequalification service. Nobody can guarantee that, and everybody who implies it is hoping you will not notice the difference between kept carefully and accepted.
Every answer carries the sheet and the revision. Go look at the sheet; that is what the line is for.
Invented crew, invented job, invented sheets.
The full list of what it refuses to do, argued rather than disclaimed →
Signing a safety document in an app
A signature in the app is a legal signature. Federal law says an electronic signature cannot be denied effect solely because it is electronic (15 U.S.C. § 7001(a)), and Washington says the same in its own statute (RCW 1.80.060), which also sets out how a signature is attributed to the person who made it (RCW 1.80.080).
What an acknowledgment in this app actually consists of, so you know what you are holding:
Invented crew, invented job. If the plan changes afterward, the old version and his acknowledgment stay together.
The signature is not an image of a name. It is a row that says who, when, and on which version — and the version does not move under it later.
And the rule that makes the rest of it worth anything: nobody can sign for another man. Not a foreman for his crew, not the office for a man who went home, not a shared login, because there are no shared logins.
A record whose author is "the iPad" is not a record.
Rules for using it
Short, because this is a tool for a crew and not a public forum.
- Don't share a login. One person, one account. This is the rule the whole record rests on.
- Only upload documents your company has the right to upload. Somebody else's drawings, somebody else's submittals — that is your call to make and it is on your company.
- Don't use it to build a case against a man. There is nothing in it to build one with — no score, no location, no count of anything about a person — and if you were planning on that, this is the wrong product and we would rather you found out here.
- Don't try to break it. If you find a way in anyway, write to admin@torspan.com. We will thank you in writing, fix it, and tell you when it is fixed. We will not send a lawyer at somebody who told us the truth about our own software.
- Don't resell it or rebuild it. Use it for your work. That is the whole license.
When we stop serving an account
Three reasons, and there is not a fourth: you stop paying, the account is being used to break something on purpose, or we are shutting the whole company down, which is If Torspan stops.
What happens first: we write to you, from a person, and say what the problem is and how long you have. Nothing is switched off the same day it is noticed.
What happens then, in every case: the account goes read-only. Sign-in works, export works, nothing new is written, and it stays that way for twelve months before anything is erased. We do not take a company's records away as leverage — not for money, not for a dispute, not for anything.
If you think we got it wrong, write. There is no appeals department: the person who answers the email is the person who can change it.
If we disagree
No forced arbitration.
No class action waiver.
No jury waiver.
The standard in this category is the opposite — an agreement that pushes every dispute out of court, into private arbitration, one customer at a time, before anybody has had a disagreement about anything. It is written into the terms on the day you sign up, and the day you notice it is the day you needed it.
You keep every right you would otherwise have had, including the right to be part of a case with other people.
Before either party files anything: one writes to the other and says what is wrong. Thirty days. A software company and a contractor can usually fix a thing in a phone call, and litigation is the most expensive way either of them can be wrong.
If that fails: Washington law, and the state courts in Snohomish County, where we are. Small claims stays available to either of us for anything that fits in it.
And for a crew member who is not a party to this agreement: none of the above binds him, because he did not sign it. He can write to us at admin@torspan.com about anything on this page, and he gets a written answer.
What we're on the hook for
Every software agreement caps the money. So does this one — and then it says which part of the deal the cap does not touch, which is the part nobody prints.
Capped
The most Torspan can owe your company in damages is what your company paid, or owed, for the twelve months before whatever went wrong.
No software company can promise more than that, and one that promises more is either lying or insured in a way it has not told you about.
Not capped, because it isn't money
Handing your records back is an obligation to perform, not a sum to be capped. The export and the six commitments in If Torspan stops are things we do.
If we failed to do them, a court can order us to do them, and the dollar cap is not a way out of doing them. Money is a poor substitute for a safety file and we are not offering it as one.
And nothing above limits what we owe you if we did something on purpose. A cap covers mistakes. It does not cover bad faith, and we will not be the company that argues otherwise.
Changing this page
Something changes, you hear about it before it takes effect. Thirty days' written notice to every address on the account for anything that affects your company. A typo fix is not a change, and gets written down anyway.
You don't have to subscribe to anything to find out. There is no policy-updates mailing list to join, because the notice goes to the people it affects. If you are a customer, it comes to you.
The old version does not disappear. Every version stays readable at its own address, and What changed says in one sentence what moved and why. You should be able to see what a company took out, not just what it left in.
And the two rules from the top still apply to every change: the reading that is better for you holds if two of our pages disagree, and a change that is worse for you applies to accounts opened later, not to you.
The short boring part
Kept short on purpose, and every sentence in it is one somebody actually needs.
- Who may have an account. People on your company's payroll or working on your jobs, put on the account by your company. The app is not for children and is not directed to anyone under 13. We do not knowingly set up an account for anybody under 16.
- Language. This page is written in English. If we publish it in another language and the two versions disagree, that is our defect — and until it is fixed, the version that is better for you is the one we will honor. Your crew's records are always kept in the language they were written in.
- If we are bought or the company is transferred, your records go with this agreement, not to any bidder, at any price, as a separate asset. What transfers is this agreement, and the training limit, the ownership clause and the six commitments in If Torspan stops travel with it unchanged. You will be told before it happens, not after.
- If one part of this is unenforceable, the rest still stands, and the unenforceable part gets rewritten to do what it was trying to do.
- This page is the whole agreement between your company and Torspan about AirOrchestra. Nothing said in an email replaces it — but if Torspan promised you something in writing and this page contradicts it, write to us and we will make one of them right rather than pointing at the other.
- We can hand our side of this to somebody else only in a sale of the whole company, and only with everything in it intact. You can hand your side to a company that buys yours, and you do not need our permission to do it.
What changed
Every version of this page stays readable at its own address. This is the list.
| Date | What changed | Read it |
|---|---|---|
| Sep 4, 2026 | The license to hold your records is back, because we hold them again. The product runs on a service Torspan operates, and the clause for a computer your company buys is gone with the computer. Canceling makes the account read-only for twelve months and then erases it, as the first version said. If Torspan stops leads with the export built for every account. The written instruction that carries it out stays as a commitment and names who carries it out; it no longer says it does not depend on anyone at Torspan being reachable. The twenty-four-month price lock, the first-month credit and the thirty-day refund are not in this version; the ninety days' notice before a price change is, and so is billing after the month. The free-month credit for a fault on our side stays, with its three words defined. | The one you are reading |
| Aug 25, 2026 | The licence to hold your records and move them between our machines is gone, because there is nothing of yours on a machine of ours. Cancelling no longer makes the account read-only for twelve months and then erases it — the computer keeps working and nothing is erased. If Torspan stops now leads with the fact that nothing has to be handed back. A clause was added for the computer your company buys from Apple, on which we take no margin. And one term is narrower than what it replaced: the free-month credit is now scoped to a fault on our side, because the machine's uptime is in your building and we will not publish a promise about a room we are not standing in. | terms/2026-08-25 |
| Aug 22, 2026 | First version. | terms/2026-08-22 |
The old version stays at its own address and the change is described here — including the changes that were in our favor, and the one on the row above that is not.
Software's one attempt at a terms of service whose edit history you could read was Basecamp's public policy repository. It was archived on 26 December 2023 and is now read-only (github.com/basecamp/policies). That is the whole field. The bar is on the ground and we are stepping over it with a table.
Say it before you buy, not after.
If a sentence on this page is not what you need it to be, say so before you buy rather than after. A term is easier to change before a signature than after one, and this is the page where that is literally true.
admin@torspan.com — read the business day it arrives, answered in writing by the end of the next business day.
The same commitments in plain sight, with the reasons under them — Your records.
Everything this product refuses to do, said without a "yet" on the end — What it won't do.
The other half of the agreement, what's collected and what never is — Privacy.