Yesware
Yesware declares 11 subprocessors in its subprocessor list, which we last checked on Nov 12, 2026 (evidence). They include Amazon Web Services, Google Cloud and Salesforce. No published changes since we first read it on Nov 6, 2026. 2 tracked vendors name Yesware as a subprocessor, including Akita and Flywire.
Not loaded by any published homepage.
Subprocessors CSV of Yesware's subprocessors · Atom feed of Yesware's subprocessors DORA draft CSV of Yesware's subprocessors as declared by Yesware what's this? ·
11 third parties.
| Name | Purpose | Location | Listed since |
|---|---|---|---|
| 84CODES | Cloud Message Queuing Provider; Message queues carrying email events, inbound email handoff, CRM contact/task sync, calendar sync, user/plan/team changes | USA | |
| Amazon Web Services | Application database, file storage and archives: user account records, email attachments, call archives, billing membership records, logs; Cloud provider | USA | |
| Cloudmailin | MX for the inbound sync; Whole inbound messages relayed to Yesware: sender/recipient emails, subject, body, attachments; calendar invites (attendee names/emails, event details) | USA | |
| Fastly | Cloud provider; Website visitor IP addresses and request metadata for the marketing site only; no product or tracking traffic | USA | |
| Google Cloud Platform | Cloud provider; Primary application databases and compute: user accounts, email and calendar sync data, CRM sync data, tracking/event data, backups | USA | |
| Heroku | Event stream (Kafka): email message metadata, prospect/email tracking events (recipient email, open/click), user events; 2-day retention; Managed Cloud Messaging Platform | USA | |
| MongoDB, Inc. | Data storage and processing; Email message records and summaries, scheduled emails, email open/click tracking events (recipient email, time, IP), CRM contact/object cache, calendar event maps, user activity | USA | |
| New Relic | Data analytics; User name, email, domain and id on every authenticated transaction; captured request parameters (can include prospect/recipient emails); error payloads | USA | |
| Redis | Managed Cloud Database Provider; Web session store, application caches and background-job queues: user/session identifiers, queued jobs that may carry email or calendar metadata | USA | |
| Segment.io | Marketing; user email, full name, domain, account/trial/subscription dates, product-usage events; browser page views (IP and user agent inferred) | USA | |
| TWILIO | Cloud provider; transactional email: recipient email, user and team names, activity reports, billing/invoice notices. Not customers' tracked emails | USA |
Web TechnologiesCSV of Yesware's web technologies · Atom feed of Yesware's web technologies
Yesware's homepage made 273 requests to 42 domains, 26 services controlled by another company, and 2 domains not identified.
26 third parties by category: Analytics 7Advertising 6Marketing automation 3Cookie compliance 1Other 9
sitedataprocessing.comcdnstyles.com
16 tracked companies loaded by the homepage are not in Yesware's subprocessor list. A website can use a service without it processing customer data.
Subprocessor of (2)CSV of the companies listing Yesware · Atom feed of the companies listing Yesware
Service statusCSV of Yesware's status page incidents · Atom feed of Yesware's status page incidents
90 days agotoday
- 0 incidents in 90 days
- 0 major or critical
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Authentication Issues with Yesware's Salesforce Integration | major | 51 days | |
| Custom Availability for Meeting Scheduler Not Loading | no impact stated | 12 h 46 min | |
| Mac Users Experiencing Issues with Desktop Outlook Add-in | no impact stated | 3 days |
Incidents per month
critical major minor no impact stated
As Yesware's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Incidents reported by Yesware's subprocessorsCSV of incidents reported by vendors Yesware lists · Atom feed of incidents reported by vendors Yesware lists
199 reported incidents in the last 30 days, by 4 of the vendors Yesware lists as subprocessors.
A subprocessor list names a company, not the service an incident touched. This does not show that Yesware was involved.
And 174 more. All of them: CSV · Who is around them.
ChangesCSV of Yesware's changes · Atom feed of Yesware's changes
See the list as we read it on any date: Time machine
None since tracking began.