Six promises
The shared system is built to serve several clients on one set of services. A client is one organisation, and keeping clients apart means these six things, without exception.
1. No client can see another’s work. Watch lists, keywords, topics, trends, forecasts, stance, cases, flags, reports, drafts, labels, media verdicts, audit trail and spend stay with their client, on every screen and in every export, search, similar-posts answer and error message.
2. No client’s choices move another’s results. Keywords, labels, corrections, rules and thresholds change only their own client’s topics, alerts, forecasts and calibration.
3. Each client has its own daily budget, so a busy day for one cannot pause collection for another.
4. Each user belongs to one client. A few named people on our side can switch between clients, and each switch is written to the audit log.
5. Every stored row can be traced to the client it belongs to, and the build fails if a table or query does not say.
6. A client that leaves takes its data with it, and the rest is deleted without touching any other client’s.

Public posts are shared, your work is not
A post that two clients both watch is public, so one collected copy of it serves both. What each client does with it, such as its topics, labels and cases, is stored for that client alone.
Detection models are shared. Labels and calibration are kept per client: one client’s labels never change another’s calibration, and a client without enough labels of its own starts from the shared starting calibration, never from another client’s.
A client that needs its data in a database no other client touches runs its own installation instead: the same build, on its own servers.
How it can be shown
Separation is enforced in one place and tested, so it can be demonstrated rather than taken on trust.
01
One filter for every read and write
Every stored row carries the client it belongs to, and one central filter adds that client to every read and write. The signed-in session carries the user’s client.
02
Queues, caches and files too
Work queues, caches and file folders are keyed by the client, not only the database tables.
03
A test the build must pass
The build fails on any table or query that does not say which client a row belongs to.
04
A second client in the test data
A made-up second client is tested against the first: every screen and data view returns nothing of the first, and one client’s labels leave the other’s calibration unchanged.
05
Switches on record
Each time one of our named people switches between clients, the switch is a line in the audit log.
Leaving
First
Your data, exported
The client’s data is handed over as CSV files with a PDF summary.
Within 30 days
The rest, deleted
Everything else the client held is deleted, and no other client’s data is touched.
Shared copies
Public posts
A collected public post that another client still watches stays for that client; one that no client watches any more is deleted with the rest.
Put the six promises to your reviewers, then decide between the shared system and an installation of your own.
Request a demo/trust/separation · Client separation