Make (Integromat)

Is Make (Integromat) safe?

For corporate use, only with a written policy in place first: Tangerin AI places Make (Integromat) in the high exposure band. AI automation tool. May have access to internal systems, APIs, and company data via integrations.

Main entry for Make (Integromat) →

Facts

Domain

integromat.com

Category

Automation

Data exposure

High exposureMeasures the data exposure of using the tool, not the vendor's reputation.

Home country

Czechia

Does the free version train on your data?

The vendor's policy could not be verified.

Home country is the headquarters of the company behind the tool. It is not a claim about where data is processed or stored: data residency depends on the plan you hold and must be confirmed with the vendor.

Why Make (Integromat) has high exposure

AI automation tool. May have access to internal systems, APIs, and company data via integrations.

What to do about it

Requires a written policy before approval. Define what kind of data may be entered, verify whether training on your data can be disabled in the plan you hold, and record the tool in your AI inventory. Approving without a policy is the single most common source of audit findings.

Here is the distinction almost every company gets wrong in its first audit: almost no framework (NIST AI RMF, ISO 42001, the EU AI Act) requires you to block AI tools; the exception is the EU AI Act's prohibited practices, such as inferring employees' emotions. What all of them require is that you know what is in use and have made a conscious, recorded decision about each item. A high-exposure tool approved under a written policy is compliance; a low-exposure tool in use with nobody aware of it is an audit finding.