Below is the list of Subprocessors and the way we use their services.
Infrastructure
We use these subprocessors for hosting and running our services. These third parties store and process user data within our service.
Subprocessor | Purpose of Processing | Location | DPA |
---|---|---|---|
GCP | Hosting and storage systems provider | Frankfurt | https://cloud.google.com/terms/partners-data-processing-addendum |
Google Workspace | Company workspace, calendar, Gmail, main OAuth provider. | USA | https://workspace.google.com/terms/09242021/dpa_terms/ |
Platform
Subprocessor | Purpose of Processing | Location | DPA | Transfer Mechanism | Monitoring |
---|---|---|---|---|---|
Grafana | Infrastructure & Application Monitoring | USA | https://grafana.com/legal/data-processing-agreement/ | SCC | https://status.grafana.com. Integration with ‣ |
LaunchDarkly | Feature toggle management | USA | https://launchdarkly.com/policies/data-processing-addendum/ | EU-U.S. Data Privacy Framework Principles | https://status.launchdarkly.com/. Integration with ‣ |
Mailgun | Applicative email manager | USA | https://www.mailgun.com/legal/dpa/ | SCC | https://status.mailgun.com/. Integration n/a |
OpenAI | Provider for AI functionality | USA | https://openai.com/policies/data-processing-addendum/ | SCC | https://status.openai.com/. Subscribed to API statuses by way of Slack e-mail integration in ‣ |
Recall | Recording & Transcription services | USA | Signed | Don’t offer a status page, but was told that they keep us informed of status updates in ‣ | |
Sentry | Error tracking | USA | https://sentry.io/legal/dpa/ | EU-U.S. Data Privacy Framework Principles | Not necessary |
Github | Application source control and deployment | USA | github-data-protection-agreement | EU-U.S. Data Privacy Framework Principles | https://www.githubstatus.com. Integration with ‣ |
DISABLED due to being spammy and not providing enough granularity | |||||
Pinecone | Vector DB for semantic search | USA | https://www.pinecone.io/dpa/ | SCC | https://status.pinecone.io. Integration with ‣ |
Rollout | Integrations Management | USA | Signed | https://status.rollout.com/. Integration n/a | |
Deepgram | Transcription voice calls | USA | Signed | SCC | https://status.deepgram.com/. Integration with ‣ |
Gladia | Transcription voice calls | France | signed | https://status.gladia.io/. Integration with ‣ | |
Twilio | recording phone calls | USA | https://www.twilio.com/en-us/legal/data-protection-addendum | EU-U.S. Data Privacy Framework Principles | https://status.twilio.com/. Integration with ‣ DISABLED due to being spammy |
Azure OpenAI | Generating insights from meeting transcriptions | Data stored at rest remains in the designated Azure geography, while data may be processed for inferencing in any Azure OpenAI location. |
*** For the Enterprise plan, you can choose to deploy in a different region.** | https://learn.microsoft.com/en-us/legal/cognitive-services/openai/data-privacy
Please read about deployment type “Global-Standard”: https://learn.microsoft.com/en-us/azure/ai-services/openai/how-to/deployment-types | SCC | | | RevAI | Transcription voice calls | USA | https://www.rev.com/legal/data-processing-addendum | SCC | Not necessary | | ZenLeads Inc. | Enrichment on contacts | USA | https://www.apollo.io/dpa | DPF | https://status.apollo.io. E-mail forwarding to Slack integration with ‣ |
We use these subprocessors to assist us in managing and delivering our Service.