What Dispatch holds about people, why, and for how long. The controller for the people who use the panels is XONIK Technologies Private Limited, registered at 3/3B, Saket Nagar, Bhopal, Madhya Pradesh 462024, India. Questions, requests and complaints go to privacy@xonik.com, and we answer within 30 days.
We do not collect LinkedIn profile data about people who have not interacted with your posts, build audience or lead databases, scrape anything, or run advertising or behavioural analytics. There are no analytics cookies, no advertising cookies and no tracking scripts. We do not use anything here to train a model, ours or anybody else's.
No request leaves the page. Every file a page needs — its markup, its script, its typefaces — comes from this installation and nowhere else, and the content policy the server sends names no outside origin at all, so your browser would refuse one even if a page asked. Nothing about your visit reaches a third party, and nothing here is a tracker.
This paragraph used to say the opposite: one third-party request was made, for the typefaces, from Google Fonts — which told Google the address you were browsing from and which browser you used. It said so, and it said we would rather serve the fonts ourselves. We now do. The history is left here rather than quietly rewritten, because a privacy notice that only ever describes the present is one you cannot tell has changed.
| Account people, content, approvals | Performing the contract with your organisation |
|---|---|
| Audit log, sign-in addresses, throttling | Our legitimate interest in keeping the service secure and being able to show what happened |
| LinkedIn tokens | Performing the contract, on the authorisation the member gave through LinkedIn's own sign-in |
| Invoices and payment records | A legal obligation |
The current list, with each provider named, is on the security page and is kept there rather than here so it cannot go out of date quietly. Nobody else sees it. We do not sell personal data, and there is no circumstance in which we would.
The database and the graphics sit on one server in the region named on the security page. Where a provider necessarily processes data outside that region, the transfer relies on the standard contractual clauses or on an adequacy decision, whichever applies to that provider.
Every table has a written rule and the deletion runs on a schedule rather than on a query filter. The rules, and whether anything is overdue, are published on the security page. In summary: another member's profile data for 24 hours, comments and mentions for six weeks, reporting figures for a year, approvals for seven years because that is how long the question they answer gets asked, and everything else for as long as the account exists. Invoices go with the account when it is erased, so download them from the billing tab before erasing if you need them for your own records — we cannot recover them afterwards.
When an account is erased, everything under it goes with it — immediately, permanently, and including the image files on disk. One audit row survives recording that an erasure happened, without the content.
These are the permissions this installation asks for when somebody connects a destination, and they are the whole request:
openid — identifies the person who authorised the connectionprofile — identifies the person who authorised the connectionw_member_social — publish to a person's profileNothing else. The permissions above do not allow, and so this installation never does, any of the following: a person's own follower count; analytics for a person's own posts; analytics for a person's profile; follower counts and demographics; how far through a video people watched; impressions and engagement for a page's posts; list the pages this person administers; publish to a company page; read a page's own posts; read comments on a page's posts; read many posts' engagement in one call; reply to a comment as the page; see mentions of a page by other members; show a commenter's name, headline and picture; webhook notifications instead of polling. A permission that is not asked for cannot be used even if the network offered it.
Taking it back. Disconnecting a destination inside the panel destroys our copy of the token — the stored value is wiped rather than marked inactive — and nothing can be published to it afterwards. The grant itself lives with the network, and the member who gave it can withdraw it there, in their own account's permitted-services settings, without going through us. Either is enough on its own.
Access, correction, erasure, restriction, objection and portability. Export and erase are both buttons in the panel, so two of these do not require asking us: the export is a complete archive of everything the account holds, in formats that open without us. For the rest, write to privacy@xonik.com.
Where a business uses Dispatch for its clients, that business is the controller for that content and we are its processor; a request about it should go to them and we will help them answer it.
You can complain to the supervisory authority where you live or work. In the UK that is the Information Commissioner's Office; in the EU, your national authority. We would rather you told us first, but you do not have to.
Two things are kept in your browser, and neither is a tracker.
session. It is what keeps you signed
in, and the application does not work without it. HttpOnly, so no script
can read it; SameSite=Lax, so another site cannot spend it; Secure, so it
is never sent over plain HTTP. It expires when the session does —
twelve hours by default — and signing out deletes it.dispatch.theme. It records
whether you chose light, dark, or to follow your system, so the choice
survives when you open another page. It is stored in your browser's local
storage, never sent to us, and nothing is written there at all until you
press the switch yourself.That is the complete list. There are no analytics cookies, no advertising cookies, no tracking pixels and no third-party cookies of any kind. Both items above are exempt from the consent requirement — one because the service you asked for cannot run without it, the other because it exists only when you choose it — which is why Dispatch has no cookie banner. There is nothing to consent to, and a banner asking you to consent to nothing wastes a click and teaches people to dismiss the ones that matter.
You can clear both at any time from your browser's site settings, or by signing out and pressing the theme switch back to “system”. Clearing them signs you out and forgets the theme; nothing else is lost.
Dispatch is a tool for businesses and is not directed at children. We do not knowingly hold data about anybody under 18, and accounts are opened by organisations rather than by individuals. If you believe a child's data has reached us, write to privacy@xonik.com and we will delete it.
India's Digital Personal Data Protection Act 2023 asks us to name the person who will answer a question about your data. That is Amit Govil, privacy@xonik.com. A question, a correction, a request to erase or a complaint can go there and we will answer within 30 days. If you are in the EU or the UK you may also complain to your own supervisory authority, and nothing here takes that away.
None. Nothing here decides anything about a person automatically, and nothing is profiled.
The model provider is your sub-processor, not ours. That is not a form of words — it is how the software is built, and the reason it is true is worth a sentence. You enter your own key, from your own account with your own vendor. The call is made with that key. We hold no model account of our own, we do not resell model access and we do not mark it up; we could not, because nothing leaves under our key. So the vendor's terms that apply are the ones you agreed with them, the bill goes to you from them, and if you stop paying us the key keeps working.
That is why no model provider appears in our sub-processor list on the trust page: none of them receives anything from us. The one you chose appears on that page as yours, named from this deployment's own settings, so an auditor reading it can see which vendor your account sends to.
What is sent: the brief, the facts confirmed on that account, the sources behind them and that account's own published posts, and for a reply or a sentiment reading, the text of the comment. LinkedIn member data is not sent — not the names, headlines or photographs of people who comment on your posts, and not your account holders' personal data. Nothing from another account is ever sent with yours.
The same is true of the platform application. An account may run on its own developer application with the network rather than on ours, in which case its relationship with the network is direct and its rate limits are its own. Using ours is the default and is simpler; either way the access token belongs to the account and is sealed before it is stored.
If we ever start calling a model on our own account rather than on yours, we will name the provider in the sub-processor list, say what it can see, and give 30 days' notice before it begins.
Assembled with the help of a language model. Check each figure against the source shown beside it before acting on it.
If personal data is exposed, we will tell the affected accounts and the supervisory authority within 72 hours of becoming aware, and say what we know even where that is not yet everything.
If this notice changes materially we will email the accounts it affects before it takes effect. The date at the top is when the current version started.
Questions or complaints about your data: Amit Govil, privacy@xonik.com, at privacy@xonik.com.