Our platform employs a least-privilege model for data access. This means that all data is only accessible to the service responsible for storing, processing, or querying it. For example, the OCR service, which performs document OCR, has a dedicated storage that no other services can access. Likewise, the OCR work service cannot access data from storage allocated to other services. All requests must go through the APIs of the involved services. We use JSON Web Tokens (JWTs) to securely handle authorization outside the application, ensuring that our identity systems and the tenant service are the sources of truth. Tokens can only be used for their authorized purposes. When you or someone from your team calls a microservice or shard, the tokens are forwarded to your identity system and validated against this system. This process ensures that the token is current and signed before the corresponding data is released. Combined with the authorization and authentication required to access these microservices, the impact of a compromised service is limited. Furthermore, we proactively identify potential vulnerabilities in our product to minimize their impact on you. We conduct a series of security programs to identify, detect, and respond to security threats.