Terms of Service

Agreement

These Terms of Service (“Terms”) govern access to and use of the People web application and related services (the “Service”) operated by the person or entity that deploys this instance (“we,” “us,” or “Operator”). By creating an account or using the Service, you agree to these Terms on behalf of yourself and, if applicable, your organization.

The Service

People provides dashboards and analytics that combine Slack, GitHub, and (when connected) Jira Cloud activity data configured by your organization. Features depend on how the Operator configures integrations, monitored users, channels, and retention settings. The Service is explicitly a metadata-only consumer of Slack data: Slack message content, blocks, attachments, uploaded files, direct messages, and multi-person DMs are never ingested or stored. The Service is provided “as is” and “as available.”

Accounts and responsibilities

You are responsible for maintaining the confidentiality of credentials and for activity under your account. Organization administrators control invitations, roles, and integration settings. You must comply with applicable laws, Slack’s, GitHub’s, and Atlassian’s terms when connecting those products, and your employer’s policies.

Acceptable use

You may not misuse the Service, attempt unauthorized access, probe or scan systems without permission, or use the Service to violate others’ privacy or workplace policies. The Operator may suspend or terminate access for violations or security concerns.

Data and privacy

Processing of personal data is described in our Privacy Policy, including the specific Slack bot token scopes the Service requests and the data each scope enables. In summary: from Slack the Service stores only workspace and channel identifiers, channel names, and metadata-only activity signals (timestamps, channel IDs, user IDs, event subtypes, reaction names, presence states) for users an administrator has explicitly configured as monitored. Slack message content, attachments, files, direct messages, and multi-person DMs are not ingested — the im:history and mpim:history scopes are intentionally not requested.

Where Jira Cloud is used and the deployment stores Atlassian identifiers (such as Jira accountId), the Operator is responsible for keeping Atlassian's required privacy reporting and data lifecycle obligations satisfied (including automated reporting to Atlassian where configured). Retention of activity data follows per-organization settings (default 90 days for event data unless configured otherwise). Integration tokens (Slack bot tokens, GitHub App installation tokens, Jira OAuth tokens) are stored encrypted at rest when APP_ENCRYPTION_KEY is configured. A workspace administrator can disconnect any integration at any time from Settings → Integrations; on disconnect the associated tokens are revoked and integration-scoped records are removed from the organization.

Disclaimer

To the maximum extent permitted by law, the Service is provided without warranties of any kind, express or implied. We do not warrant uninterrupted or error-free operation. Analytics are indicative and may not reflect complete activity.

Limitation of liability

To the maximum extent permitted by law, the Operator and its suppliers shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or loss of profits or data, arising from use of the Service.

Changes

We may update these Terms from time to time by posting a revised version. Continued use after changes constitutes acceptance where permitted by law.

Contact

For questions about these Terms: support@wepeople.app.

Slack Marketplace

If the Service is distributed with Slack, we aim to follow Slack’s security and compliance expectations. See Slack’s Marketplace security guidelines.