Legal · Discord bot
Nefarious Charting Privacy Policy
Effective September 12, 2026 · Last updated September 19, 2026
This Policy explains what Nefarious Digital doing business as Nefarious stores when we run Nefarious Charting (Nefarious Charting Bot, application id 1519049378466369667). It covers command processing, optional saved features, sharing, and your choices.
Members request market charts with commands such as nf AAPL 1h, nlc SPY, or nfa NVDA. The bot fetches market data and replies with a chart image; fc and !fc remain supported aliases. Optional features include heatmaps, headlines, paper trading, saved layouts, and scheduled posts. Paper accounts, user-supplied layout names, Discord IDs, and chart settings are stored; raw conversations are not archived.
Discord Inc. operates Discord. Their privacy policy applies to that platform. This page covers what we keep on our hosts (including the nefarious-charting stack).
Questions or deletion requests: Business@nefarious.trading.
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.
02Who we are
Controller: Nefarious Digital (Nefarious). Email: Business@nefarious.trading.
The wider site and Discord community are described in the site Privacy Policy. This Policy is only about the charting bot.
03Command text (briefly processed, not archived)
The current implementation enables Discord’s Message Content intent to see ordinary server prefixes like nf, fc, and !fc. When a message arrives, the process reads the first token, and if it matches a command (or the bot is @mentioned) it parses the ticker and timeframe in memory, fetches market data, and sends a PNG. Direct messages sent to the bot are processed by the same handler. Bot mentions and DMs can be read without this privileged intent.
We do not write Discord message bodies to SQLite. There is no table of every command anyone typed. Accessible messages are received and checked; unmatched messages are not acted on. The reviewed handler does not intentionally log raw message bodies, but error diagnostics can include submitted symbols and provider responses. Discord client memory caches may temporarily retain recently received messages.
04What is stored
Always (operator configuration)
- Application credentials and operator settings needed to connect to Discord.
- Server and channel configuration used to route requests and scheduled replies.
Optional SQLite (data/charting.db)
Only if someone uses those features:
- Paper trading — Discord user ID, account creation time, cash, symbol, quantity, average price, and asset type. Checking a portfolio can create an account.
nfresetclears positions and restores cash; it keeps the account and user ID. - Layouts — server ID (or DM channel ID), user-supplied layout name, ticker, interval, and source. Server layouts are shared with other users of that server.
- Schedules — guild id, channel id, time of day, kind (chart/heatmap), ticker or heatmap type, last-run date.
Market caches (not Discord chat)
Option/GEX level JSON and similar files under the bot’s data volume are third-party or computed market numbers used to draw overlays. They are not member messages.
Discord also keeps a copy of the chart image we sent, under Discord’s retention and your channel history.
05What we do not collect
- A long-term archive of command text or other channel messages.
- A persistent archive of DM bodies, voice audio, or online status.
- Server member lists or role graphs (Server Members intent is off).
- Presence or streaming status (Presence intent is off).
- Payment cards, government ids, or health data.
- Advertising cookies or cross-site tracking tied to this bot.
Privileged intents: Message Content: used; Server Members: not used; Presence: not used. Details: Terms, intents and /legal/intents.
06Your choices and channel visibility
Avoid commands and mentions to stop invoking features. There is no per-user exclusion list: accessible messages still reach the client while Message Content is enabled. Server operators can deny View Channel or remove the bot to stop its access. Contact us to delete stored records.
Commands and replies, including portfolio summaries and display names in portfolio replies, are visible to people who can access the channel. Saved layouts are shared within their server. Do not include sensitive personal information in a command or layout name.
07How we use this information
- Render the chart or heatmap you asked for and send it back to the same channel.
- Keep optional paper balances and scheduled posts working.
- Debug failed renders and feed outages.
- Respond to deletion requests.
We do not use Discord data to train machine-learning or AI models, and we do not sell it.
08Retention
- Raw command text: processed in memory, including temporary client caches; no raw-message archive is implemented. Selected fields are retained below.
- Paper accounts / layouts / schedules: retained until removed by an operator or the supported feature controls. There is no automatic 30-day expiry. Resetting a portfolio does not delete its account; contact us for full deletion.
- Market caches and diagnostics: caches may be refreshed or removed during operation. The reviewed code does not establish a fixed expiry for host logs or backups; contact us for the retention applicable to a deletion request.
- Discord copies: until a moderator deletes the message or the platform expires it.
10Third parties
- Discord. Discord Privacy Policy.
- Market data sources used to build candles and headlines (for example exchange public APIs, Yahoo Finance, TradingView-compatible endpoints, Hyperliquid public info). Their terms apply to those feeds.
11Your rights and how to request deletion
Email Business@nefarious.trading with:
- Your Discord user id (and username).
- Whether you want full paper-account deletion, a saved layout/schedule removed, or a posted reply deleted. A portfolio reset alone does not delete the account.
- A message link if you want a specific reply removed.
We may ask for proportionate verification of account ownership or server permissions. We will remove data we control subject to applicable retention obligations and explain any exception. We cannot erase copies independently retained by Discord, other members, or market providers.
If you are in the EEA, UK, or a U.S. state with a comprehensive privacy law, you may also ask for access, correction, or a portable copy of any personal data we hold about you in this bot’s database (typically a Discord id and optional paper positions). We will not discriminate against you for asking. You may complain to your local supervisory authority.
12Children
Discord requires users to meet its minimum age (generally 13+). Nefarious Charting is not directed at children under 13, and our community Terms require 18+ for trading education. If you believe we stored data about a child, contact Business@nefarious.trading and we will delete what we have.
13Changes
We will post updates at this URL and change the “Last updated” date. We will explain material changes to collection, purposes, or sharing before applying them where required by law.
Also see our Nefarious Charting Terms, Privileged intents, Discord intents matrix, Site Privacy Policy, and Site Terms of Service.