What the Slack app can actually see
Not a generic privacy policy — the real mechanics of what happens when you use LucidSpec in Slack, written for the person who has to approve installing it.
Only when you ask
No passive listening, ever
The Slack app never reads your channels in the background. It only ever looks at a message when someone explicitly right-clicks it and chooses "Check readiness."
No standing access to channel history. No monitoring. Nothing happens until a person invokes it on a specific message.
Exactly three permissions
Nothing broader than the job requires
chat:write — lets the app post the readiness result back to you, and post a visible reply if a gap is overridden.
chat:write.public — lets that reply post into a channel even if the app hasn’t been invited to it yet, so overrides stay visible to the team, not silently dropped.
commands — required by Slack’s own permission model for the "Check readiness" message shortcut to appear in the right-click menu at all. No slash commands are built or used.
Sensitive data is masked first
Before anything reaches the AI
Emails, access keys, tokens, and other obvious secrets are automatically masked before the message is sent for analysis — the same masking step the LucidSpec web app already uses.
If a message is flagged as unsafe content, it’s rejected before any AI call happens at all.
What’s stored, and what isn’t
Most checks leave no record
A normal readiness check isn’t stored anywhere by LucidSpec — it’s checked, shown in the popup, and done.
The only thing that gets logged is an explicit override: who marked something ready anyway, what was overridden, and the reason they gave. That record is also posted visibly back to the thread — never a silent, hidden log.
Every claim is grounded
Not a black-box score
The AI can only mark something as present if it can point to the exact sentence in your message that says so. A separate check then confirms that sentence is really there before the result is trusted.
This is checked, not just claimed — disagreements between the AI and a simple keyword check are flagged for a second look instead of silently resolved.
Where this stands today
Installing LucidSpec into a Slack workspace is self-serve: sign in to a LucidSpec account, click “Add to Slack” on the Integrations page, and approve it on Slack's own consent screen — nothing beyond the three permissions above is ever requested. If you'd rather walk through it together first, that's still an option — just ask.
Slash commands and any reading of channel history are not built — the message shortcut described above is the entire surface area today, regardless of which way you install it.
Questions before you install it?
Talk to us directly if you'd like a walkthrough first — or install it yourself in a couple of clicks from the Integrations page.