SlackVault Data Security - Where Your Archive Lives

Data securitySlackVault reduces risk mainly by not holding your data. Message content travels from Slack to the Firebase project you own via the extension in your browser, so there is no central archive to breach. The Slack client secret is kept server-side in a Cloudflare Worker used only for the OAuth code exchange and token refresh, which keeps it out of every shipped bundle.What this covers

Slack client secrets stay in a Cloudflare Worker, never in the website or extension bundle.

Message content is written straight from your browser to your Firebase project.

Requested Slack scopes are read-only.

Analytics never cover message content.

What SlackVault does not do

Securing your own Firebase project, including its security rules and who can read it, is your responsibility.

A workspace access token held by the extension can read your workspace, so treat the browser profile it runs in as sensitive.

No formal third-party security audit or compliance certification has been carried out.

Creating your Slack app

Frequently asked questions

Deleting your account and data

Written by Ahsan Mahmood. Last updated 2026-07-21.https://slackvault.aoneahsan.com/legal/security