SaaS Ranking
Menu

Aplos

aplos.com · Church and community management · checked 2026-09-03

22/100FBand F

Rank 10 of 20 in Church and community management, where the median is 19.5.

We measured 12 of 12 criteria for Aplos on 2026-09-03. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 22 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

Aplos

aplos.com · Church and community management

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 22of 100 Rank 10 of 20

Published commitments3 of 9 found

Measured behaviour0 of 3 found

Checked 2026-09-03. 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.

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 Aplos has no such document.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-03.

Show the 8 addresses we checked
  1. https://aplos.com/legal/dpa – blocked or unavailable (HTTP 403)
  2. https://aplos.com/dpa – blocked or unavailable (HTTP 403)
  3. https://aplos.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://aplos.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://aplos.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://aplos.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://aplos.com/trust/dpa – reached, no match (HTTP 404)
  8. https://aplos.com/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://aplos.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://aplos.com/subprocessors – reached, no match (HTTP 404)
  3. https://aplos.com/sub-processors – reached, no match (HTTP 404)
  4. https://aplos.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://aplos.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://aplos.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://aplos.com/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://www.aplos.com/privacy · checked 2026-09-03

Show the 7 addresses we checked
  1. https://aplos.com/security – reached, no match (HTTP 200)
  2. https://aplos.com/trust – reached, no match (HTTP 404)
  3. https://aplos.com/legal/privacy – reached, no match (HTTP 404)
  4. https://aplos.com/privacy – found, but behind a sign-in
  5. https://aplos.com/privacy-policy – reached, no match (HTTP 404)
  6. https://aplos.com/compliance – reached, no match (HTTP 404)
  7. https://aplos.com/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-03.

Show the 2 addresses we checked
  1. http://aplos.com/ – redirects to https://aplos.com/
  2. https://aplos.com/ – no HSTS header

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://aplos.com/ – third-party requests before any interaction: ad.doubleclick.net, ajax.googleapis.com, alb.reddit.com, analytics.ahrefs.com, api.claydar.com, api.hubapi.com, api.hubspot.com, app.hubspot.com, app.leandata.com, app.qualified.com, bat.bing.com, cdn-cookieyes.com, cdn.claydar.com, cdn.jsdelivr.net, cdn.leandata.com, cdn.prod.website-files.com, cdn1.leandata.com, connect.facebook.net, d3e54v103j8qbb.cloudfront.net, ddwl4m2hdecbv.cloudfront.net, dev.visualwebsiteoptimizer.com, fonts.googleapis.com, fonts.gstatic.com, googleads.g.doubleclick.net, grsm.io, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hubspot.com, js.qualified.com, js.usemessages.com, partnerlinks.io, partnerstack.joinvelora.com, pixel-config.reddit.com, px.ads.linkedin.com, r2.leadsy.ai, region1.analytics.google.com, scripts.clarity.ms, snap.licdn.com, static.claydar.com, static.cloudflareinsights.com, stats.g.doubleclick.net, t.clarity.ms, tracking-api.g2.com, tracking.g2crowd.com, www.clarity.ms, www.facebook.com, www.google.com, www.google.de, www.googletagmanager.com, www.redditstatic.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-03.

Show the 8 addresses we checked
  1. https://aplos.com/legal/subprocessors – blocked or unavailable (HTTP 403)
  2. https://aplos.com/subprocessors – blocked or unavailable (HTTP 403)
  3. https://aplos.com/sub-processors – reached, no match (HTTP 404)
  4. https://aplos.com/legal/dpa – reached, no match (HTTP 404)
  5. https://aplos.com/dpa – reached, no match (HTTP 404)
  6. https://aplos.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://aplos.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://aplos.com/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://aplos.com/legal/sla – reached, no match (HTTP 404)
  2. https://aplos.com/sla – reached, no match (HTTP 404)
  3. https://aplos.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://aplos.com/trust/sla – reached, no match (HTTP 404)
  5. https://aplos.com/uptime – reached, no match (HTTP 404)
  6. https://aplos.com/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://aplos.com/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://www.aplos.com/privacy · checked 2026-09-03

Show the 7 addresses we checked
  1. https://aplos.com/legal/privacy – reached, no match (HTTP 404)
  2. https://aplos.com/privacy – found, but behind a sign-in
  3. https://aplos.com/privacy-policy – reached, no match (HTTP 404)
  4. https://aplos.com/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://aplos.com/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://aplos.com/trust/privacy – reached, no match (HTTP 404)
  7. https://aplos.com/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 3
✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.aplos.com/ · checked 2026-09-03

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.aplos.com/pricing · checked 2026-09-03

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://www.aplos.com/security · checked 2026-09-03

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare