Client portal flagged by Mimecast: ngrok reference in page metadata + domain list request

Hi Queue team,

One of our corporate clients uses Mimecast, and it opens our portal (projects.cutpointstudio.com, CNAME to cutpointstudio.usequeue.com) in Browser Isolation, which cuts their sessions off after five minutes. While looking into why, I found a few things on the portal's sign-in page that are likely making security filters treat it as suspicious.

1. ngrok reference in the page metadata

The sign-in page includes this meta tag:

<meta name="twitter:domain" content="masud.queue.ngrok.io">

ngrok domains are commonly associated with phishing, so this is a strong red flag for scanners. It looks like a leftover from a development setup. Could you remove it, or set it to the portal's own domain?

2. Blank page title

The sign-in page has an empty <title>. Can this be set to our workspace name (Cutpoint Studio), or is there a setting where I can change it?

3. Third-party scripts on the sign-in page

The sign-in page loads Apollo tracking (assets.apollo.io, aplo-evnt.com) and Plaid (cdn.plaid.com) before anyone signs in. A bank-linking script on an email-entry page fits the pattern filters look for in phishing pages. Could these load only after sign-in, or only where they're needed?

4. Login page content

Is there a way to add branding or a short line of text to the sign-in page, so it doesn't present as a bare email form?

Thanks for your help. This is blocking work with a client, so a quick fix on the ngrok tag in particular would be much appreciated.

Otherwise, I'll be forced to use a different service.