Privacy Policy

Effective: 08/19/2026 (v1)

Overview

The identities.dev presence service (the "Bot") is operated by Silver Dev Studios (an unregistered, non-trademarked project) and operated in California, USA. The presence API is self-built for identities.dev — it is not Lanyard, and we are not affiliated with the Lanyard project. This Privacy Policy explains what the Bot collects and how that data is exposed.

What the Bot collects

The Bot connects to the Discord gateway and, for Discord users who share a guild (server) with the Bot, caches in memory:

• Live Discord presence: online status, current activities (including games), and platform information.
• Spotify "now playing" information (song, artist, album art) when Discord reports it.
• Username and avatar (to display in presence blocks and slash-command replies).
• Guild membership (whether a user is in the identities.dev server) for the presence-block membership gate.

Why it collects this

• To power the Site's presence blocks (identity, Spotify, and activity cards).
• To enforce the membership gate before a presence block can be added.
• To answer the Bot's slash commands (/presence, /status, /profiles).

How presence data is exposed

This is important. The presence API is public. It serves live presence over a REST endpoint (GET /v1/users/<id>) and a WebSocket. Anyone who has a user's Discord ID can query that user's live presence, including through third-party applications that use this API independently. The API is offered as a public service; we are not affiliated with, and are not responsible for, third-party uses of the API outside of identities.dev.

If you do not want your presence to be queryable, the most reliable step is to leave the guild the Bot shares with you — the Bot can only see presence for users it shares a guild with. You can also adjust your Discord privacy settings, but note the Bot reads presence through legitimate gateway intents, not by circumventing Discord's controls.

Retention

The Bot keeps presence in memory only. The cache is rebuilt each time the Bot connects to the gateway. Nothing about individual users is persisted to disk.

Slash commands

The Bot's slash commands read the invoking member's Discord ID (and, for /status and /presence, an optional target user ID). The /profiles command also reads the Site's public profiles API to list a user's published profiles. All slash-command replies are ephemeral (visible only to the invoking user).

Third parties

The Bot communicates with Discord (the gateway and REST API) to receive presence and resolve users/members. Subject to Discord's own Privacy Policy. The Bot operates under Discord's Developer Terms of Service and Developer Policy: it requests only the gateway intents it needs, holds presence data in volatile memory, and does not sell or share Discord end-user data.

Your choices

• Leave the guild — the Bot can only track presence for users it shares a guild with.
• Revoke the Bot — remove the Bot from servers you control, or have a server admin do so.
• Discord privacy settings — adjust presence/visibility in Discord itself.

Age

You must be at least 13 years old, or the minimum age required to use Discord in your country, whichever is higher.

Security

Presence data is held in memory and is only as secure as the infrastructure the Bot runs on. We do not expose the Bot token.

Changes to this policy

We may update this Privacy Policy. The "Effective" date above reflects when it was last revised.

Contact

For questions, email info@identities-dev.com or reach out in the identities.dev Discord server.