VERISCO Shield Monitor and respond
Data and privacy
What VERISCO records about your staff, how to record less of it, how long it is kept, and how to export or erase it.
Open Data & Privacy in your console. You are the data controller for everything on the monitoring pages.
It reduces what is written, not what is shown#
These settings run before a record is written. Switching something off means rows that never held it in the first place. A filter applied when reading would leave the data on disk and call it privacy.
The consequence: turning a level down does not clean up history, and turning it back up does not recover what was not collected. Settings apply to new records.
What you can control#
| Data | What it is |
|---|---|
| Device | The browser and operating system of a sign-in. |
| IP address | Can be stored truncated instead of whole. |
| Location | The coordinates derived from an address. |
| Replay | The detail kept for reconstructing a session. |
Each has its own level. Level 0 follows the platform default.
Pseudonymous view#
A separate switch. When it is on, people are shown by a pseudonym across your console and are not linked to their timeline.
- The pseudonym is stable for a person within your tenant. You can still tell "the same person again" from "somebody new" without knowing who they are.
- It is a display choice. It changes what your console's users see. The collection levels above change what exists.
The AI assistant follows this setting: it can tell you that an account is failing repeatedly without naming it.
Retention#
How long records are kept before they are removed automatically. You can override the platform default for each kind of record.
Export and erase#
| Action | Role | Effect |
|---|---|---|
| Export | Administrator and above | Take your monitoring data out. |
| Erase | Owner | Remove the records held about one person. |
Erase cannot be undone
There is no recovery step. Confirm the subject before running it.
What this does not cover#
These settings govern what VERISCO records about sign-ins to your application. They say nothing about the data inside your own application or your own user database. VERISCO reads your user table to check credentials; in read-only mode it never writes to it.
Something missing or wrong on this page? Tell us and we will fix it.