SaaS Ranking

Content, media and collaboration / Document management

Amagno

What Amagno publishes on amagno.de, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 4/100 FBand F

Rank 5 of 7 in Document managementcategory median 9checked 2026-09-02

11 gaps found: 11 criteria not found at the addresses we checked. 1 found11 not found0 not measured

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Amagno

amagno.de · Document management

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

Published commitments1 of 9 found

Measured behaviour0 of 3 found

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

Amagno

amagno.de · Document management

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

Published commitments1 of 9 found

Measured behaviour0 of 3 found

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 3

No data processing agreement found.

Checked 8 addresses on 2026-09-02.

Show the 8 addresses we checked
  1. https://amagno.de/legal/dpa – reached, no match (HTTP 404)
  2. https://amagno.de/dpa – reached, no match (HTTP 404)
  3. https://amagno.de/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://amagno.de/data-processing-agreement – reached, no match (HTTP 404)
  5. https://amagno.de/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://amagno.de/legal/gdpr – reached, no match (HTTP 404)
  7. https://amagno.de/trust/dpa – reached, no match (HTTP 404)
  8. https://amagno.de/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-02.

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

Is this wrong? Send us the URL

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-02.

Show the 7 addresses we checked
  1. https://amagno.de/security – reached, no match (HTTP 404)
  2. https://amagno.de/trust – reached, no match (HTTP 200)
  3. https://amagno.de/legal/privacy – reached, no match (HTTP 404)
  4. https://amagno.de/privacy – reached, no match (HTTP 404)
  5. https://amagno.de/privacy-policy – reached, no match (HTTP 410)
  6. https://amagno.de/compliance – reached, no match (HTTP 200)
  7. https://amagno.de/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-02.

Show the 3 addresses we checked
  1. https://status.amagno.de/ – Could not be fetched: fetch failed.
  2. https://amagno.de/status – reached, no match (HTTP 404)
  3. https://amagno.de.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-02.

Show the 5 addresses we checked
  1. https://amagno.de/pricing – reached, no match (HTTP 410)
  2. https://amagno.de/pricing/ – reached, no match (HTTP 410)
  3. https://amagno.de/plans – reached, no match (HTTP 404)
  4. https://amagno.de/en/pricing – reached, no match (HTTP 404)
  5. https://amagno.de/pricing-plans – 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-02.

Show the 2 addresses we checked
  1. http://amagno.de/ – redirects to https://amagno.de/
  2. https://amagno.de/ – 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-02.

Show the 1 address we checked
  1. https://amagno.de/ – third-party requests before any interaction: ad.doubleclick.net, bat.bing.com, cdn.leadinfo.eu, connect.facebook.net, googleads.g.doubleclick.net, region1.analytics.google.com, scripts.clarity.ms, snap.licdn.com, stats.g.doubleclick.net, www.clarity.ms, www.google.com, www.google.de, www.googletagmanager.com, www.youtube.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-02.

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

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-02.

Show the 6 addresses we checked
  1. https://amagno.de/security – reached, no match (HTTP 404)
  2. https://amagno.de/trust – reached, no match (HTTP 200)
  3. https://amagno.de/trust-center – reached, no match (HTTP 404)
  4. https://amagno.de/compliance – reached, no match (HTTP 200)
  5. https://amagno.de/legal/security – reached, no match (HTTP 404)
  6. https://trust.amagno.de/ – Could not be fetched: fetch failed.

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-02.

Show the 6 addresses we checked
  1. https://amagno.de/legal/sla – reached, no match (HTTP 404)
  2. https://amagno.de/sla – reached, no match (HTTP 404)
  3. https://amagno.de/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://amagno.de/trust/sla – reached, no match (HTTP 404)
  5. https://amagno.de/uptime – reached, no match (HTTP 404)
  6. https://amagno.de/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-02.

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

Is this wrong? Send us the URL

Published evidence 1

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://amagno.de/datenschutz/ · checked 2026-09-02

Keep going