runsonwhat

Banco Security's tech stack

What does Banco Security use?

Banco Security (bancosecurity.cl) uses at least 16 tools we can see from public records, including HubSpot for sales, Google Analytics for analytics, Metricool for marketing and Cloudflare for content delivery. Last checked .

Industry
Banking
Size
1,001–5,000 employees
Based in
Santiago, Chile
Founded
1981
LinkedIn
Company page
Tools found
16
Categories
9
Layers
5 of 5
Last checked
Oct 2026

Banco Security's stack, layer by layer

Each tool links to the other companies we've found using it. The label says what kind of public trace gave it away.

Edge & Hosting

1 tool, where the bytes are served from

Application

1 tool, what the product is built with

Data & Observability

4 tools, what they measure and store

Go-to-market

7 tools, how they find and keep customers

Company Ops

3 tools, what the team runs on day to day

Email Delivery

Security & Compliance

Banco Security tech stack FAQ

What tools does Banco Security use?

We've found 16 tools at Banco Security (bancosecurity.cl). Edge & Hosting: Cloudflare. Application: jQuery. Data & Observability: Google Analytics, Google Tag Manager and Microsoft Clarity. Go-to-market: Meta Pixel, Google Ads and HubSpot. Company Ops: SendGrid, GlobalSign and EasyDMARC. Last checked October 3, 2026.

What CRM does Banco Security use?

Banco Security uses HubSpot for sales and CRM. We found HubSpot through website code.

What analytics tools does Banco Security use?

Banco Security uses Google Analytics, Google Tag Manager and Microsoft Clarity for analytics. We found Google Analytics through website code.

What marketing software does Banco Security use?

Banco Security uses Metricool for marketing. We found Metricool through website code.

Does Banco Security use Cloudflare?

Yes. We found Cloudflare at Banco Security through custom domain and website code. Cloudflare is used by 147,753 companies we track.

How does runsonwhat know what Banco Security uses?

We read public traces only: Banco Security's DNS and email records, certificate logs, the code its website loads, and published subprocessor lists. A tool is listed only when a direct record backs it up. DNS is rechecked weekly and the website monthly.

We read public traces only: DNS and email records, certificate logs, website code and published subprocessor lists. A tool is listed when a direct record backs it up, and dropped when a recheck no longer finds it. Is this your company? See how to opt out.