Products
Data controls
You decide what is kept, for how long, and when it is erased.
What it does
Verification handles personal data, so the platform gives you controls over its life. They fall into four groups: how long data is kept, how it is erased, what leaves the platform in callbacks, and who can reach it.
Retention
Retention is a setting you choose per scenario. Sessions keep their data for the period your scenario sets, so a flow that needs a short life for its data and a flow that needs a longer one can differ. See the scenario editor.
Erasure
Erasure is available by API on request.
- The erase call destroys the personal data of a session.
- A
PD_ERASURE_COMPLETEwebhook confirms that the destruction is complete. - An erasure log lists what was destroyed, when, why and by whom.
The data protection overview describes the lifecycle in full, and the webhooks documentation describes the event.
Callbacks without personal data
Webhooks can leave personal data out of the callback.
- The body of the callback request can be encrypted.
- The callback can omit names, document data and images and keep only the session identifier, which links to the session. Your system then fetches the result by that identifier.
Access
- Roles limit what each team member can do in the dashboard.
- A login log records who signed in.
- Token expiry lets an API token run out on a date you set.
- An IP allowlist limits the addresses from which API requests are accepted.
Deployment
You can run the platform in our cloud, or have our engineers install it on your own servers. See deployment.
Next
Read the data protection overview for the whole lifecycle, or write to us with a security question.
Questions, answered plainly
Can I choose how long session data is kept?
Yes. Retention is a setting you choose per scenario.
How do I erase a person's data?
Call the erase method through the API. A webhook confirms when the destruction is complete, and the erasure log records what was destroyed.
Can callbacks leave out personal data?
Yes. A callback can omit names, document data and images and keep the session identifier, or its body can be encrypted.
Who can access the data?
Access is controlled with roles, a login log, token expiry and an IP allowlist.