Start with a local evaluation, then scope a pilot around approved Slack channels, governed retrieval, JSONL exports, and deployment evidence.
For testing Slack channel archive workflows before a pilot.
Start setup →For teams validating approved public and private channel retrieval.
Plan a pilot →For production channel archives, governed retrieval, and deployment review.
Talk to us →Can't find what you're looking for? Send the pilot details through the contact page.
Slackscraper uses Slack API flows with read-only scopes that a workspace admin explicitly approves. The app cannot send messages, modify channels, or impersonate users.
Yes. Retrieval and export use a configured canonical store so searches, deletions, access profiles, and export jobs have a governed source of truth.
Sync stops, Slack access can be revoked, and exported JSONL artifacts remain wherever you wrote them. Data deletion and retention terms are defined during pilot or production setup.
Controlled deployments are scoped with the team. We review configuration, storage, export evidence, and diagnostic redaction before production use.
The system is designed for auditable operations: read-only scopes, tenant boundaries, access profiles, deletion ledgers, audit events, checksummed exports, and evidence bundles. Formal compliance artifacts are handled separately.