Evenrow reads. It does not change your systems.
What we do with your data, where it is processed, and who can see what.
Read-only
Evenrow reads agreements and records. It does not write to your systems, and it cannot change a record, a price or a payment. What your team confirms lives in Evenrow, next to the clause, and you decide what to do with it.
Starts on data exports
No integration is needed to begin. The first month runs on exports from your systems: the agreements for one process and the records they govern. A connection to your systems is a later step, and only if you want it.
Where your data is processed
Two options, your choice. Hosted by Evenrow, in the European Union. Or inside your own environment: in your Databricks or Snowflake account, or as Evenrow running in a cloud account you own. In both cases the data stays in the region you choose.
Access follows your permissions
Each person sees the processes and records they are allowed to see. Access is by named user with two-factor sign-in. Staff at Evenrow see a customer's data only for the work you asked for, and every access is logged.
SOC 2 Type II in process with EY
Evenrow's controls for security, availability and confidentiality are being examined by EY. The letter of engagement is available on request under NDA.
NDA before any data is shared
Nothing is sent to Evenrow before a signed NDA. The exports you share are used only for the process you chose, and are deleted on request at the end of the engagement.
Ask us anything about how your data is handled.
Security questionnaires, supplier assessments and architecture questions go to contact@evenrow.ai. We answer them ourselves.
Start with one process: one month, on data exports, no integration.
Send us the exports for one process. A month later your team sees every record of that process against the agreements that govern it, with the clause next to each one.
contact@evenrow.ai