This page answers the questions people ask most often before trusting SlackVault with a workspace archive, grouped around security, cost, coverage and export. The short version is that your data goes to your own Firebase project, there is nothing to pay us, and coverage is bounded by what the Slack API will return for your plan and scopes.
Only whoever can access your Firebase project. SlackVault stores no copy of your messages, so access control is entirely governed by your own project settings.
The Slack client secret stays server-side in a Cloudflare Worker that performs the OAuth code exchange. It is never included in the website or extension bundle.
No. Message content is never used for analytics. Product analytics cover app usage only, and are disabled when their keys are not configured.
No. The scopes it requests are read-only, so it cannot post, edit or delete messages in your workspace.
Anything synced before deletion stays in your archive. Anything deleted before it was ever synced cannot be retrieved, because the API no longer returns it.
Your archive is unaffected, because it lives in your Firebase project and can be read with any Firebase client or exported to JSON, CSV or PDF.
Yes. Each workspace is connected separately with its own Slack app authorisation and appears as its own archive.
As much as your Slack plan exposes through the API and your Firebase quota can hold. Plans that restrict history access restrict what any backup tool can read.
Written by Ahsan Mahmood. Last updated 2026-07-21.
https://slackvault.aoneahsan.com/docs/faq