← All bots

Legal · Discord apps · Developer Portal

Nefarious Charting privileged intents

Effective September 12, 2026 · Last updated September 19, 2026

Paste pack for Discord’s Privileged Intent form for Nefarious Charting (application ID 1519049378466369667). The reviewed code enables discord.Intents.default(); intents.message_content = True; intents.guilds = True. This page distinguishes that current configuration from whether Discord will approve the requested access.

Preferred path: migrate prefix commands to slash commands. Discord recommends interaction-based commands when they can provide the same functionality. Bot mentions and DMs already have content-access exceptions. No Server Members or Presence use was found.

01Verified storage and retention status

Bot storage checked September 19, 2026. The inspected bot's persistent data is stored without encryption at rest.

The bot's logs have no configured size or file-count limits. No automatic expiry was established for those logs. Do not select “Yes” for encryption of all stored API data or promise a 30-day deletion limit on the basis of this page.

The retention and deletion rules below describe each data category. A removal request must also address logs and backups containing the requested data. Storage migration, bounded logs and a verified deletion procedure remain required operational work.

02Intent matrix

  • Message Content — currently enabled. Currently enabled for ordinary server messages starting with nf, nlc, nfa, and other supported prefixes. Messages mentioning the bot and direct messages are exceptions that remain readable without this intent. Slash commands are a feasible replacement for these text commands; the current implementation alone does not establish eligibility for approval. Prefer migration and disable Message Content after validating the replacement.
  • Server Members — NO. Nefarious.py never enables intents.members and has no on_member_join / role-sync / member-list code. Manage-Server checks for schedules use permissions on the message author object.
  • Presence — NO. The bot never reads online, idle, DND, or streaming status. intents.presences is not set.

What the gateway is used for

  • Message Content — read ordinary server messages for nf / nlc / nfa and other prefixes; bot mentions and DMs do not require this privileged intent
  • Guilds — guild id for saved layouts and scheduled posts
  • Guild Messages — receive server message events; sending charts instead uses channel permissions such as Send Messages and Attach Files

See Discord’s privileged-intent alternatives guide. A chart image establishes output functionality; it does not establish that broad message access is necessary. Validate any replacement before disabling the current intent.

03What does your application do?

Nefarious Charting provides market charts for the Nefarious Discord community. Members type nf AAPL 1h, nlc SPY, nfa NVDA, or other supported commands, or mention the bot with a request such as chart NVDA 1h. It parses the ticker and settings, fetches market data, and replies with a chart image. nf is the standard chart command; fc and !fc are also supported. Optional features include heatmaps, headlines, paper trading, saved layouts, and administrator-managed scheduled posts. Selected command fields and Discord IDs are retained for those optional features. The bot checks accessible messages for prefixes but does not archive conversations, moderate members, or monitor presence. The current prefix workflow could migrate to slash commands. Charts and paper balances are educational and do not execute real trades.

04Privacy Policy fields

Do you have a public Privacy Policy? Yes
Where is it available? Official Nefarious website (nefarious.trading). Add this URL to the application's Developer Portal settings before submission.
Privacy Policy URL: https://www.nefarious.trading/legal/nefarious-charting/privacy
Terms of Service URL: https://www.nefarious.trading/legal/nefarious-charting/terms

05Message Content — current use and alternatives

Use this factual description if reviewing the current implementation. Resolve the alternative-access question before submitting a request.

The current implementation reads ordinary server messages for explicit prefixes such as nf AAPL 1h, nlc SPY, and nfa NVDA. It parses the requested ticker and settings, fetches market data, and posts a chart. The client currently enables message_content; without it, non-mentioned prefix messages in server channels have unavailable content.

Messages that mention the bot and DMs sent to it remain readable under Discord's exceptions. The bot already supports a mention-based input path. Chart requests, paper trading, layouts, and schedules could also migrate to slash commands; there is no verified technical barrier to that migration. We therefore do not claim that prefix compatibility alone merits approval. This describes the existing implementation for review, and any request must explain a genuine need beyond a preference for prefixes.

The bot does not perform moderation or presence monitoring. It does not archive raw messages or use them to train AI models. Optional saved layout names and chart settings are retained as structured records.

Can users opt out of message-content tracking?

No per-user Gateway exclusion; feature use is voluntary
Members can avoid invoking commands or mentions, and request deletion of stored feature records. This is not a per-user opt-out from Gateway delivery: while Message Content is enabled, accessible messages reach the process and their first token is checked. Administrators can deny View Channel or remove the bot to stop that access in a channel or server. No individual exclusion list is implemented.

Storing message content off-platform?

Yes — selected command fields; no raw-message archive
Raw server and DM command bodies are parsed in memory and are not intentionally archived. Optional SQLite records retain selected fields derived from commands: user-supplied layout names, ticker symbols, intervals, quantities, and schedules, alongside Discord IDs. Treat those retained fields as off-platform data in the application; do not answer that no message-derived content is stored.

Used to train ML / AI models?

No

06API data and selected command fields stored off-platform

Discord IDs and selected command fields are stored off-platform: Yes; 30 days or less No.

Optional SQLite records can remain longer than 30 days; there is no automatic expiry in the reviewed code. nfreset clears positions and restores cash but keeps the Discord user ID and account record. Full account deletion and saved-layout removal require operator action; administrators can remove schedules. Market candle caches contain market data. Error logs may contain submitted symbols or provider responses, so host log and backup retention must also be checked before submission.

Checked September 19, 2026: the deployed persistent storage is on an unencrypted apps dataset. Container JSON logs have no configured rotation limits. Do not select Yes for encryption of all stored API data until storage and log remediation is verified.

Deletion contact: Business@nefarious.trading.

07Server Members and Presence — do not request

Leave those boxes unchecked. If Discord asks why you do not need them:

Server Members: Nefarious.py never enables intents.members and has no on_member_join / role-sync / member-list code. Manage-Server checks for schedules use permissions on the message author object.

Presence: The bot never reads online, idle, DND, or streaming status. intents.presences is not set.

08Chart output and source links

The linked chart attachment and advanced reply illustrate output from this application. A captured output alone does not prove the triggering command or the need for Message Content. Reviewers may need server access to open Discord links.

Questions: Business@nefarious.trading.

Also see our Terms of Service, Privacy Policy, and All-bot intents matrix.