Contract Integration · Relyance AI Docs

Overview

This integration analyzes your vendor agreements and produces high-level summaries of the terms and clauses from your vendor contracts.

Why is this integration important?

The contract integration helps with:

Populating the Data Inventory and Map: Relyance scans agreements to identify the third-party vendor and automatically makes them visible in the data map. This contributes to the automatic creation of a robust data map without any manual intervention.
DPA provision summary: From executed DPAs, our Machine Learning models help extract key provisions such as Categories of Personal Data, Basis of Data Transfer, Data Subject Request provisions, etc. and summarize them for easy consumption in the platform.
Robust ROPA: Provisions and information from scanning the DPA are automatically added to the Relyance Universal ROPA (Records of Processing Activity).
Compare and Contrast: W e can compare and contrast data that is outlined in the contact vs what's actually being processed in the source code and flag those discrepancies via our Intelligent Insights.

Integration Details:

Details about how to configure the Contract Integration are listed below:

Stakeholders Needed	We typically work with the Privacy / Legal teams to identify the source folder for vendor contracts and connect with your Contract Lifecycle Management tool.
Effort	The integration time is a few seconds to a few minutes at best.
Integration Configuration Summary	While we have step by step guides, a generic process to configure the infrastructure integration is below: To get started, navigate to Settings > Integrations > Contract Integration. Find the desired vendor and click it to open its connections. In the Create Connection section, select the desired connection type. Provide the appropriate connection details such as API Keys, Folder Names, etc. to configure the connection and click Save. Relyance also provides step-by-step guides for the specific integrations. Note: In the current state, Relyance ML models scan executed vendor agreements that are stored as PDFs. Any non-PDF or non-vendor-based agreements (such as customer agreements) will be ignored by our ingestion model.

Stakeholders Needed

We typically work with the Privacy / Legal teams to identify the source folder for vendor contracts and connect with your Contract Lifecycle Management tool.

Effort

The integration time is a few seconds to a few minutes at best.

Integration Configuration Summary

While we have step by step guides, a generic process to configure the infrastructure integration is below: To get started, navigate to Settings > Integrations > Contract Integration. Find the desired vendor and click it to open its connections. In the Create Connection section, select the desired connection type. Provide the appropriate connection details such as API Keys, Folder Names, etc. to configure the connection and click Save. Relyance also provides step-by-step guides for the specific integrations. Note: In the current state, Relyance ML models scan executed vendor agreements that are stored as PDFs. Any non-PDF or non-vendor-based agreements (such as customer agreements) will be ignored by our ingestion model.