Transparency alternatives to Slides
Other Presentation software vendors we measure, sorted by how much we found at them and not at Slides. This is a comparison of disclosure, not of features or fitness.
11 shown of 11 that differ from Slides on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Slides has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Slides” is the one that closes them.
| Vendor | Score | Found there, not found at Slides | Found at Slides, not found there | |
|---|---|---|---|---|
| AhaSlidesahaslides.comSee also Transparency alternatives to AhaSlides | 52/100 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | 1 Named privacy contact | Compare |
| Vismevisme.coSee also Transparency alternatives to Visme | 41/100 | 2 Status page with history, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Presentations.AIpresentations.aiSee also Transparency alternatives to Presentations.AI | 30/100 | 2 Data processing agreement, Notice before subprocessors change | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| MagicSlidesmagicslides.appSee also Transparency alternatives to MagicSlides | 22/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Plusplusai.comSee also Transparency alternatives to Plus | 22/100 | 2 Certifications named, HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Haiku Deckhaikudeck.comSee also Transparency alternatives to Haiku Deck | 35/100 | 1 HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Chroniclechroniclehq.comSee also Transparency alternatives to Chronicle | 17/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Decktopusdecktopus.comSee also Transparency alternatives to Decktopus | 17/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Sendstepssendsteps.comSee also Transparency alternatives to Sendsteps | 17/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Storydocstorydoc.comSee also Transparency alternatives to Storydoc | 13/100 | nothing we found there and not here | 2 Data location stated, security.txt (RFC 9116) | Compare |
| SlidesAIslidesai.ioSee also Transparency alternatives to SlidesAI | 9/100 | nothing we found there and not here | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.