Is consent required for Boomi on my website?

Conditional. Boomi is categorized as functional. It operates primarily as a backend integration platform with minimal browser-side scripts. Any embedded workflow forms that set preference cookies require consent under GDPR. CCPA disclosure is needed if personal data is processed.

What does Boomi track or collect on a website?

Boomi has minimal browser-side presence on customer-facing websites. When embedded forms or API connectors are present, they may collect submitted form data and set functional cookies to maintain session state during multi-step workflow interactions.

How does ConsentStack detect Boomi on a website?

ConsentStack detects Boomi by identifying its embedded form loaders and API connector scripts. It is classified as functional. On consent grant, Boomi workflow components initialize normally. On denial, embedded integration forms are blocked from loading on the page.

What tracker domains does Boomi use?

ConsentStack has catalogued tracker domains for Boomi including boomi.com. These are the network destinations Boomi's scripts contact, which a consent platform blocks until a visitor agrees.

Boomi - Integration Platform Privacy Overview

Back to Vendor Library

Overview

Boomi is an enterprise integration platform as a service (iPaaS) that connects cloud applications, on-premises systems, and data sources through a visual workflow designer. It enables organizations to automate data flows between ERP, CRM, HR, and e-commerce systems without custom code. Boomi operates entirely as a backend infrastructure service and has no meaningful presence as a client-side script on public-facing websites.

What This Script Does

Boomi's browser-side presence on customer websites is minimal to nonexistent for standard integrations. When Boomi is used to power backend data flows, all processing occurs server-to-server. No JavaScript SDK loads in end-user browsers, and no cookies are set by Boomi on visitor devices.

In rare deployment scenarios, Boomi may surface on a website through an embedded workflow form or a connector that serves an interactive data entry interface. In such cases, form submission data is transmitted to Boomi's API endpoints for processing. These interactions involve server-side data flows rather than client-side tracking or profiling.

Consent & Compliance

Because Boomi does not deploy client-side scripts or set cookies on websites in standard configurations, it falls outside the scope of the ePrivacy Directive's consent requirements at the website layer. There are no tracking pixels, behavioral profiling mechanisms, or persistent identifiers set by Boomi in visitor browsers.

Under GDPR, if Boomi is used to process personal data as part of a backend integration (for example, syncing customer records between systems), it acts as a data processor under Article 28, and a data processing agreement between the site operator and Boomi covers that relationship. Under CCPA, Boomi operates as a service provider for enterprise data integration with no independent monetization of visitor data.

Should You Block This Without Consent?

No. Boomi does not set cookies or execute tracking scripts on websites. There is no client-side component to block at the consent management layer. Data governance for Boomi integrations is handled through data processing agreements and backend configuration, not through website consent management platforms.

Is Boomi GDPR compliant?

Boomi typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Boomi can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Boomi, not on Boomi itself.

Visit website