Pharos

pharos.com

Pharos declares 8 subprocessors in its subprocessor list, which we last checked on Oct 25, 2026 (evidence). They include Amazon Web Services, Salesforce and Slack. No published changes since we first read it on Oct 12, 2026.

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

8 third parties.

NamePurposeLocationListed since
1Password Password management
Amazon Web Services
Infrastructure for cloud offerings, additional regions available include: Europe, Canada, South America, Asia, Australia, and Africa. See our Pharos Cloud Data Privacy Whitepaper for complete details.; Infrastructure-as-a-Service provider
US
Entra (Office 365) Collaboration, XDR, MDM, Identity ManagementUS
GitLab Hosted in AWS private cloud; Version controlUS
Rippling Employee management
Salesforce CRM, SupportUS
Slack Collaboration
Vanta Continuous security and compliance monitoringSecurity Compliance

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

Pharos's homepage made 49 requests to 9 domains, 4 services controlled by another company, and 1 domain not identified.

CDN (2): jsDelivr, Google CloudCookie compliance (1): CookieYesOther (1): Widgets: Navattic

4 third parties by category: CDN 2Cookie compliance 1Other 1

Third parties 4 · 26 requests
CookieYes CookieYes 20% of the page's requests 10
jsDelivr Bootstrap 5.2.2 Popper 2.11.6 Slick jsDelivr 16% of the page's requests 8
Google Cloud Google Hosted Libraries jQuery 1.11.0 10% of the page's requests 5
Navattic Navattic 6% of the page's requests 3
Unknown 1 · 7 requests

hb.wpmucdn.com

First party 1 · 16 requests
Pharos Alpine.js 3.17.4 Draftpress HFCM FancyBox 6.0.34 Google Font API Google Tag Manager HSTS LazySizes Linkedin Ads Linkedin Insight Tag Max Mega Menu MySQL Nginx Open Graph PHP Priority Hints RSS SiteGround Swiper WordPress WordPress Block Editor Yoast SEO 28.7 33% of the page's requests 16

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

ComplianceCSV of Pharos's compliance · Atom feed of Pharos's compliance

Certified

Certifications as Pharos's trust center lists them; reports are usually shared on request (evidence)

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

Jul 29: before our history of this status pageJul 30: before our history of this status pageJul 31: before our history of this status pageAug 1: before our history of this status pageAug 2: before our history of this status pageAug 3: before our history of this status pageAug 4: before our history of this status pageAug 5: before our history of this status pageAug 6: before our history of this status pageAug 7: before our history of this status pageAug 8: before our history of this status pageAug 9: before our history of this status pageAug 10: before our history of this status pageAug 11: before our history of this status pageAug 12: before our history of this status pageAug 13: before our history of this status pageAug 14: before our history of this status pageAug 15: before our history of this status pageAug 16: before our history of this status pageAug 17: before our history of this status pageAug 18: before our history of this status pageAug 19: before our history of this status pageAug 20: before our history of this status pageAug 21: before our history of this status pageAug 22: before our history of this status pageAug 23: before our history of this status pageAug 24: before our history of this status pageAug 25: before our history of this status pageAug 26: before our history of this status pageAug 27: before our history of this status pageAug 28: before our history of this status pageAug 29: before our history of this status pageAug 30: before our history of this status pageAug 31: before our history of this status pageSep 1: before our history of this status pageSep 2: before our history of this status pageSep 3: before our history of this status pageSep 4: before our history of this status pageSep 5: before our history of this status pageSep 6: before our history of this status pageSep 7: before our history of this status pageSep 8: before our history of this status pageSep 9: before our history of this status pageSep 10: before our history of this status pageSep 11: before our history of this status pageSep 12: before our history of this status pageSep 13: before our history of this status pageSep 14: before our history of this status pageSep 15: before our history of this status pageSep 16: before our history of this status pageSep 17: before our history of this status pageSep 18: before our history of this status pageSep 19: before our history of this status pageSep 20: before our history of this status pageSep 21: before our history of this status pageSep 22: before our history of this status pageSep 23: before our history of this status pageSep 24: before our history of this status pageSep 25: before our history of this status pageSep 26: before our history of this status pageSep 27: before our history of this status pageSep 28: before our history of this status pageSep 29: before our history of this status pageSep 30: before our history of this status pageOct 1: before our history of this status pageOct 2: before our history of this status pageOct 3: before our history of this status pageOct 4: before our history of this status pageOct 5: before our history of this status pageOct 6: before our history of this status pageOct 7: before our history of this status pageOct 8: before our history of this status pageOct 9: before our history of this status pageOct 10: before our history of this status pageOct 11: before our history of this status pageOct 12: before our history of this status pageOct 13: before our history of this status pageOct 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: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: no incident reportedOct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reported

90 days agotoday

No incidents reported since Oct 14, 2026

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

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

7 reported incidents in the last 30 days, by 3 of the vendors Pharos lists as subprocessors.

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

DateCompanyIncidentImpactLasted
VantaStale data for CloudflareDomainInventory and CloudflareZoneRule major7 h 42 min
1PasswordHigh error rate on 1Password.com major3 days
1PasswordSome users are unable to view vault profiles using the web interface minor10 min
RipplingProducts partially degraded major1 h 47 min
RipplingIssues using 1Password passkeys minor25 h 51 min
RipplingRPass Chrome extension login failures no impact stated—
RipplingRippling app is down critical8 h 35 min

Who is around them.

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

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

None since tracking began.

Rating badge for Pharos's site

Pharos transparency rating

It updates with the rating.

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