Universe
universe.com · Event management · checked 2026-09-03
Rank 6 of 19 in Event management, where the median is 26.
- 4 found
- 8 not found
- 0 not measured
We measured 12 of 12 criteria for Universe on 2026-09-03. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 35 out of 100, band E.
Overview
Transparency labelsaas-ranking.com
Universe
- A
- B
- C
- D
- E
- F
Published commitments4 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- 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 behaviour0 of 3 found
- not foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
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 Universe has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://universe.com/legal/dpa– reached, no match (HTTP 404)https://universe.com/dpa– reached, no match (HTTP 404)https://universe.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://universe.com/data-processing-agreement– reached, no match (HTTP 404)https://universe.com/legal/data-processing-addendum– reached, no match (HTTP 404)https://universe.com/legal/gdpr– reached, no match (HTTP 404)https://universe.com/trust/dpa– reached, no match (HTTP 404)https://universe.com/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://universe.com/legal/subprocessors– reached, no match (HTTP 404)https://universe.com/subprocessors– reached, no match (HTTP 404)https://universe.com/sub-processors– reached, no match (HTTP 404)https://universe.com/legal/sub-processors– reached, no match (HTTP 404)https://universe.com/trust/subprocessors– reached, no match (HTTP 404)https://universe.com/privacy/subprocessors– reached, no match (HTTP 404)https://universe.com/legal/subprocessor-list– reached, no match (HTTP 404)
HTTPS enforced with HSTS
weight 2 of 3No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-09-03.
Show the 2 addresses we checked
http://universe.com/– HTTP 301, no redirect to HTTPShttps://universe.com/– HSTS max-age=300
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://universe.com/– third-party requests before any interaction: cdn.cookielaw.org, cdn.jsdelivr.net, cdn.prod.website-files.com, cdn.transifex.com, connect.facebook.net, d3e54v103j8qbb.cloudfront.net, telemetry.svc.transifex.net, www.googletagmanager.com
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://universe.com/legal/subprocessors– reached, no match (HTTP 404)https://universe.com/subprocessors– reached, no match (HTTP 404)https://universe.com/sub-processors– reached, no match (HTTP 404)https://universe.com/legal/dpa– reached, no match (HTTP 404)https://universe.com/dpa– reached, no match (HTTP 404)https://universe.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://universe.com/trust/subprocessors– reached, no match (HTTP 404)https://universe.com/legal/sub-processors– reached, no match (HTTP 404)
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://universe.com/security– reached, no match (HTTP 404)https://universe.com/trust– reached, no match (HTTP 200)https://universe.com/trust-center– reached, no match (HTTP 404)https://universe.com/compliance– reached, no match (HTTP 404)https://universe.com/legal/security– reached, no match (HTTP 404)https://trust.universe.com/– The name "trust.universe.com" could not be resolved.
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://universe.com/legal/sla– reached, no match (HTTP 404)https://universe.com/sla– reached, no match (HTTP 404)https://universe.com/legal/service-level-agreement– reached, no match (HTTP 404)https://universe.com/trust/sla– reached, no match (HTTP 404)https://universe.com/uptime– reached, no match (HTTP 404)https://universe.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-03.
Show the 1 address we checked
https://universe.com/.well-known/security.txt– 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 4
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://www.universe.com/privacy · checked 2026-09-03
Status page with history
weight 2 of 3A public status page with incident history.
Source: https://status.universe.com/ · checked 2026-09-03
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://www.universe.com/pricing · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.universe.com/privacy · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.