Callboard
These terms are between you and CallBoard Software LLC (“Callboard”, “we”, “us”), an Oregon limited liability company, at 1303 SE Stephens St, Roseburg, OR 97470. You can reach us at sales@callboardsoftware.com.
In force from 26 October 2026.
Metered use of Repartee. It is not a file you keep and not an application you log into: it runs on machines we own in Oregon, it takes the file you send it, the work is done on our own graphics cards, and it hands files back to you. You are not buying the source, a seat, or a copy of anything.
What you buy is units (1,000 tokens each). One unit is the single piece of work this program charges for, the storefront prices it by the unit, and every job report tells you how many units (1,000 tokens each) it did and how many it did not.
There is no account and no password. The key is the account. It is one line of text, shown to you exactly once, at the moment it is made — only a one-way hash of it is kept here, so we cannot look yours up, cannot tell you what it is, and cannot send it to you again. A lost key is replaced, never recovered.
Every key arrives with 200 units (1,000 tokens each) already on it. That allowance needs no payment, no card and no agreement to these terms beyond using it, and it is how you find out whether the program is any use to you.
Paid units (1,000 tokens each) are bought in bitcoin, through a checkout server we run ourselves, at the prices on the storefront. They are added to the key you buy them for, on top of its free allowance.
Buy from the Buy more box inside the program and the units (1,000 tokens each) are added on their own as soon as the bitcoin network confirms the payment. Buy from the storefront instead and paste the invoice number from your receipt into that same box. Before anything is added the program reads the invoice back from our checkout and checks it is ours, for this program, for the full price of the plan, and paid. Each payment adds its units (1,000 tokens each) once, to one key.
A unit is charged after the work came back and passed the program's own checks, never before. A unit that failed on the graphics card, timed out, came back unreadable, or was held back by the program's own word list is not charged — and the job report names it and says why, rather than quietly leaving it out of the total.
When an allowance is spent, the next job is refused before any work starts, and the refusal prints how many units (1,000 tokens each) were used. You cannot be taken past your allowance by a job that turned out to be bigger than you thought: there is no balance to go negative, there is a count, and it stops.
We do not round a job up, bundle units (1,000 tokens each) you did not use into one you did, or charge a minimum per job. One unit of work that succeeded is one unit.
On our machines, in Oregon, inside that one program's own folder. The file you send is written there so the job can run, and the files the job produces are written there so you can download them. The program refuses an upload larger than 1 MB rather than starting work it cannot finish.
There is no automatic deletion today, and we are not going to print a retention period this software does not enforce. A job's files stay in that folder until they are deleted by hand. Nothing reads them after the job, nothing indexes them, no gallery or thumbnail cache is built from them, and no copy of them leaves the machine — but they are still there.
Write to sales@callboardsoftware.com and we delete a job's files. On the day the program deletes them on its own, the clock it keeps will be printed on this page and on the privacy page, and not before.
Apart from the files, what the program writes down is: a one-way hash of your key, your unit counts, and one row per job — the name of the file you sent, which variant you asked for, how many units (1,000 tokens each) finished, how many were held back, the times, and one sentence saying how it ended. There is no name, no address, no company and no password anywhere in it, because the program never asks for any of those.
It does not allow reselling access, running jobs on behalf of another business, sharing your key outside your own business, or any attempt to get work out of the program without it being counted.
The key stops being able to start a job, and says so in a sentence with the number in it. That is the whole of it: nothing is deleted, nothing is locked, and no clock starts.
Every file the program has already handed you is on your own computer and stays yours. You do not need us, a working key, or an internet connection to open any of it, and we could not take it back if we wanted to. There is nothing of yours in this program to be locked out of — what it holds is the jobs you sent it, not your books.
This software drafts, sorts, flags and refuses. It is not legal advice, tax advice, a compliance review, or a person reading your work. Every threshold, platform rule, jurisdiction table and word list in these programs holds what we put into it or what you entered, and each of the screens that holds a rule says so on it.
The judgement in these programs comes from a language model running on our own graphics cards, and it is wrong sometimes. Where a program can check its own answer it does, and where it cannot it says on the page that the answer is a draft. A program that flags something is not an opinion that you are in breach; a program that passes something is not an opinion that it is lawful, or that a platform will accept it. Nothing here replaces your lawyer, your accountant, or your own eyes on what came back.
We warrant that the program will do what the storefront it was sold from says it does. We do not warrant that it is free of faults, that it fits a purpose we were not told about, that any law or platform rule it was built around has not changed since, or that a given job will succeed.
There is no uptime promise. These programs run on hardware we own rather than somebody else's cloud, which is the point of them — and it means that when a machine is down or a graphics card is busy, a job waits or it fails. A job that fails costs you nothing, and that is the remedy for it.
You may only send work from a lawful business. You are responsible for what you send, for having the right to send it, and for what you do on the strength of what comes back. We do not review, moderate or vet the files you send beyond running the job you asked for, and nothing any of these programs says is clearance to publish anything.
Two things must never be sent to these programs: material involving anybody under 18, and material involving anybody who has not consented to it. That is not a policy we enforce by inspection — we are telling you plainly that it is a term of using this at all.
If we are liable to you for anything arising out of these terms or the software, that liability is limited to the fees you paid us in the twelve months before the claim. We are not liable for lost profit, lost business, fines, penalties, or the cost of a dispute with anybody else. Nothing here limits liability that cannot lawfully be limited.
You can stop at any time by not sending another job — see the refund policy for what happens to units (1,000 tokens each) you have paid for and not used. We may change these terms for future purchases and will say so at sales@callboardsoftware.com before the change takes effect; the terms you bought units (1,000 tokens each) under govern the units (1,000 tokens each) you already bought.
We may stop a key without refund if it is being resold, used for a business it was not issued to, shared outside that business, used to try to get work out of the program without it being counted, or used to do something unlawful.
The law of Oregon governs these terms, and a dispute neither of us can settle goes to the courts of Douglas County, Oregon.
Written in plain English to be accurate rather than clever. It is commercial software terms, not a solicitor’s draft, and it should be read by one before the company trades on it.