Security and compliance / Mass notification and critical events
Mobile Text Alerts
What Mobile Text Alerts publishes on mobile-text-alerts.com, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.
Transparency 22/100 FBand F
Rank 5 of 12 in Mass notification and critical eventscategory median 17checked 2026-09-02
9 gaps found: 9 criteria not found at the addresses we checked. 3 found9 not found0 not measured
Public transparency score, not a product or security rating.
Transparency labelsaas-ranking.com
Mobile Text Alerts
- A
- B
- C
- D
- E
- F
Published commitments2 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
Checked 2026-09-02. 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.
We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.
Show the full transparency label
Transparency labelsaas-ranking.com
Mobile Text Alerts
- A
- B
- C
- D
- E
- F
Published commitments2 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
Checked 2026-09-02. 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.
We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.
Not found, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-02.
Show the 8 addresses we checked
https://mobile-text-alerts.com/legal/dpa– reached, no match (HTTP 404)https://mobile-text-alerts.com/dpa– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://mobile-text-alerts.com/data-processing-agreement– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/data-processing-addendum– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/gdpr– reached, no match (HTTP 404)https://mobile-text-alerts.com/trust/dpa– reached, no match (HTTP 404)https://mobile-text-alerts.com/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-02.
Show the 7 addresses we checked
https://mobile-text-alerts.com/legal/subprocessors– reached, no match (HTTP 404)https://mobile-text-alerts.com/subprocessors– reached, no match (HTTP 404)https://mobile-text-alerts.com/sub-processors– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/sub-processors– reached, no match (HTTP 404)https://mobile-text-alerts.com/trust/subprocessors– reached, no match (HTTP 404)https://mobile-text-alerts.com/privacy/subprocessors– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/subprocessor-list– reached, no match (HTTP 404)
Data location stated
weight 3 of 3No statement about data location found.
Checked 7 addresses on 2026-09-02.
Show the 7 addresses we checked
https://mobile-text-alerts.com/security– reached, no match (HTTP 404)https://mobile-text-alerts.com/trust– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/privacy– reached, no match (HTTP 404)https://mobile-text-alerts.com/privacy– reached, no match (HTTP 404)https://mobile-text-alerts.com/privacy-policy– reached, no match (HTTP 200)https://mobile-text-alerts.com/compliance– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/privacy-policy– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-02.
Show the 3 addresses we checked
https://status.mobile-text-alerts.com/– Could not be fetched: fetch failed.https://mobile-text-alerts.com/status– reached, no match (HTTP 404)https://mobile-text-alerts.com.statuspage.io/– Could not be fetched: fetch failed.
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-02.
Show the 1 address we checked
https://mobile-text-alerts.com/– third-party requests before any interaction: a.quora.com, api.segment.io, assets.calendly.com, bat.bing.com, bat.bing.net, cdn.segment.com, connect.facebook.net, dev.visualwebsiteoptimizer.com, mpc-prod-23-s6uit34pua-ue.a.run.app, mta-cdk-site-cms-prod.s3.us-west-2.amazonaws.com, px.ads.linkedin.com, q.quora.com, s3-us-west-2.amazonaws.com, sc.lfeeder.com, scripts.clarity.ms, scripts.kissmetrics.io, snap.licdn.com, tr-rc.lfeeder.com, tracking-api.g2.com, tracking.g2crowd.com, www.clarity.ms, www.facebook.com, www.googletagmanager.com, z.clarity.ms
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-02.
Show the 8 addresses we checked
https://mobile-text-alerts.com/legal/subprocessors– reached, no match (HTTP 404)https://mobile-text-alerts.com/subprocessors– reached, no match (HTTP 404)https://mobile-text-alerts.com/sub-processors– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/dpa– reached, no match (HTTP 404)https://mobile-text-alerts.com/dpa– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://mobile-text-alerts.com/trust/subprocessors– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/sub-processors– reached, no match (HTTP 404)
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-02.
Show the 6 addresses we checked
https://mobile-text-alerts.com/security– reached, no match (HTTP 404)https://mobile-text-alerts.com/trust– reached, no match (HTTP 404)https://mobile-text-alerts.com/trust-center– reached, no match (HTTP 404)https://mobile-text-alerts.com/compliance– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/security– reached, no match (HTTP 404)https://trust.mobile-text-alerts.com/– The name "trust.mobile-text-alerts.com" could not be resolved.
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-02.
Show the 6 addresses we checked
https://mobile-text-alerts.com/legal/sla– reached, no match (HTTP 404)https://mobile-text-alerts.com/sla– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/service-level-agreement– reached, no match (HTTP 404)https://mobile-text-alerts.com/trust/sla– reached, no match (HTTP 404)https://mobile-text-alerts.com/uptime– reached, no match (HTTP 404)https://mobile-text-alerts.com/legal/uptime-sla– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-02.
Show the 1 address we checked
https://mobile-text-alerts.com/.well-known/security.txt– reached, no match (HTTP 404)
Published evidence 3
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://mobile-text-alerts.com/pricing · checked 2026-09-02
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://mobile-text-alerts.com/ · checked 2026-09-02
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://mobile-text-alerts.com/privacy-policy · checked 2026-09-02