Sub-Processors
Last updated: August 19, 2026
Sendqube uses the sub-processors below to provide the product and service. Each one is contractually bound to protect data and process it only on our instructions. We keep this list current as we add or remove sub-processors — see the Data Processing Addendum for the terms these arrangements operate under.
Infrastructure
Primary database, authentication, and file storage.
Data: All workspace data — contacts, sequences, mailbox credentials (encrypted), accounts, meeting recordings and transcripts.
Hosts and runs the application itself.
Data: Request traffic in transit — request bodies, IP addresses, session cookies.
Runs Sendqube's own backend service for raw email sending/receiving, mailbox warmup, and web scraping — first-party infrastructure Sendqube operates, hosted on AWS.
Data: Full email content (outbound and inbound), mailbox credentials passed per request, scraped page content.
Sends Sendqube's own transactional email (sign-in codes, team invites).
Data: Recipient email address, one-time codes, invite links.
AI providers
Sendqube generates AI drafts, research summaries, and chat responses through a fallback chain — if the primary provider is unavailable, the next one in the chain is used instead. All providers in the chain can receive the data listed below; which one actually serves a given request depends on availability at that moment.
Primary AI provider for campaign copy, research, and the Senq AI chat agent.
Data: Contact and company data used for personalization, email drafts, chat messages.
AI inference fallback, and speech-to-text transcription for meeting recordings.
Data: Same as above for inference; meeting audio for transcription.
AI inference fallback.
Data: Same as above.
AI inference fallback.
Data: Same as above.
AI inference fallback.
Data: Same as above.
Last-resort AI inference fallback.
Data: Same as above.
Data enrichment & search
Contact and company enrichment, and Lead Finder search — connected per workspace.
Data: Contact names, emails, and company names sent; job title, industry, and LinkedIn URL returned.
Finds a person's work email at a known company domain — connected per workspace.
Data: Name and company domain sent; email address and confidence score returned.
Paid email-verification fallback used when free-tier checks return an inconclusive result.
Data: Contact email addresses.
Web search used by Senq AI for account research.
Data: Search queries containing prospect or company names.
Web scraping, used only for LinkedIn profile and company pages.
Data: LinkedIn URLs and the page content returned.
Outreach channels
LinkedIn and SMS outreach are available on select workspaces only.
Sends SMS messages for workspaces with SMS outreach enabled.
Data: Recipient phone numbers and message content.
Connect requests and messages for workspaces with LinkedIn outreach enabled, sent via automated browser session using the workspace's own connected LinkedIn account — LinkedIn has no official sending API.
Data: The connected LinkedIn account's session, prospect profile URLs, and message content.
Meeting recording & transcription
Available on select workspaces that enable meeting bots on a meeting type.
The meeting bot joins the workspace's scheduled Google Meet call and records audio, for workspaces with meeting recording enabled.
Data: Meeting audio and any participant names/content visible during the call.
Mailbox & identity providers
Gmail mailbox connection, Google Calendar, and sign-in.
Data: OAuth tokens (encrypted at rest), email content sent and received, calendar events.
Microsoft 365/Outlook mailbox connection, Microsoft Calendar, and sign-in.
Data: OAuth tokens (encrypted at rest), email content sent and received, calendar events.
Bot protection on sign-up and sign-in.
Data: IP address and browser/device signals.
Analytics
Used only when a workspace configures it — never on by default.
Session recording on the workspace's own unsubscribe page, when the workspace connects its own Clarity project.
Data: Page interactions, session recordings, and the visitor's IP address and user agent.
Website visitor identification
Reverse-looks-up a website visitor's IP address to identify the visiting company, for workspaces using the Visitors feature.
Data: Visitor IP addresses.
Customer-connected integrations
Active only for workspaces that choose to connect them.
Two-way contact and activity sync, for workspaces that connect it.
Data: Contact names, emails, phone numbers, company, and activity.
Two-way contact and activity sync, for workspaces that connect it.
Data: Contact names, emails, phone numbers, company, and activity.
Two-way contact and activity sync, for workspaces that connect it.
Data: Contact names, emails, phone numbers, company, and activity.
Two-way contact and activity sync, for workspaces that connect it.
Data: Contact names, emails, phone numbers, company, and activity.
Questions about a specific sub-processor? Email dev@sendqube.in.
