19
Vendors named
| Asana | user data is sometimes discussed and referenced in tasks and comments in Asana |
| Atlassian | user data is sometimes discussed and referenced in tasks and comments in Jira |
| AWS | the bulk of customer-provided user data is hosted in AWS |
| ClickHouse | customer-provided user data is stored in ClickHouse cloud to drive some Vitally application functionality, including reporting and analytics |
| Fullstory | user data is stored in Fullstory for support and issue tracking purposes |
| Gong | Contains call recordings between Vitally employees and our users and sales prospects which may contain user data. |
| Hex | We use Hex to pull data from multiple sources including the product and other data sources like Jira. It may process and temporarily store user data of current customers. |
| Honeycomb | user data is tracked in Honeycomb for infrastructure monitoring |
| HubSpot | basic user data (e.g. name, email, shared conversations) is stored in Hubspot |
| Intercom | user data is maintained in Intercom for live chat and support |
| Pendo | product instrumentation including user data is used for product analytics. |
| Recall | Vitally is integrating with a vendor providing Meeting Recorders to record and transcribe meetings that may take place over tools like Zoom and Google Meet. |
| Retool | Connects to production systems as a user interface for internal tooling that may process user data. |
| Salesforce (+Heroku, Slack) | user data is sometimes discussed in chat in Slack |
| Sentry | user data is stored in Sentry for exception/error tracking |
| Stripe | payment data, including user emails and company names, is maintained in Stripe. |
| Twilio (+Segment, SendGrid) | user data is tracked in Segment for forwarding to other subprocessors, like Intercom |
| Usergems | basic user data (name, email) are stored in Usergems |
| Zapier | some user data is sent to Zapier for forwarding to some of our other subprocessors, like Slack. |