Third Party Index

Workvivo

workvivo.com

Transparency

Strong

Breakdown
Subprocessor list30 / 30
Processing locations8 / 8
Purposes7 / 7
Data processing addendumnot found0 / 12
Trust centernot found0 / 8
Privacy policy6 / 6
security.txtnot found0 / 6
Security page5 / 5
Status page5 / 5
Vulnerability disclosurenot found0 / 5
Pages still reachable8 / 8
Total69 / 100

Only documents we can retrieve count: a page behind a login or a broken link scores nothing.

Badge

Workvivo transparency rating

For Workvivo's own site; it updates with the rating.

<a href="https://thirdpartyindex.com/vendors/workvivo"><img src="https://thirdpartyindex.com/badge/workvivo.svg" alt="Workvivo transparency rating on Third Party Index" height="20"></a>
[![Workvivo transparency rating on Third Party Index](https://thirdpartyindex.com/badge/workvivo.svg)](https://thirdpartyindex.com/vendors/workvivo)

Documents

DocumentVerifiedChangedEvidence
Subprocessor list snapshot
Privacy policy snapshot
Terms snapshot
Security page snapshot
Status page statuspage snapshot

Subprocessors

4 third parties. CSV · Atom

NamePurposeLocationListed since
Amazon Web Services Cloud Services Provider; Intelligent Features Service Provider (Optional)Ireland (or USA or UAE if selected by Customer)
Anthropic Intelligent Features Service Provider (Optional)USA
Sendbird Inc. (Optional); Chat FunctionalityUSA, EU
Zoom Communications, Inc. (Optional); Chat Functionality; Intelligent Features Service Provider (Optional)USA, EU

Listed as a subprocessor by (1)

Purposes as each company states them.

Service status

BeganIncidentImpactLasted
Workvivo Application - outage affecting users in EU2 Regionnone1 min
Service Disruption - Workvivo UAE (.me) AWS Region Onlyminorongoing
Service Disruption - Workvivo UAE (.me) AWS Region Onlyminor11 h 20 min
Workvivo Application - activity feed issue affecting usersminor16 min
Workvivo Application - intermittent outage affecting usersminor2 h 7 min
Workvivo Application - outage affecting users in EU Regioncritical—

As Workvivo's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Changes

None since tracking began.