Does Discord log device identifiers like MAC addresses or advertising IDs?

Checked on November 26, 2025
Disclaimer: Factually can make mistakes. Please verify important information or breaking news. Learn more.

Executive summary

Discord’s public user-facing settings let you view and manage devices and sessions (showing OS, app/web, location and last-used time) but do not advertise exposure of low-level hardware identifiers like MAC addresses or platform advertising IDs to users; internal logs that include IP and device data exist and are only released under legal process, per available reporting [1] [2]. Coverage in the provided sources is limited on exactly which low-level identifiers Discord stores, and none of the supplied items explicitly say “Discord logs MAC addresses” or “Discord records advertising IDs” (available sources do not mention exact storage of MACs/advertising IDs).

1. What Discord shows you: session lists and device metadata

Discord’s user interface provides an “Active Devices” or “Devices” view that lists where your account is logged in and shows operating system, whether it’s a web or native app, approximate location and last-used time; you can remotely sign out of sessions from that view (TechWiser summary of the feature; Adweek guide on viewing active devices) [1] [3].

2. What Discord keeps internally: IP and “device data” in logs

Independent explainers note that Discord’s internal logs include IP addresses and device data and that such internal records are not publicly exposed except through legal process (for example, in response to law enforcement subpoenas), indicating Discord does record at least some connection- and device-related metadata for operational and security purposes [2].

3. Neither the changelog nor help posts substantiate MAC/advertising-ID logging

The supplied Discord changelog and community help posts included in the search results do not state that Discord records MAC addresses or advertising IDs; the community requests and support threads focus on session history, IPs and the desire for richer login history like lists of IPs or device sessions but do not claim presence of MAC or advertising ID fields [4] [5] [6].

4. Legal and operational limits: third-party incident shows sensitivity of identity data

A 2025 third‑party vendor incident described in reporting highlights that Discord and its vendors sometimes collect personally identifying documents (e.g., uploaded ID images for age verification) and that such sensitive materials can be exposed through vendor breaches — underscoring that Discord and its contractors do hold identity- and device-related data beyond what is visible in user settings [7]. That incident does not say Discord collected MAC addresses or advertising IDs either; it does indicate that platform data flows to vendors and those vendor breaches can leak sensitive information [7].

5. What the available sources explicitly deny or do not mention

The available sources explicitly say internal logs include IP and device data released only under legal process [2], but none of the supplied reporting or help pages explicitly claim Discord stores MAC addresses or advertising IDs, nor do they provide privacy-policy level detail on such low-level identifiers. Therefore, statements that Discord definitely logs MAC addresses or advertising IDs cannot be supported from these items (available sources do not mention MAC addresses or advertising IDs).

6. Reasonable inferences and the limits of those inferences

From the docs and reporting you can infer Discord collects connection metadata (IP, OS, session tokens) for security, fraud prevention, and troubleshooting — standard practice for online services — and that some device metadata is recorded in internal logs [1] [2]. However, whether Discord records hardware MACs or platform advertising IDs is not settled by the supplied sources; those identifiers are often considered more sensitive and are not usually necessary for ordinary session management, but that absence of mention in these sources is not proof Discord never collects them (available sources do not mention whether Discord collects MACs/advertising IDs).

7. What to do if you’re worried about device identifiers

Based on the materials: use the Devices view to review and revoke active sessions [1] [3]; if you need detailed audit records (IP logs/device-level forensic data), the reporting indicates those are internal and typically released only via legal process [2]. For concerns about vendor handling of uploaded ID documents, the third‑party incident suggests limiting sharing of sensitive images and monitoring communications from Discord if you submit identity documents [7].

Conclusion — what reporting supports and what remains unknown

Reporting and help-doc summaries show Discord records session and device metadata and keeps internal logs (including IPs) that are not user‑facing and are controlled for legal disclosure [1] [2]. None of the provided sources state that Discord logs MAC addresses or advertising IDs; the question of whether Discord stores those specific low-level hardware or advertising identifiers is not answered in the current set of sources (available sources do not mention MAC addresses or advertising IDs).

Want to dive deeper?
Does Discord collect MAC addresses or other hardware identifiers when you install or run the app?
What device identifiers (IMEI, MAC, advertising ID, IDFA/GAID) are included in Discord’s privacy policy and telemetry?
How can I check or prevent Discord from accessing my device identifiers on Windows, Android, or iOS?
Do third-party integrations, bots, or embedded web views in Discord expose device identifiers to servers?
Has Discord ever had breaches or disclosures showing collection or misuse of device identifiers?