Privacy, Consent and Data Handling

[Overview](../) · Help & Security

PresenceKit is designed around explicit opt-in. It helps applications display Discord presence only when the user has agreed to share that information through the official PresenceKit service.

How a user enables sharing

1. Join the official PresenceKit Discord server.

2. Run /confirm and approve the sharing notice.

3. Run /status to check approval status if needed.

4. Run /disconnect to revoke access, or leave the server to end eligibility.

Being a member of the Discord server is not equivalent to consent. Unconfirmed accounts cannot be queried through the official API.

What an approved response may include

• Public-facing Discord profile fields such as display name and avatar.
• Current status and reported device indicators.
• Current games, applications, custom status and Spotify activity.
• Activity timestamps, artwork metadata and other available safe Rich Presence fields.

The API does not provide bot tokens, private messages, raw Gateway session IDs, or Rich Presence join/spectate secrets. Some fields may be absent because Discord does not supply them or because of the user's privacy settings.

Revocation and unavailable states

When sharing ends, PresenceKit stops serving the user's approved presence and removes them from active batch subscriptions. Applications must also stop rendering stale data on revoked, 404, or other terminal unavailability.

A successful response with availability: "pending" means consent is approved but a fresh presence snapshot is not available. It is not an offline signal.

Application developer responsibilities

• Ask users for their numeric Discord IDs only when they want to be displayed.
• Respect /disconnect and avoid retaining stale presence indefinitely.
• Do not build unauthorized user directories or attempt to enumerate consented accounts.
• Consider what visitors, analytics or downstream services can see once data is embedded on a public site.
• Provide appropriate privacy disclosures if your application stores or redistributes retrieved data.

IMPORTANT

Revocation prevents further access through PresenceKit but cannot retroactively delete copies already stored or redistributed by independent applications.

Discord platform terms

Opt-in does not automatically authorize unlimited third-party redistribution. Integrators and maintainers should review Discord Developer Terms and applicable policies before a public launch. Destination-specific authorization may be necessary; a successful SDK test does not establish platform approval.

Read Getting started for the consent flow and API reference for response semantics.