Dispatch is software for scheduling and publishing posts to LinkedIn. These terms are between XONIK Technologies Private Limited, company number U72200MP2006PTC018444, registered at 3/3B, Saket Nagar, Bhopal, Madhya Pradesh 462024, India (“we”), and the organisation that opens an account (“you”). Accepting an invitation, opening an account or paying an invoice accepts them.
An account, the panels, and a worker that publishes approved posts at the times you set. We publish only what somebody in your account has approved. Nothing is published automatically on your behalf, and no post is ever generated and published without a person seeing it first.
The software is licensed, not sold, in both editions. We grant you a non-exclusive, non-transferable, revocable right to use it for the term you have paid for, for your own business and for the brands in your account. That right ends when the term does. Everything else stays ours: the software, the source, the interface, the name and everything we build. Nothing in these terms transfers ownership of any of it, and nothing here is a sale.
There are two editions, and which one you have changes what these terms cover.
What a licence does not include is the source. You may run the software; you may not copy it beyond the installations the licence names, decompile it, resell it, or remove or alter the licensing, integrity or attribution mechanisms in it. We do not sell the source, and we would rather say that here than have it discovered in a procurement call. Source escrow can be arranged where the worry is what happens should we stop: that is a reasonable worry, it has a standard answer, and it goes in the order form.
Your model key is your own in both editions, and in the hosted edition your platform application can be too. The model key is yours from your own vendor and the calls leave under it. A hosted account may run on its own developer application with the network rather than on ours; a licensed installation always does. So your access to the network, your model spend and, in the licensed edition, your data do not depend on our goodwill — which is the part of the question that matters.
When a licence term ends. A licensed installation warns you on every screen for the notice period in your licence before the term ends, and names the date. If the term ends without being renewed, it stops publishing. It does not stop opening: you keep signing in, reading and exporting every post, every source and every approval for the period the licence sets out, after which the installation closes and tells you where the export is. Taking your own material away from you on your own server the moment an invoice lapses is not a remedy we want, and it is not one we take.
You will not use Dispatch to publish anything unlawful, defamatory, harassing, or infringing; to impersonate anybody; to publish on behalf of a person or organisation who has not authorised it; or to attempt to reach another customer's account. We may suspend an account we reasonably believe is doing any of these, and will say why.
These four are the whole of what assistance means here, and each of them is a thing the software does rather than a thing we say.
The network this product publishes to has its own rules for a tool that puts a language model near published content. We honour them as behaviour rather than as a promise, and each of these is checked by an automated test rather than remembered:
This is the wording somebody is shown before they agree to the first of them, printed here from the same text the consent screen uses, so the two cannot disagree:
AI-assisted — Writing first drafts
A model is given your brief, the facts confirmed on this account and the sources behind them, and writes a draft.
What is sent, and what is kept: Your briefs, your confirmed facts and your own published posts are sent to the model that writes the draft. They are not used to train anybody's model and are never sent with another account's material.
What stays yours: Nothing is published. Every draft arrives as a draft, on a screen where you can rewrite it, and somebody has to approve it afterwards.
Accuracy: Assembled with the help of a language model. Check each figure against the source shown beside it before acting on it.
This consent covers this use only. It can be withdrawn at any time, and it stops applying to the next request rather than at some later point.
Research briefs, draft post copy and the written summary in the monthly report are assembled with the help of a language model. The call is made under your own key, from your own account with your own vendor. You enter that key yourself; it is tested at the moment you enter it and sealed before it is stored. Two things follow, and they are the two that matter commercially: the model bill is yours and reaches you from your vendor rather than from us, and we do not resell model access or mark it up — we could not, because the calls do not leave under our key. If you stop paying us, your key keeps working. It was never ours to switch off.
Three more things follow, and we would rather you read them here than discover them.
This report was assembled with the help of a language model. The performance figures come from LinkedIn's own reporting and are not generated; the written summary is. A language model can be wrong while sounding certain, so read the summary against the figures and the cited sources above it, and verify anything you intend to act on or repeat.
We use LinkedIn's official API under their developer terms. We do not scrape, we do not automate connection requests or messages, and we do not build or sell a database of people. Some things are impossible through the API for everybody — newsletters and long-form articles have no endpoint at all — and the product names those rather than implying otherwise. If LinkedIn changes or withdraws the access this depends on, the service may stop working through no act of ours; we will tell you, stop charging you, and you may export everything.
Your plan sets how many brands, destinations, sign-ins and posts a month your account has, and a share of the application-wide LinkedIn call budget. These are the plans as sold, and every figure in this table is read from the same table the software refuses on — it is not typed beside it:
| Plan | Brands | Destinations | Sign-ins | Posts a month | Price |
|---|---|---|---|---|---|
| Solo | 1 | 3 | 2 | 40 | $228 a year |
| Team | 5 | 15 | 5 | 200 | $588 a year |
| Agency | 15 | 45 | unlimited | 600 | $1,548 a year |
A sign-in is somebody who works in the panel. A client who only reviews and approves opens a signed link with no account behind it and costs no seat. Anything beyond the listed plans is quoted, and what is quoted is what that account gets. When a limit is reached the service refuses the work and tells you why. LinkedIn limits calls per application across all customers, so publishing may be paused for everyone to prevent the application being rate limited. A post takes its place against the monthly allowance when it is approved, and gives it back if it is pulled, sent back to draft, or fails for good.
Plans are billed in advance for the period shown on your invoice, due within 14 days. Reminders are sent at one and eight days overdue. An invoice more than 16 days overdue pauses publishing on the account and on every client brand under it. It does not delete anything, and paying restores exactly what the suspension stopped. Prices exclude any tax that applies where you are. An invoice renews automatically at the end of each period unless you have cancelled.
If you leave part-way through a year, the section below says exactly what comes back and how it is counted — written down rather than left to be argued about later.
You can move up or down at any time, mid-year, by writing to us. There is no notice period and no penalty for moving.
Whatever is left on the period you are on comes off the one you are moving to, worked out by the day. Moving up, you pay the difference rather than the whole year again. Moving down, the balance stays on the account as credit against your next invoices until it is used up. That credit is not paid out in cash — it is money you have already paid for service, and it keeps buying service. Refunds are the section below, and they work differently, because that is money leaving rather than money staying.
You can cancel at any time from the panel. Nothing is deleted when you do, and you can export everything you have — posts, images, sources, approvals, the publishing record and the audit log — at any time, including after cancelling. Erasing the account is a separate button and it is yours to press.
Two rules cover refunds, and they are the whole of it.
Beyond those, we refund where we have materially failed to provide the service. We will not withhold a refund we owe because the account was used — using what you paid for is not a reason to keep the money for the part you did not.
We may end an account with 30 days' notice, or immediately for a serious breach of the acceptable use section. In either case you keep export and erase afterwards, for as long as the account exists. We do not delete an account on a timer: your data stays until you erase it, and erase is a button in the panel.
We will not publish anything nobody approved, sell or share your content or your contacts, use your posts or your data to train any model, or read your LinkedIn data beyond what publishing and reporting require.
Your content is yours. You give us only the permission needed to store it, show it to the people in your account, and publish it to the destinations you choose. The software, the panels and everything we build stay ours. Nothing in these terms transfers ownership either way.
We will provide the service with reasonable skill and care. We do not promise it will be uninterrupted or error-free, and we do not offer an uptime service level: there is no measured operating history to commit against, and a promise nobody can keep is worse than no promise. When there is one, it will be offered in writing. Except as stated here, and to the extent the law allows, there are no other warranties.
Dispatch does not publish to LinkedIn. It asks LinkedIn to publish, through LinkedIn's own API, and LinkedIn decides. The same is true of every other service this product depends on — the hosting, the mail, and any language model connected to it. None of them is ours, none is under our control, and none has promised us anything.
So we are not liable for a loss you suffer because one of them failed, changed or refused. In particular, and without limiting that: LinkedIn changing, restricting, deprecating or withdrawing its API; LinkedIn rejecting, throttling, hiding, removing or reducing the reach of a post; LinkedIn suspending or restricting an account or a page; an access token being revoked; an outage at any of them; a change to their terms, their limits or their prices; or a language model returning something wrong, biased or unusable. Nor are we liable for what any of those services does with data you send them under your own agreement with them.
What we will do is tell you when we know, keep the record of what was attempted and what came back, and — where a failure lasts more than 30 days — let either of us end the account, with the unused part of the period refunded. If LinkedIn withdraws the access this product is built on, the product stops working, and neither of us has a claim against the other for that.
Nothing publishes from Dispatch without somebody in your account approving it by name. That approval is the point at which the words become yours.
What Dispatch does is put the evidence next to the claim: the figure, the publisher, the date, the sentence it was taken from, and a flag when the source has moved since. What it does not do is certify that a claim is true, that a source is reliable, or that a post is lawful, accurate or right for your audience. Research briefs and draft copy are assembled with the help of a language model, and a language model can be confidently wrong. Read the post and check the sources before you approve it. If you approve something inaccurate, misleading, defamatory or in breach of somebody else's rights, that is yours, and the indemnity below is where that risk sits.
A published post cannot be unpublished by us. LinkedIn's edit exposes the text only and never the image, and deleting a post is permanent and is yours to do. There is no version of this where a mistake is quietly fixed afterwards — which is the whole reason the approval carries a name.
Published posts cannot be unpublished by us: LinkedIn's edit exposes text only and never the image, and deleting a post is permanent and yours to do.
To the extent the law allows, neither of us is liable for indirect or consequential loss, loss of profit, loss of revenue, loss of goodwill, loss of anticipated savings, or loss or corruption of data. Our total liability, in aggregate across every claim arising in any twelve months and however it arises — in contract, in tort including negligence, under statute or otherwise — is limited to the fees you actually paid us in those twelve months. Where you have paid us nothing, as on a trial, that limit is nothing.
That figure is a ceiling, not an entitlement and not an agreed refund. Reaching it means proving a loss of that size that we actually caused. Having paid us is not itself a loss, and having used the service is not a loss at all.
Nothing here limits liability for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot lawfully be limited. Those exceptions are not generosity: a limitation clause that tries to exclude them is one a court can strike out whole, taking the rest of this section with it.
You will cover us against a third-party claim arising from what you published — its content, the rights in it, or the authority to publish it. We will cover you against a claim that the software itself infringes somebody's intellectual property.
This agreement is with XONIK Technologies Private Limited, the company. A claim arising out of it is against the company and not against any director, officer, employee, contractor or shareholder of it personally, and you agree not to bring one against them. This is how the limits and exclusions above are meant to work: they protect the company and the people who work for it to the same extent, and neither of us can get round them by suing an individual instead.
This does not, and cannot, affect a person's own liability for fraud, for death or personal injury caused by their negligence, or for anything a law places on them directly rather than on the company.
Neither of us will disclose the other's confidential information, except to people who need it and are under the same obligation, or where the law requires it. This lasts three years after the account ends.
The privacy notice says what we hold and why. Where we process personal data on your instruction, the data processing addendum applies and forms part of these terms.
Neither of us is liable for a failure caused by something genuinely outside our control — including a change to, or withdrawal of, LinkedIn's API. If it lasts more than 30 days either of us may end the account and we will refund the unused part of the period.
Notices to us go to privacy@xonik.com. Notices to you go to the email address on your account. Either counts as given when sent, unless it bounces.
We will give 30 days' notice by email before changing these terms in a way that affects you, and you may cancel in that window without penalty. A change required by law or by LinkedIn may take effect sooner, and we will say so.
These terms are the whole agreement between us about the service. If a court finds part of them unenforceable, the rest continues. Not enforcing something once does not waive it. You may not transfer this agreement without our consent, which we will not unreasonably withhold; we may transfer it as part of a sale of the business, and will tell you. Nobody who is not a party to these terms may enforce them.
Before either of us starts proceedings, the one with the complaint will put it in writing to the other — what happened, what they say it cost, and what they want done — and we will both try in good faith to settle it within 30 days. Either of us can still go to court sooner where urgent relief is genuinely needed, or to protect a right that would otherwise be lost.
This is not a way of putting a claim off. It is here because most disagreements are a misunderstanding about what the software did, and the publishing record and audit log usually settle those in an afternoon.
These terms are governed by the laws of India, and the courts at Bhopal, Madhya Pradesh have exclusive jurisdiction over any dispute.