Yapily

yapily.com

Yapily declares 10 subprocessors, plus 1 of its own affiliates, in its subprocessor list, which we last checked on Nov 20, 2026 (evidence). They include Salesforce, posthog and Gong. No published changes since we first read it on Sep 30, 2026. 1 tracked vendor, Light, names Yapily as a subprocessor.

Subprocessors CSV of Yapily's subprocessors · Atom feed of Yapily's subprocessors DORA draft CSV of Yapily's subprocessors as declared by Yapily what's this? · 

10 third parties, 1 affiliate.

NamePurposeLocationListed since
ComplyAdvantage (IVXS UK Limited) Transaction monitoring software provider for payment transactions (PIS) provided to Yapily Connect customers.EEA
Gong.io A Customer Relationship Management (CRM) Platform for Sales, Marketing and Customer SuccessEU, US and Israel
Google Cloud Platform, Google LLC Cloud storage of Yapily platform, data and servicesLondon, UK, with back-up in Belgium, EEA
Invers Transaction data enrichment servicesNetherlands, EEA
Ntropy Network Inc. API package and Transaction data enrichment servicesDelaware, USA
Ondato Identity verification and KYB complianceNetherlands, Ireland
Plain (Not Just Tickets Limited) B2B Customer Support Platform,EEA
PostHog, Inc Product-analytics and session-replay platform.EEA
Salesforce UK Limited Internal customer management solutionLondon, UK
Vitally, Inc A Customer Success Platform, providing personalised interactions through increased productivity, visibility, and collaborationGlobal
Yapily affiliates (1)
NamePurposeLocationListed since
Yapily Limited Where contracting for Yapily Connect Services, Yapily Limited acts as sub-processor to the Yapily Connect Entities to provide the Technology ServicesUK

Web TechnologiesCSV of Yapily's web technologies · Atom feed of Yapily's web technologies

Yapily's homepage made 183 requests to 21 domains, and 9 services controlled by another company.

Advertising (3): Google Cloud, Microsoft, OpenAIAnalytics (2): Meta, LinkedInLive chat (1): usually detected as Live chat: SalesforceCookie compliance (1): iubendaOther (2): reviewed as CMS: Storyblok; reviewed as Video players: Vimeo

9 third parties by category: Advertising 3Analytics 2Live chat 1Cookie compliance 1Other 2

Third parties 9 · 128 requests
Storyblok storyblok.com 39% of the page's requests 71
Google Cloud DoubleClick Floodlight Google Analytics Google Tag Manager 8% of the page's requests 15
Vimeo vimeocdn.com, vimeo.com 8% of the page's requests 15
Microsoft Microsoft Advertising 6% of the page's requests 11
Meta Facebook Pixel 2.9.419 3% of the page's requests 5
LinkedIn Linkedin Insight Tag 2% of the page's requests 3
OpenAI ChatGPT Ads Measurement Pixel 2% of the page's requests 3
iubenda iubenda 2% of the page's requests 3
Salesforcesubprocessor pardot.com 1% of the page's requests 2
First party 1 · 55 requests
Yapily Astro 7.3.2 Google Font API HTTP/3 Microsoft Clarity Open Graph Salesforce Salesforce Marketing Cloud Account Engagement Storyblok Vimeo core-js 3.32.2 30% of the page's requests 55

7 tracked companies loaded by the homepage are not in Yapily's subprocessor list. A website can use a service without it processing customer data.

Subprocessor of (1)CSV of the companies listing Yapily · Atom feed of the companies listing Yapily

1 company
  • Light light.inc Open banking bank feeds. Obtains the end user's consent directly and processes account and transaction data under its own licence.

Service statusCSV of Yapily's status page incidents · Atom feed of Yapily's status page incidents

Aug 24: no incident reportedAug 25: no incident reportedAug 26: no incident reportedAug 27: no incident reportedAug 28: no incident reportedAug 29: no incident reportedAug 30: no incident reportedAug 31: no incident reportedSep 1: no incident reportedSep 2: no incident reportedSep 3: no incident reportedSep 4: no incident reportedSep 5: no incident reportedSep 6: no incident reportedSep 7: no incident reportedSep 8: no incident reportedSep 9: no incident reportedSep 10: no incident reportedSep 11: no incident reportedSep 12: no incident reportedSep 13: no incident reportedSep 14: no incident reportedSep 15: no incident reportedSep 16: no incident reportedSep 17: no incident reportedSep 18: no incident reportedSep 19: no incident reportedSep 20: no incident reportedSep 21: no incident reportedSep 22: no incident reportedSep 23: no incident reportedSep 24: no incident reportedSep 25: no incident reportedSep 26: no incident reportedSep 27: no incident reportedSep 28: no incident reportedSep 29: no incident reportedSep 30: no incident reportedOct 1: no incident reportedOct 2: 1 incident (1 no impact stated)Oct 3: no incident reportedOct 4: no incident reportedOct 5: no incident reportedOct 6: no incident reportedOct 7: 1 incident (1 no impact stated)Oct 8: 1 incident (1 minor)Oct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: no incident reportedOct 15: no incident reportedOct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: 1 incident (1 critical)Oct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reportedOct 27: no incident reportedOct 28: no incident reportedOct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: 2 incidents (2 minor)Nov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reportedNov 13: no incident reportedNov 14: no incident reportedNov 15: no incident reportedNov 16: no incident reportedNov 17: no incident reportedNov 18: no incident reportedNov 19: no incident reportedNov 20: no incident reportedNov 21: no incident reported

90 days agotoday

  • 6 incidents in 90 days
  • 1 major or critical
  • 3 h 18 min typical time to resolve
  • 5 h 57 min longest major
BeganIncidentImpactLasted
VoP Service Disruptionminor1 h 46 min
GET Transactions - TotalCount - Service Disruptionminor3 h 18 min
API Service Disruptioncritical5 h 57 min
Console - Unable to create applicationminor25 h 4 min
GET Users - Service Disruptionno impact stated1 h 45 min
Console - Applications tab Service Disruptionno impact stated1 h 37 min
PIS Service Disruptionmajor1 h 38 min
API Service Disruptionmajor—

Incidents per month

0 3 6 Dec 2025: 1 incident (1 no impact stated) · typical time to resolve 50 min Jan 2026: 1 incident (1 major) · typical time to resolve 3 h 43 min Feb 2026: 1 incident (1 minor) · typical time to resolve 2 days Mar 2026: 5 incidents (1 critical, 2 major, 2 minor) · typical time to resolve 5 days Apr 2026: 1 incident (1 minor) · typical time to resolve 21 days May 2026: 1 incident (1 minor) · typical time to resolve 23 h 24 min Jun 2026: 4 incidents (2 major, 2 minor) · typical time to resolve 21 h 1 min Jul 2026: 1 incident (1 major) Aug 2026: 1 incident (1 major) · typical time to resolve 1 h 38 min Sep 2026: 0 incidents Oct 2026: 4 incidents (1 critical, 1 minor, 2 no impact stated) · typical time to resolve 5 h 57 min Nov 2026: 2 incidents (2 minor) · typical time to resolve 3 h 18 min Dec 2025Jan 2026Feb Mar Apr May Jun Jul Aug Sep Oct Nov

critical major minor no impact stated

As Yapily's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Incidents reported by Yapily's subprocessorsCSV of incidents reported by vendors Yapily lists · Atom feed of incidents reported by vendors Yapily lists

10 reported incidents in the last 30 days, by 2 of the vendors Yapily lists as subprocessors.

A subprocessor list names a company, not the service an incident touched. This does not show that Yapily was involved.

DateCompanyIncidentImpactLasted
GongMeeting Recording Degradation (Google Meet) major17 h 47 min
GongMicrosoft Teams calls & outlook is currently affected by a service disruption at Microsoft minor2 h 16 min
PlainHelp Center errors no impact stated—
PlainIntermittent API errors on write actions minor2 h 54 min
PlainDelays in incoming emails minor1 h 55 min
PlainSome Sidekick requests failing minor10 min
PlainDelays receiving Slack messages in Plain minor11 min
PlainReporting data delayed minor47 min
PlainElevated errors across the Plain app, API and help centers major19 min
PlainDegraded AI features minor1 h 33 min

Who is around them.

ChangesCSV of Yapily's changes · Atom feed of Yapily's changes

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for Yapily's site

Yapily transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/yapily"><img src="https://thirdpartyindex.com/badge/yapily.svg" alt="Yapily transparency rating on Third Party Index" height="20"></a>
[![Yapily transparency rating on Third Party Index](https://thirdpartyindex.com/badge/yapily.svg)](https://thirdpartyindex.com/vendors/yapily)