Security & Privacy

Slackactivity requests three Slack permissions, and none of them can read a message. It can set your availability, read your own name and read your own email address. That is the entire surface. This page spells out what is stored, what your admin can see, and how to remove all of it.

What it can and cannot access

Slackactivity connects with a user token and no bot token at all. It requests exactly three scopes:

ScopeWhat it allows
users:writeSet your own presence to active or away. This is the entire product.
users:readRead your own profile, so the dashboard can show your name and default your schedule to your Slack timezone.
users:read.emailRead your own email address, used to identify your account across workspaces. Optional — if your workspace withholds it, everything still works.

Cannot read messages

No channels:history, groups:history, im:history or search:read. Message content is unreachable — not withheld by policy, but absent from the grant Slack issued.

Cannot read files or channels

No files:read and no channel listing scopes. Slackactivity does not know what channels you are in, let alone what is in them.

Cannot post as you

No chat:write. It cannot send a message, react, or reply on your behalf in any channel or DM.

Cannot touch other people

Every call is scoped to your own account. It cannot read or change any other member's presence, profile or settings.

What is stored

The honest version, field by field. Everything below exists because a scheduler that runs while you are asleep needs it:

  • Your Slack access token. Required to call Slack on the schedule you set. Revocable by you at any time from Slack's own app settings.
  • Workspace and account identifiers. Your Slack team id, workspace name and your Slack user id, so signing in again reconnects you to the right account.
  • Your email, name and avatar — whatever Slack returns, used to identify your account and show who is signed in.
  • Your schedule. Start hour, end hour, working days and timezone, per workspace.
  • An activity log. One row every 5 minutes per active workspace recording whether the scheduler set you active or away, and any API errors. This is what the charts in your dashboard are built from.

No message content, file content, channel names or other members' data is stored, because none of it is ever received in the first place. Your data is not sold, and it is not shared with advertisers.

How it is protected

Encrypted in transit

All traffic between your browser, our servers and Slack runs over TLS, with HSTS enabled so browsers refuse to downgrade to plain HTTP.

Least-privilege by design

No bot token is requested, so there is no workspace-wide credential to leak. The user token can do exactly the three things listed above and nothing else.

Session cookies

Sign-in uses an HttpOnly, Secure, SameSite cookie that JavaScript cannot read, signed so it cannot be forged or edited client-side.

Dead tokens are dropped

If Slack reports a token as revoked or invalid, that workspace is deactivated automatically and the scheduler stops calling it, rather than retrying a dead credential forever.

Before you connect any presence tool

Worth asking of us and of every alternative. The answers should be easy to find on any tool's own site:

  1. 1. Which exact scopes does it request? Slack shows you this on the authorisation screen. If a presence tool asks for message history, close the tab.
  2. 2. Does it need a bot token? A bot token is a workspace-level credential. Presence automation does not need one — Slackactivity requests none.
  3. 3. Does it install anything? Browser extensions and desktop utilities have far broader reach over your machine than a server-side OAuth integration does.
  4. 4. Can you delete everything yourself? You should not have to email anyone. Deleting a workspace here removes its token and history in one click.
  5. 5. What will your admin see? Assume they can see it, and pick a tool whose permission list you are comfortable explaining.

What your IT department sees

Slackactivity appears in your workspace's installed apps list, attributed to you, with the three scopes above shown next to it. Many organisations require admin approval before a member can authorise any app, in which case you will not be able to connect until an admin says yes.

We think that is the right way round, and it is why the permission set is kept deliberately small and boring. Separately, whether automating your presence is appropriate is a question about your employer's policies rather than about Slack's technical rules — how your employer sees your Slack status covers what is actually visible to them.

Deleting your data

Delete a workspace

One click in the dashboard removes that workspace's token, settings and full activity history. The history is deleted by a database cascade at the same moment, not queued for later.

Revoke from Slack

You can remove Slackactivity from your workspace's app settings at any time. That invalidates the token at Slack's end immediately, independently of anything we do.

Full details are in the privacy policy and terms. If something here is unclear or you need a specific answer for a security review, get in touch.

Security & privacy FAQ

Can Slackactivity read my Slack messages?

No. Reading messages requires scopes such as channels:history, groups:history or search:read. Slackactivity does not request any of them, so the permission simply is not there — this is enforced by Slack, not by our good intentions. You can see the exact list on Slack's authorisation screen before you approve anything, and again afterwards in your workspace's app settings.

What does Slackactivity actually store?

Your Slack access token, your Slack user and team ids, the workspace name, your email and display name if Slack provides them, your schedule (start hour, end hour, working days, timezone), and one small row every 5 minutes recording whether the scheduler set you active or away. That activity log is what powers the charts in your dashboard. No message content is ever received or stored, because we cannot read it.

Why do you store my Slack token at all?

Because the whole product is a scheduler that runs while you are not there. To set your presence at 09:00 on Tuesday, the server needs a credential it can use at 09:00 on Tuesday. Any tool that keeps working with your laptop closed necessarily holds a token — one that claims otherwise is either using a browser extension on your machine or is not being precise. You can revoke it instantly from Slack, without involving us.

Will my IT department or workspace admin see this?

Yes, and you should assume so. Slackactivity appears in your workspace's list of installed and authorised apps, along with the scopes you granted. Depending on your workspace settings, an admin may need to approve it before you can connect at all. We deliberately request the smallest scope set that works so that what an admin sees is as boring as possible.

How do I delete my data?

Deleting a workspace in the dashboard removes its token, its settings and its entire activity history immediately — the history is removed by a database cascade, not a scheduled job. You can also revoke Slackactivity from Slack's own app management screen at any time, which invalidates the token from Slack's side regardless of what we do.

Three permissions. None of them read a thing.

Connect Slack, set your hours, and keep your presence accurate. Free forever, and removable in one click.