Privacy model

• No surveillance stack — no keystroke logging, screen capture, or always-on desktop agents.
• OAuth and app installs — you connect Slack, GitHub, and Jira deliberately; admins choose channels and repos.
• Purpose limitation — data serves team capacity and rhythm visibility inside your org, not ad targeting or resale.
• Transparency — pause states and fair-totals policies are visible, not hidden admin knobs.

WePeople ingests metadata — timestamps, ids, event types, presence state, PR titles as provided by vendor APIs where allowed — not message bodies, blocks, attachments, source code, or file contents.

• Slack — channel and user ids, event subtypes, reaction names, presence. No DM or group-DM content; scopes exclude private message history.
• GitHub — commit shas, PR metadata, review events. No repository file blobs through WePeople.
• Jira — issue keys, transitions, story points. Issue descriptions are not stored for monitoring.
• Developer Ingest — you choose fields in payloads; follow the trust model and avoid sending secrets or PII you do not need.

There is no hidden manager-only ranking view. Individual contributors and leads see the same Monitoring, Reports, and SPACE surfaces — including sort-by-score and team comparisons.

Role differences control who can change settings(integrations, org schedule, billing), not who can see peers’ activity metadata within the org.

Workers can pause contribution tracking for focus time, PTO, or personal boundaries. Paused workers show Monitoring paused on the directory and board — gaps are not silent. See People & profiles.

Admins can pause on behalf of a worker when policy allows; the same visible label applies.

Each integration page in Integrations docs lists exact fields stored. Disconnecting pauses new ingestion but does not silently wipe historical metadata — retention and deletion follow your plan and policy.

Workspace administrators control which Slack channels include the bot and which GitHub repos install the app — minimizing over-collection at the source.

Data ages out per plan retention. Organization deletion triggers org-scoped removal subject to legal holds and backup cycles described in the policy.

Enterprise customers can negotiate DPAs, subprocessors, and residency — contact sales via support.

For collection categories, lawful bases, subprocessors, and data subject requests, read the full Privacy Policy. For security practices and scope boundaries, see Trust model.

Questions about what your org configured (channels, monitored users, retention) are best answered by your workspace Admin — WePeople provides the product; your organization controls connections.