Help members elevate their thought and understanding of a connected B2B SaaS Revenue Funnel and GTM motion by networking and sharing knowledge.
Contribute to the growth of every member and actively promote Revenue Operations and value of the function in their respective company
Advance the practice of the RevOps operating model in spirit and action
Data encryption
Customer data isolation
API security controlled via API Gateways
API access using secure JWT tokens
SOC2 Type II Compliant
Masking of PII data (optional)
RevSure.AI is now SOC2 Type II Compliant
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.
RevSure.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-central-1a’ zone located in the United States.
Strict Access Security
Monitoring
Power Availability
Personnel
For further information on GCP Security and Compliance refer to the following links:
Customer data is secured in transit using TLS and encrypted at rest within the application. RevSure.AI 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:
When a user visits a website or application which has instrumented the RevSure.AI SDK, details of their interactions are captured and sent to RevSure.AI 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. RevSure.AI 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:
Customer data is stored in separate dataset and customer must have access to APIs (web UI access via username and password) to be able to access the data. This provides logical separation between data belonging to multiple clients. RevSure.AI is the sole tenant on our infrastructure.
We maintain a robust application security program, covering the following:
Our disaster recovery plans require that data in the production environment be frequently snapshotted and stored durably in multiple geographic locations in the US are maintained for the duration of the customer relationship and for one month after the termination of an agreement unless otherwise specified or required by law.
