> For the complete documentation index, see [llms.txt](https://pulselabs.gitbook.io/pulse-labs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pulselabs.gitbook.io/pulse-labs/privacy-center/readme/subprocessors.md). # Subprocessors Pulse Labs engages the third-party subprocessors listed below to process personal data in connection with providing our services. Each subprocessor is bound by contractual obligations consistent with the requirements of applicable data-protection law and our customer Data Processing Agreements. Additions and removals are posted to [Subprocessor updates](/pulse-labs/privacy-center/readme/subprocessors/subprocessor-updates.md), where you can subscribe to be notified of changes. *** ## Infrastructure, hosting & data stores | Subprocessor | Purpose of processing | Categories of data | Location(s) | | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------------------------- | | Amazon Web Services (AWS) | Cloud hosting, storage (S3), queues (SQS/SNS), CDN (CloudFront), compute (ECS/Lambda/Elastic Beanstalk), databases (RDS/DynamoDB) | All participant & customer data, at rest and in transit | United States (us-east-1) | | MongoDB Atlas | Primary application document database | Participant profiles, responses, study data | United States | | Redis (managed) | Caching, queues, session/state | Session & transient operational data | United States | | Firebase (Google) | Mobile backend / messaging / config | Device tokens, app state, limited PII | United States | ## Monitoring & observability | Subprocessor | Purpose of processing | Categories of data | Location(s) | | --------------------- | -------------------------------------------- | ------------------------------------------------------- | ------------- | | New Relic | Application performance monitoring & logging | Telemetry; logs may contain limited PII | United States | | Sentry | Error & crash monitoring | Stack traces; may contain limited PII | United States | | LangSmith (LangChain) | LLM tracing/observability for AI features | LLM prompts & outputs (may contain participant content) | United States | ## Identity, verification & fraud prevention | Subprocessor | Purpose of processing | Categories of data | Location(s) | | ------------ | ------------------------------------------------- | ---------------------------------------- | -------------- | | Auth0 (Okta) | Authentication / identity for app & API | Email, auth credentials, profile | United States | | Fingerprint | Device intelligence / fingerprinting (anti-fraud) | Device & browser identifiers, IP address | United States | | vpnapi.io | IP / VPN & proxy intelligence (anti-fraud) | IP address | United States | | ProxyCheck | IP / proxy & VPN intelligence (anti-fraud) | IP address | United Kingdom | | Fraudio | Payment fraud detection | Payment & transaction metadata | Netherlands | | Persona | Identity / ID verification (KYC) | Government ID, selfie/biometric, phone | United States | | Twilio | SMS verification & messaging | Phone number | United States | ## Participant payments & payouts | Subprocessor | Purpose of processing | Categories of data | Location(s) | | ------------ | --------------------------------------------------- | --------------------------- | -------------- | | Stripe | Payment processing & payouts (incl. Stripe Connect) | Card & payout data | United States | | Tremendous | Participant rewards / gift-card payouts | Name, email, payout details | United States | | Wise | International participant transfers | Name, bank/payee details | United Kingdom | ## Communications & notifications | Subprocessor | Purpose of processing | Categories of data | Location(s) | | ----------------- | --------------------------------------------- | ------------------------------------- | ------------------------- | | SendGrid (Twilio) | Transactional email | Email address, message content | United States | | CometChat | In-app messaging / participant chat & support | Message content, user identifiers | United States | | Amazon SES (AWS) | Transactional email | Email address, message content | United States (us-east-1) | | Pushwoosh | Push notifications & SMS gateway | Device tokens, phone number | United States | | Pusher | Realtime messaging/presence | Connection metadata, message payloads | United Kingdom | ## Documents & consent | Subprocessor | Purpose of processing | Categories of data | Location(s) | | ------------ | ------------------------------------------ | ---------------------- | ------------- | | BoldSign | E-signature for consent forms & agreements | Name, email, signature | United States | ## Analytics, AI & data processing | Subprocessor | Purpose of processing | Categories of data | Location(s) | | --------------------------------- | -------------------------------------- | -------------------------------- | ------------- | | PostHog | Product analytics & session recording | Behavioral data, session replays | United States | | Google Cloud — Gemini / Vertex AI | LLM analysis of sessions & transcripts | Participant content, transcripts | United States | | OpenAI | LLM processing | Participant content, transcripts | United States | | Anthropic | LLM processing | Participant content, transcripts | United States | | Google Maps Platform | Geocoding / location features | Location data | United States | | HubSpot | CRM & marketing | Leads, contacts, email | United States | ## Video & media | Subprocessor | Purpose of processing | Categories of data | Location(s) | | ------------ | -------------------------------------- | ------------------------------------- | ------------- | | 100ms | Live video/audio sessions (interviews) | Audio/video streams, session metadata | United States | | LiveKit | Real-time audio/video infrastructure | Audio/video streams | United States | ## Integrations & data export | Subprocessor | Purpose of processing | Categories of data | Location(s) | | --------------------------------- | ----------------------------------------- | ----------------------------------------- | ------------- | | Prismatic | Embedded integration platform (iPaaS) | Data routed through customer integrations | United States | | Google Workspace (Sheets / Drive) | Customer-selected data export destination | Exported study & participant data | United States | *** *Last updated: 2026-06-23. This list is version-controlled; the effective date of each change is recorded in page history.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://pulselabs.gitbook.io/pulse-labs/privacy-center/readme/subprocessors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.