# Security and Privacy Cloudshim understands that the security of the customer's data is nothing less than critical. To deliver peace of mind, we believe in transparency regarding Cloudshim's security standards and practices. ### Application Security Cloudshim's application is hosted and managed within the AWS data center. The data center has been accredited under ISO 27001, SOC 1 and SOC 2m PCI Level 1, FISMA Moderate, and Sarbanes-Oxley (SOX). The data center is located in the United States. ### IAM & Authentication Cloudshim follows [AWS security best practices](https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#delegate-using-roles) for the creation of IAM role delegation. No credentials are stored on our systems. Cloudshim uses AWS Cognito for user sign up, sign in, and authentication which is PCI DSS, SOC, and ISO 27001 compliant. ### Data Communication between you and Cloudshim servers is encrypted via industry best practices (HTTPS). All data is safely stored in data stores which are encrypted using industry-standard AES-256 and KMS keys with FIPS 140-2 level encryption. Data in transit always uses SSL/TLS 1.2 encrypted channels for connection security. ### **API Security** Cloudshim API is SSL-only and you must be a verified user to make API requests. Authorization against the API can only be made using an API token. ### Credit Card/ Bank Account Cloudshim uses Stripe payment infrastructure to process credit card payments. To read more on Stripe security [click here](https://stripe.com/docs/security/stripe). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.cloudshim.com/resources/security-and-privacy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.