Third Party Index

Vistaly

vistaly.com

Subprocessors

5 third parties. CSV · Atom

NamePurposeLocationListed since
Amazon Web Services, Inc. AIWe use AWS to host our entire application infrastructure, including servers, databases, and backups. AWS also provides AI inference via Amazon Bedrock, running Claude models within AWS's infrastructure. AWS enables us to provide secure, scalable, and reliable services, including data storage, processing, AI inference, and disaster recovery solutions to ensure high availability and durability for our application.Data Processing Region: Your selected region (US or EU); Location: 410 Terry Ave N, Seattle, WA, 98109-5210 United States
AssemblyAI, Inc. AIWe use AssemblyAI for speech-to-text transcription in our beta Vistaly product. AssemblyAI is not used by app.vistaly.com (Vistaly V1).Data Processing Region: Your selected region (US or EU); Location: 2261 Market Street #4577, San Francisco, CA 94114 United States
Google LLC We use Google to facilitate secure login through Google's OAuth service. This allows users to log in to our platform using their Google accounts, ensuring a seamless and secure authentication process.Data Processing Region: United States; Location: 1600 Amphitheatre Parkway, Mountain View, CA, 94043-1351 United States
Microsoft Corporation We use Microsoft to facilitate secure login through Microsoft's OAuth service. This allows users to log in to our platform using their Microsoft work, school, or personal accounts, ensuring a seamless and secure authentication process.Data Processing Region: United States; Location: One Microsoft Way, Redmond, WA 98052 United States
Product Talk LLC Product Talk provides licensed services integrated into the Vistaly platform, including the Interview Snapshot Generator and OST Update features. These services run within Vistaly's infrastructure; Product Talk personnel access is limited to execution traces and logs of these services for quality assurance and debugging. All data remains within Vistaly's infrastructure — Product Talk does not store or export customer data.Data Processing Region: Your selected region (US or EU); Location: Bend, OR 97703, United States

Service status

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

90 days agotoday

No incidents reported since Oct 1, 2026

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

Changes

None since tracking began.

Rating badge for Vistaly's site

Vistaly transparency rating

It updates with the rating.

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