All our employees and contractors (workers) sign confidentiality agreements before gaining access to our codebase and data. Every employee is trained and made aware of security concerns and best practices for their systems, during onboarding as well as on a periodic basis. We log all access to all accounts by IP address. Access is granted to production servers only as required and is provisioned on an as-needed basis. Access to servers is limited by role based access through IAM that enforces segregation of duties and 2 factor authentication.
Factors.AI servers that persistently store customer data are hosted by Google Cloud Platform (GCP). GCP’s data center is SOC 1, SOC 2 and SOC 3 compliant. GCP also logically isolates each customer’s Cloud Platform data from that of other customers and users. All data is stored and processed in GCP’s ‘us-west-1b’ zone located in the United States.
All GCP data center facilities include
Strict Access Security
Monitoring
Personnel
Power Availability
For further information on GCP Security and Compliance refer the following links
Customer data is secured in transit using TLS and encrypted at rest within the application. Factors also logically separates data across accounts and access to your data is protected by strong authentication and authorization controls.
Your data is encrypted using the 256-bit Advanced Encryption Standard (AES-256), or better, with symmetric keys: that is, the same key is used to encrypt the data when it is stored, and to decrypt it when it is used. These data keys are themselves encrypted using a key stored in a secure keystore, and changed regularly. Further details may be found below
https://cloud.google.com/sql/faq#encryption-manage-rest
https://cloud.google.com/security/encryption-at-rest/default-encryption
When a user visits a website or application which has instrumented the FactorsAI SDK, details of their interactions are captured and sent to FactorsAI through API calls secured over HTTPS/HTTP, based on configurations set by the customer. All of our other APIs and websites use HTTPS exclusively. All data transferred over HTTPS is encrypted. FactorsAI uses SHA-2 compliant cipher suites to secure data in transit. Further, the data is encrypted and authenticated in transit at one or more network layers when data moves outside physical boundaries not controlled by Google or on behalf of Google. All our servers are hosted within a Virtual Private Cloud with fine grained security control. Within our datacenter VPC’s, data may be transferred unencrypted. Further details may be found below
https://cloud.google.com/security/encryption-in-transit
https://cloud.google.com/vpc-service-controls
All customer data is tagged with a project-specific token, and a customer must have access to the corresponding API key and secret in order to retrieve that data via API (access to the web UI is controlled via username and password). This provides logical separation between data belonging to multiple clients. FactorsAI is the sole tenant on our infrastructure. A customer’s data may reside on database systems which house data belonging to other customers, but our logical controls (token, key and secret) separates one client from another client’s data.
We maintain a robust application security program, covering the following
Factors Incident Management policy requires that any and all suspected or confirmed Data Security incidents must be immediately reported to the Data Protection Officer. An ‘incident’ is defined as any event that compromises the integrity, confidentiality or availability of an information asset. The DPO will engage with the Incident Response Team and coordinate with the management and the legal counsel to take appropriate actions to meet our obligations and mitigate the impact to consumers, employees or the Company from the incident.
Our disaster recovery plans require that data in the production environment be frequently snapshotted and stored durably in multiple geographic locations in the US. Backups are maintained for the duration of the customer relationship and for one year after the termination of an agreement unless otherwise specified or required by law.
Customer data is backed up by Slashbit's operations team. In the event of an exception, operations personnel perform troubleshooting to identify the root cause and then re-run the backup job immediately or as part of the next scheduled backup job.
Backup infrastructure is maintained in GCP, with physical access restricted according to applicable GCP policies. All backups are encrypted using KMS-managed encryption keys, with access restricted to key personnel via GCP IAM permissions.
The data importer undertakes to adopt supplementary measures to protect the Personal Data transferred under the EU Standard Contractual Clauses from the data exporter to the United States of America ("Transferred Data") by implementing appropriate technical and organizational safeguards, such as encryption or similar technologies, access controls or other compensating controls, to protect Transferred Data against any interference that goes beyond what is necessary in a democratic society to safeguard national security, defence and public security. Specifically, the data importer warrants that it is not required by national law to create or maintain any means to facilitate access to its systems and/or the Transferred Data by government authorities, such as a back door, or for the data importer to be in possession or to hand over the encryption key to access such data. In the event that the data importer receives a legally binding request for access to the SCC Personal Data by a government authority of the USA ("Disclosure Request"), the data importer will:1. promptly notify the data exporter of such request to enable the data exporter to intervene and seek relief from such disclosure, unless the data importer is otherwise prohibited from providing such notice, such as a prohibition under criminal law to preserve the confidentiality of a law enforcement investigation; and2. promptly inform the government authority if, in the data importer's opinion, such request is inconsistent and/or conflicts with its obligations pursuant to the EU Standard Contractual Clauses. The data importer will document any such communication with the public authorities relating to the inconsistency and/or conflict of such request with the EU Standard Contractual Clauses;"
