
That holds for your own installation and for the shared system alike. The drawing marks the country as one region, because that is what the configuration names: no place within India is given.
What is stored in India
| Data | Where it is kept |
|---|---|
| Collected posts, accounts and the links between them | The database, in India |
| The records built from them: topics, verdicts, coordinated groups, forecasts, flags, labels and cases | The database, in India |
| Media, key frames and transcripts | Object storage, in India |
| Evidence packs, sealed and checksummed | Object storage, in India |
| Reports | Object storage and the console, in India |
| Archives and exports of older records | Object storage, in India |
| Work queues and caches | In India |
| Service logs and traces | In India |
| The audit log | The database, in India |
Processing
Data is stored in India, but some of the work on it is done by outside services. This section names each kind and what it may be sent.
The installation’s configuration lists each outside service with an external address by kind, with the classes of data it may be sent. The configuration check fails if an outside service with an external address is switched on without such a row.
Language models write the summaries, the written explanations of verdicts and the headlines of reports, give a second stance reading for posts with very wide reach, and judge whether a suggested trend term is about what you watch. They may receive key frames, transcripts, post text, handles and the results of the media checks; never credentials, and never who your operators are. Where your organisation requires it, a language model in India can be used instead.
The data service that collects public posts receives the keywords and handles it is asked to search. It also receives key frames and a link to the media, because reverse image search runs through it.
Reverse image search receives key frames. By default it is given a short-lived link served from your installation in India, with no storage address and no credential in it.
The outside sending service receives the text, any media (such as a video to upload or an image to post) and the target of each approved reply, comment, message or post sent through it, and the official account it goes out from. It holds the tokens of your official accounts; the product holds none. Platform reports are filed through each platform’s own form, with the evidence pack.
Alert and delivery channels, a messaging service and email, receive alert messages about rule firings, the system’s own operational alarms, and links to reports; an internal report can have its PDF attached.
Outside media-check services are off by default in the configuration for an installation. Switching one on is a change to the protected settings, and the list then shows what it may receive: at most six key frames, or an audio clip of at most 60 seconds, per call.
Whatever these services return is stored in India, with the rest of your data.
On your own servers
As your own installation, on your own servers in India, every service and store of Media Verdict runs for your organisation alone, in a database no other client uses.
The list of outside services with an external address is part of that installation’s configuration, so your reviewers can read which are switched on and what each may receive.
Read the list of outside services with your data protection officer, row by row.
Request a demo/trust/data-residency · Data residency