Help
Help
Help & Security
Privacy and consent
Only display information for users who have explicitly approved sharing via /confirm. Respect /disconnect immediately.
[Overview](./)
This section helps you troubleshoot PresenceKit integrations and correctly handle users' consent and visibility.
Find the right guide
| Topic | Documentation |
|---|---|
| Consent, visibility, and revocation | Privacy & Consent |
| Missing data, installation errors, or connection problems | Troubleshooting |
Before debugging
1. Confirm the user joined the official Discord server and explicitly approved sharing with /confirm.
2. Make sure the Discord ID is numeric and belongs to the person who opted in.
3. Check the result's availability before reading presence or spotify.
4. Treat pending, 404, 429, and 503 as distinct states. Do not mislabel pending as offline.
5. Close unused SSE subscriptions and avoid aggressive retries.
WARNING
Never collect another person's presence without their authorization, publish Discord bot tokens, or infer private account information from API errors.
Frequently asked questions
Why can an approved user still show as pending?
pending indicates the service has no fresh presence snapshot. The account may be approved, but the SDK cannot report a current status yet. Show a waiting state until an update arrives.
Can users revoke access?
Yes. Users can run /disconnect or leave the official server. Applications must respect the resulting unavailable state and should not keep showing stale activity information.
Where can I find method and response details?
Read the API Reference. For a first integration, follow Getting Started.
In this section
Was this page helpful?