Tickin for Slack: data access & uninstall
This page states exactly what the Tickin Slack app accesses, what it never accesses, what it stores, and how to remove it. It is tied to the app's real OAuth scopes. For our general policy, see the privacy policy and security overview.
What Tickin accesses, and why
The /tickin commands your team runs
So people can clock in, take breaks, request leave, and check status.
Scope:
commandsMessages the Tickin bot sends
Clock-in confirmations, approval buttons, and reports to the channel an admin picks.
Scope:
chat:write, chat:write.publicBasic Slack profile (name and email)
Only to match a Slack user to the right Tickin account. Email is the matching key.
Scope:
users:read, users:read.emailThe list of public channels
Only so an admin can choose which channel receives notifications and reports.
Scope:
channels:read
What Tickin never does
- Read your private conversations, DMs, or channel message history.
- Monitor, log, or store the messages your team sends to each other.
- Track activity unrelated to attendance, leave, and overtime.
- Access your files.
What Tickin stores from Slack
Only what's needed to run the integration:
- Your Slack workspace ID (to route requests to the right Tickin workspace).
- The bot token, encrypted at rest with AES-256-GCM.
- A mapping of each Slack user to their Tickin account (by email).
How to uninstall
Two ways, either works:
- From Slack: open your Slack app settings, find Tickin under installed apps, and remove it.
- From Tickin: go to Settings → Integrations and click Disconnect.
What happens when you uninstall
- All Slack messages and scheduled notifications stop immediately.
- The integration is marked disconnected and the bot token is invalidated.
- Your Tickin HR data (attendance, leave, payroll) is untouched — it lives in your Tickin workspace, not in Slack.
- You can reconnect at any time; reconnecting re-authorizes and restores your channel choices.
Questions about data or removal? Contact us or email support@tickin.pro.