Monte Carlo
montecarlodata.com · Product information management · checked 2026-09-05
Rank 20 of 37 in Product information management, where the median is 26.
- 3 found
- 9 not found
- 0 not measured
We measured 12 of 12 criteria for Monte Carlo on 2026-09-05. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 26 out of 100, band E.
Overview
Transparency labelsaas-ranking.com
Monte Carlo
- A
- B
- C
- D
- E
- F
Published commitments1 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour2 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- foundsecurity.txt (RFC 9116)×1
Checked 2026-09-05. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.
The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.
The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.
Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Monte Carlo has no such document.
What they state
The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.
- Third-party hosts we saw on the first load 4 googleapis.com, montecarlo.ai, mutinycdn.com, qualified.com.
Show the 4 exact wordings
fonts.googleapis.com
Read at https://montecarlodata.com/montecarlo.ai
Read at https://montecarlodata.com/client-registry.mutinycdn.com
Read at https://montecarlodata.com/app.qualified.com, js.qualified.com
Read at https://montecarlodata.com/ - HSTS max-age 31536000 seconds (365 days).
Show the exact wording
max-age=31536000; includeSubDomains
Read at https://montecarlodata.com/ - HSTS options includeSubDomains.
Show the exact wording
max-age=31536000; includeSubDomains
Read at https://montecarlodata.com/ - The file expires 2030-01-01. It was still valid when we checked on 2026-09-05.
Show the exact wording
Expires: 2030-01-01T00:00:00.000Z
Read at https://montecarlo.ai/.well-known/security.txt
Gaps, heaviest first
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-05.
Show the 7 addresses we checked
https://montecarlodata.com/legal/subprocessors– reached, no match (HTTP 404)https://montecarlodata.com/subprocessors– reached, no match (HTTP 404)https://montecarlodata.com/sub-processors– reached, no match (HTTP 404)https://montecarlodata.com/legal/sub-processors– reached, no match (HTTP 404)https://montecarlodata.com/trust/subprocessors– reached, no match (HTTP 404)https://montecarlodata.com/privacy/subprocessors– reached, no match (HTTP 404)https://montecarlodata.com/legal/subprocessor-list– reached, no match (HTTP 404)
Data location stated
weight 3 of 3We found this behind a sign-in, so it is not published openly.
Seen at https://montecarlo.ai/privacy-policy · checked 2026-09-05
Show the 7 addresses we checked
https://montecarlodata.com/security– blocked or unavailable (HTTP 403)https://montecarlodata.com/trust– blocked or unavailable (HTTP 403)https://montecarlodata.com/legal/privacy– found, but behind a sign-inhttps://montecarlodata.com/privacy– found, but behind a sign-inhttps://montecarlodata.com/privacy-policy– found, but behind a sign-inhttps://montecarlodata.com/compliance– reached, no match (HTTP 404)https://montecarlodata.com/legal/privacy-policy– found, but behind a sign-in
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-05.
Show the 3 addresses we checked
https://status.montecarlodata.com/– The name "status.montecarlodata.com" could not be resolved.https://montecarlodata.com/status– reached, no match (HTTP 404)https://montecarlodata.com.statuspage.io/– Could not be fetched: fetch failed.
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-05.
Show the 5 addresses we checked
https://montecarlodata.com/pricing– reached and rendered, no matchhttps://montecarlodata.com/pricing/– reached, no match (HTTP 200)https://montecarlodata.com/plans– reached, no match (HTTP 404)https://montecarlodata.com/en/pricing– reached, no match (HTTP 200)https://montecarlodata.com/pricing-plans– reached, no match (HTTP 404)
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
- Third-party hosts we saw on the first load 4 googleapis.com, montecarlo.ai, mutinycdn.com, qualified.com.
Show the 4 exact wordings
fonts.googleapis.com
Read at https://montecarlodata.com/montecarlo.ai
Read at https://montecarlodata.com/client-registry.mutinycdn.com
Read at https://montecarlodata.com/app.qualified.com, js.qualified.com
Read at https://montecarlodata.com/
Checked 1 address on 2026-09-05.
Show the 1 address we checked
https://montecarlodata.com/– third-party requests before any interaction: app.qualified.com, client-registry.mutinycdn.com, fonts.googleapis.com, js.qualified.com, montecarlo.ai
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-05.
Show the 8 addresses we checked
https://montecarlodata.com/legal/subprocessors– reached, no match (HTTP 404)https://montecarlodata.com/subprocessors– reached, no match (HTTP 404)https://montecarlodata.com/sub-processors– reached, no match (HTTP 404)https://montecarlodata.com/legal/dpa– reached, no match (HTTP 404)https://montecarlodata.com/dpa– reached, no match (HTTP 404)https://montecarlodata.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://montecarlodata.com/trust/subprocessors– reached, no match (HTTP 404)https://montecarlodata.com/legal/sub-processors– reached, no match (HTTP 404)
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-05.
Show the 6 addresses we checked
https://montecarlodata.com/security– blocked or unavailable (HTTP 403)https://montecarlodata.com/trust– blocked or unavailable (HTTP 403)https://montecarlodata.com/trust-center– reached, no match (HTTP 404)https://montecarlodata.com/compliance– reached, no match (HTTP 404)https://montecarlodata.com/legal/security– reached, no match (HTTP 404)https://trust.montecarlodata.com/– blocked or unavailable (HTTP 403)
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-05.
Show the 6 addresses we checked
https://montecarlodata.com/legal/sla– reached, no match (HTTP 200)https://montecarlodata.com/sla– reached, no match (HTTP 200)https://montecarlodata.com/legal/service-level-agreement– reached, no match (HTTP 404)https://montecarlodata.com/trust/sla– reached, no match (HTTP 200)https://montecarlodata.com/uptime– reached, no match (HTTP 404)https://montecarlodata.com/legal/uptime-sla– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3We found this behind a sign-in, so it is not published openly.
Seen at https://montecarlo.ai/privacy-policy · checked 2026-09-05
Show the 7 addresses we checked
https://montecarlodata.com/legal/privacy– found, but behind a sign-inhttps://montecarlodata.com/privacy– found, but behind a sign-inhttps://montecarlodata.com/privacy-policy– found, but behind a sign-inhttps://montecarlodata.com/legal/privacy-policy– found, but behind a sign-inhttps://montecarlodata.com/legal/privacy-notice– reached, no match (HTTP 404)https://montecarlodata.com/trust/privacy– found, but behind a sign-inhttps://montecarlodata.com/datenschutz– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 3
Data processing agreement
weight 3 of 3Published and readable without a login.
Source: https://montecarlo.ai/data-processing-addendum · checked 2026-09-05
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
- HSTS max-age 31536000 seconds (365 days).
Show the exact wording
max-age=31536000; includeSubDomains
Read at https://montecarlodata.com/ - HSTS options includeSubDomains.
Show the exact wording
max-age=31536000; includeSubDomains
Read at https://montecarlodata.com/
Source: https://montecarlodata.com/ · checked 2026-09-05
security.txt (RFC 9116)
weight 1 of 3Served at /.well-known/security.txt.
- The file expires 2030-01-01. It was still valid when we checked on 2026-09-05.
Show the exact wording
Expires: 2030-01-01T00:00:00.000Z
Read at https://montecarlo.ai/.well-known/security.txt
Source: https://montecarlo.ai/.well-known/security.txt · checked 2026-09-05
History
Not enough completed runs yet to draw a line. The next runs fill this in.
Compare
A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.