Skip to main content

Security at Onboard B2B

How we protect your store's data, and how recent security issues affect Onboard B2B.

Onboard B2B is made by Helium, which is SOC 2 Type II certified. An independent auditor regularly reviews how we handle your data.

Since October 2026, several security issues have been reported in tools that many websites are built on, and in some Shopify apps. If you're wondering whether Onboard B2B is affected, this article answers that, and explains how we keep your store's data safe.

Recent security issues

When a security issue is announced, we check whether Onboard B2B uses the affected software. If it does, we update Onboard B2B as soon as a fix is available. Here's where each recent issue stands.

Issue

Does it affect Onboard B2B?

What we did

PHP2Shell (CVE-2026-109618, CVE-2026-109619)

No

Onboard B2B doesn't use PHP.

Next.js (CVE-2026-96889)

No

Onboard B2B doesn't use Next.js.

Apache Tomcat (CVE-2026-101296, CVE-2026-101356, CVE-2026-103119)

No

Onboard B2B doesn't use Tomcat or Java.

MySQL

No

Onboard B2B doesn't use MySQL.

Brotli in server operating systems

No

Our servers don't include the affected package.

Node.js October 2026 release, including Brotli (CVE-2026-111497)

Yes

Updated to the fixed version on October 26, 2026.

body-parser denial of service

Yes

Updated to the fixed version on October 28, 2026.

Checkout redirects to fake payment pages (October 2026)

No

Some apps' storefront code was changed to send shoppers to fake payment pages. Onboard B2B wasn't one of the affected apps, and it doesn't change your checkout.

Gorgias security incident (October 2026)

No

We don't use Gorgias.

Every update we ship is listed in the Onboard B2B changelog.

How we protect your data

An independent auditor checks our security, availability, processing integrity, confidentiality and privacy controls for our SOC 2 Type II report. To request a copy, reach out to our support.

Onboard B2B runs on Google Cloud. All data between your store, your customers and Onboard B2B is encrypted with TLS, and outdated protocols like SSL 3.0 are turned off. We back up production data every day.

Our team uses two-factor authentication wherever it can, with hardware security keys preferred, and each person can only reach the systems their job needs. Every code change is reviewed by more than one person and checked by automated tests before it goes live.

You can see whether Onboard B2B is running normally at status.heliumdev.com.

The Security section in your Shopify admin

Shopify recently added a Security section to each app's page in your admin, under Settings > Apps.

These are new standards Shopify is asking every app to meet. As they arrive we continually update Onboard B2B to meet them.

Expiring access tokens: if this shows as Missing for Onboard B2B, we're aware of this new requirement and our team is working on it.

Security questionnaires

For a security questionnaire or our SOC 2 report, reach out to our support. Our security page, Data Processing Agreement and subprocessors list answer most questions.

Did this answer your question?