Privacy Policy

1. Information We Collect

When you install and use Pulser in your Slack workspace, we collect the minimum amount of data necessary to provide our service:

• Slack Workspace Data: We store your Slack workspace ID (Team ID) and the access token Slack issues when your workspace installs Pulser, so that the App can authenticate and communicate with your workspace.
• User Data: We store the Slack User IDs of team members who use the App, are added to a check-in, or are assigned a task in it, to attribute check-in answers and tasks to the correct individuals. For each of them we also store their Pulser role and their notification preferences (such as whether they receive the daily task briefing).
• Cached Slack Profile Details: For these people, we keep a copy of a few details from their Slack profile: their display name (or real name, if no display name is set), their timezone, and whether they are an owner or admin of the Slack workspace. We use the timezone to send scheduled messages, such as the daily task briefing and check-in reminders, at each person's local time. We use the owner/admin status to set each person's initial Pulser role. Pulser has three roles: member, manager, and admin, and a Pulser admin can change a person's role.
• Check-in Answers: We store the answers you submit to Pulser's check-ins, such as your daily standup. Apart from messages that someone in your workspace chooses to convert into a task (described below), Pulser does not read or access any other messages in your Slack channels or direct messages.
• Task Data: When you use Pulser Tasks, we store each task's title, description, status, priority, size, due date, assignees, creator, the Slack channel it belongs to, the reason given if it is marked as blocked, and timestamps (such as when it was created, updated, and completed). We also keep an activity log of changes to each task: who changed what, and when. To keep every copy of a task card up to date, we store references to the Slack messages where Pulser posted that card.
• Messages Converted into Tasks: When someone chooses "Convert to task" on a Slack message, Slack sends that message to Pulser, and its text is copied into the new task along with a link to the original message. Pulser only receives a message this way when a person explicitly chooses to convert it.
• Holidays and Time Off: We store your workspace's holidays and the dates people are out of office (for example, set with /pulser ooo), along with any note added to them.
• Workspace Settings and Admin Change Log: We store your workspace's Pulser settings, such as each check-in's questions, schedule, participants, and channel, and your task briefing and report settings. We also keep a log of administrative changes, such as edits to check-ins, holidays, and people's roles: who made each change, what it was, and when.

2. How We Use Your Information

We use the collected information exclusively to:

• Operate, maintain, and deliver the core functionality of Pulser, including its check-ins and tasks.
• Schedule check-ins and post their reports to your designated Slack channels.
• Show tasks to the people they belong to, keep task cards up to date, and send task notifications, nudges, and the daily task briefing.
• Draft standup answers from your team-visible tasks (see Section 3).
• If your workspace has Pulser's AI features turned on, read task commands, standup answers and tasks with Claude, an AI model made by Anthropic, to structure tasks, suggest tasks, and summarize the week for managers (see Sections 3 and 6).
• Skip check-ins and task briefings on holidays and during people's time off.
• Compute the performance insights described in Section 3.
• Show your workspace's Pulser admins a record of recent changes to its Pulser settings.
• Provide customer support and troubleshoot technical issues.

3. Tasks, Visibility, and Performance Insights

• Private tasks: Tasks created in a private channel or a direct message are private. Inside Pulser (for example, the App Home, the daily briefing, reports, digests, and standup drafts), a private task's title and details are shown only to its creator and its assignees. The task card itself stays in the private channel or direct message where the task was created, so members of that conversation can see it there, like any other Slack message in it. Everyone else, including managers and admins, only sees private tasks as counts in the numbers.
• Standup drafts: When Pulser drafts your standup answers from your task activity, it only uses team-visible tasks, never private ones. The draft is only a starting point: you can edit or remove any part of it before you submit.
• Performance insights: Pulser computes performance metrics for each person from task activity (for example, tasks closed, on-time rate, time to close, and reopened tasks), check-in submissions, and your workspace's holidays and people's time off, so that time off is not counted against anyone. These metrics are shown to the workspace's Pulser managers and admins, and each member can see their own. They are posted to a Slack channel only if your workspace opts in to a weekly channel post. Pulser does not combine them into a single score or rank people. Our team can also see task lists and these reports in our internal admin tools, with private task titles withheld, to operate and support the service.
• Your choices: You can turn off the daily task briefing at any time with /pulser tasks briefing off. Managers can turn off the weekly report DM with /pulser team report off.
• AI features (only where turned on): Pulser's AI features are off unless we turn them on for your workspace, and turning them on or off is recorded in your workspace's admin change log. While they are on, Pulser uses Claude, an AI model made by Anthropic, for three things:
  • When you create a task with /pulser task, the text you typed, your name and timezone, and the names and Slack User IDs of the people Pulser knows in your workspace are sent to Claude, to work out the task's title, assignees, due date, and priority. If it matched someone from a plain name, Pulser asks you to confirm before anyone is assigned.
  • After you submit a standup, your answers and the titles of your open tasks are sent to Claude to find things you said you would do that aren't tasks yet. Pulser offers them to you privately; nothing is created unless you choose to. You can turn these suggestions off with /pulser tasks suggestions off.
  • For the weekly report sent to managers and admins, standup answers from check-ins that post to public channels, the titles of team-visible tasks, and the team's task counts are sent to Claude to write a short summary of the week. Answers from check-ins in private channels and private tasks are never included. The summary is written to describe the work, not to rank or grade people.
• Slack permissions: Pulser Tasks did not add any new Slack permissions (OAuth scopes). It works with the same permissions Pulser already requested when your workspace installed it.

4. Where Your Data Is Stored and How We Protect It

Pulser runs on a single virtual machine hosted by DigitalOcean in its Amsterdam, Netherlands data center (region ams3). That machine runs the App, its PostgreSQL database, and a Redis job queue, so the data described in this policy is stored there.

These are the security measures we have in place today:

• Encryption in transit: This website, Pulser's web reports, and the endpoints Slack connects to are served over HTTPS (TLS) using Let's Encrypt certificates. Plain HTTP requests are redirected to HTTPS.
• Slack access tokens: Your workspace's Slack access token is encrypted by the App with AES-256-GCM before it is stored in our database.
• Our internal admin tools: Passwords for our team's internal admin accounts are hashed with bcrypt, and their two-factor authentication secrets are encrypted.
• Web report sign-in: Sign-in links for the web reports work only once and expire 10 minutes after they are issued, and we store only a hashed form of each link. A web report session lasts 2 hours.

Other data in our database, including check-in answers, task data, and cached Slack profile details, is not encrypted by the App itself.

5. How Long We Keep Your Data

Pulser does not currently delete data automatically, and we have no fixed retention period. We keep check-in answers, task data (including task activity logs), the text and links of messages converted into tasks, holidays and time off, workspace settings, the admin change log, and cached Slack profile details until they are deleted at your request (see Section 8).

Uninstalling Pulser from your Slack workspace does not delete your workspace's data. To have it deleted, contact us.

Some operational data is short-lived: sign-in links for the web reports expire after 10 minutes, and web report sessions last 2 hours. Pulser's schedule of upcoming messages and the entries in its job queue are working data used only to send scheduled messages on time.

We keep backups of the virtual machine that runs Pulser, made and stored by DigitalOcean. Backups are kept for up to four weeks, so data deleted from Pulser remains in existing backups until they expire.

6. Service Providers and Data Sharing

We do not sell, rent, or trade your personal information to third parties. We may share information only if required by law or to protect our legal rights.

Within your Slack workspace, Pulser posts information only where described in this policy: for example, task cards in the conversation where a task lives, digests in the channel your workspace chooses, and the weekly performance post if your workspace turns it on.

These other companies store or receive data when you use Pulser or visit this website:

• DigitalOcean: Hosts the virtual machine that runs Pulser and stores its data (see Section 4).
• Slack: Pulser works through Slack's API. The information described in this policy comes from your Slack workspace, and Pulser posts messages back into it. Slack's handling of the data in your workspace is covered by Slack's own terms and privacy policy.
• Google Fonts: This website and Pulser's web reports load their font from Google Fonts, so Google receives your IP address and the standard information your browser sends with any web request when a page loads.
• Anthropic: Only for workspaces with Pulser's AI features turned on, Pulser sends the data described in Section 3 ("AI features") to Anthropic's API, which runs Claude and returns the result to Pulser. Anthropic processes this data under its commercial terms for API customers.
• Tailwind CSS CDN: This website loads its styling from cdn.tailwindcss.com, so that service receives the same kind of information when a page loads.

We do not use analytics, advertising, or tracking tools on this website or in the App. Apart from Anthropic, for workspaces with AI features turned on, we do not send your data to any AI or large language model (LLM) provider.

7. Cookies

This website does not set any cookies. When a Pulser manager or admin opens the web reports from a link Pulser sends them in Slack, the App sets one essential sign-in cookie, pulser_app, which keeps them signed in. It is HttpOnly (scripts on the page cannot read it) and expires after 2 hours. When someone installs Pulser in a Slack workspace, the App also sets one essential security cookie, pulser_oauth_state, which holds a random value that protects the installation from forged requests. It is HttpOnly, is only sent back to the App's installation page, expires after 10 minutes, and is deleted as soon as Slack sends the person back to Pulser. We do not use cookies for analytics or advertising.

8. Your Rights and Data Deletion

You have the right to request access to or deletion of your data, including your check-in answers, task data, and task activity logs. To make a request, email us at support@afransi.ng. Deletion is handled on request: Pulser does not delete data automatically, and uninstalling Pulser from your Slack workspace does not delete your workspace's data. If you uninstall Pulser, email us to have your workspace's data deleted from our servers.

We will respond to your request within 30 days. Data we delete is removed from our database straight away, and from our backups once they expire (see Section 5).

Messages that Pulser has already posted in your Slack workspace, such as task cards and digests, are stored in Slack as part of your workspace.

9. Contact Us

If you have any questions about this Privacy Policy or wish to request access to or deletion of your data, please contact our Support team via email at support@afransi.ng.

Pulser is operated by Afransi Technologies Limited, registered in Nigeria with the Corporate Affairs Commission (RC 9436620). Registered address: Lagos, Nigeria.