Stock Market Replay — Privacy Policy
Last updated: October 10, 2026.
1. Who this policy covers
This Privacy Policy explains what MacIvor Technical LLC, an Ohio limited liability company (“we,” “us”) collects when you use the Stock Market Replay Discord application (“the App”), and when you visit stock-market-replay.com. It doesn’t cover Discord itself, or any other service linked from the App — see §7 for how those fit together.
2. The short version
We built this app to run on as little personal data as possible:
- We don’t know your email, real name, birthdate, or payment details, and we don’t ask for them.
- Everything we store is keyed to your Discord user ID — a number Discord assigns you, not anything you typed in.
- We never sell, rent, or license player data to anyone, for any purpose — not as a hedge, not “for now.” See §8.
- We do track which features and commands get used — including how far you get through the shop (view a badge, buy it) — tied to that same Discord user ID. We look at this in aggregate (which badges draw attention, which features get ignored), never to target you individually, and you can opt out of it entirely. See §3 and §8.
- You can see or delete everything we hold on you at any time with
/my-dataand/forget-me— no need to contact anyone. See §10. - We have no advertising anywhere, in the App or on the website.
- We don’t control Discord or any other vendor’s own use of your data — see §7 for what each vendor sees and whose policy governs it.
3. What we collect
Identifiers
- Your Discord user ID — the primary key for every record about you. Required to track your balance, your history, and your cosmetics across sessions.
- The Discord server (guild) ID of any server the App is added to, and, for a handful of actions (like the “share this result” button), the Discord channel ID a command was run in — so the App knows where to post back to.
Game state
- Your balance, total number of simulated trades run, and the date your account was first seen.
- An internal one-time flag marking whether you’ve been shown a particular onboarding tip. It doesn’t carry any information beyond “shown / not shown.”
Trade and position history
- Simulated positions and Market Option plays you’ve opened: which strategy or ticker, term length, stake or premium, timestamps, and the outcome once it resolves (return, payout).
- A transaction ledger recording each balance change (currently: simulated trade payouts) with a type, amount, and running balance. Once the shop ships, this same ledger will also record Diamond (virtual currency) credits and spending — see §6 for what that will and won’t include.
Cosmetics
- Which Flare (badges, titles) you own, how you got each one (earned in-game, granted, or purchased), and which ones you currently have equipped.
Milestones
- Whether you were the first player ever to reach a specific net-worth threshold (e.g., $2M, $10M, $100M, $1B) — tracked per threshold, since “first” can only ever be claimed once.
Custom content you create
- If you build a custom position, its name and composition are stored, attributed to your Discord user ID so you (and only you, per-server) can reuse it.
Feature and command usage
- Which command, button, or menu screen you used, when, in which server (or in a DM), and whether it succeeded — tied to your Discord user ID. Not part of this category: ticker names, run IDs, and amounts — that detail lives only in the gameplay data above, where it’s needed to run the game.
- Purpose: figuring out what players actually enjoy versus what gets ignored, and measuring product KPIs like shop conversion (how many people who see the shop end up buying something). Analyzed in aggregate, never to single out an individual player.
- Kept as raw per-player data for 90 days, then rolled into day-level aggregates with no player identifiers, by a nightly job.
- Whether you’ve opted out of this tracking, and when — kept even if you otherwise delete your account, so an opt-out can’t be silently undone. See §8 and §10.
- You can turn this off entirely with
/privacy— see §8.
4. What we don’t collect
- No email address, real name, birthdate, or physical address.
- No payment card, bank, or billing details — see §6.
- No IP addresses logged by the App itself (the Discord bot/game). Our infrastructure incidentally sees IP addresses in the ordinary course of serving requests, the way any hosted service’s does — that’s covered in §7, not something we collect ourselves. If the website ever adds analytics (§8), that’s the only place traffic-level data like this would be used, and only in aggregate — never inside the game.
- No message content beyond the actual command and its typed arguments needed to run that command — we don’t log or read general server chat.
- No copy of your Discord avatar, username, or profile — Discord renders that directly; we only ever hold your ID.
5. What other players can see
Everything above is about what we hold privately. Separately — because this is a multiplayer game inside a shared Discord server — some of what you do is visible to other people in that server, not just to us. This is a product of how the game displays itself, not us sharing your data with anyone; nothing here goes beyond what §3 already lists.
- The leaderboard (
/leaderboard) posts publicly to the channel by default, showing your Discord username (rendered live by Discord — we don’t store a copy of it) next to your rank, return, and equipped Flare. - Trade and Market Option results, and your own
/profileview, are private by default — Discord shows them only to you (an ephemeral response, or a direct message once a trade resolves). They’re only seen by anyone else in the server if you click the “Share to channel” button yourself; nothing posts there automatically. - Equipped Flare (your current badge and title) shows alongside your name wherever one of the surfaces above is actually visible to others — the leaderboard, or something you’ve chosen to share.
6. Purchases and payments
Diamonds (the App’s virtual currency, covered in the Terms of Service §5) are bought through Discord’s own in-app purchase flow. That means:
- We never see, receive, or store your payment method. Discord processes the charge under Discord’s own Privacy Policy, and only tells us that an entitlement (a specific Diamond pack) was granted to your Discord user ID.
- What we log on our side is just the resulting credit — an entry in the transaction ledger (§3) tied to your Discord user ID, same as any other balance change. No card number, billing address, or payment details ever pass through our systems, because Discord never sends them to us.
Payouts to the business itself (Discord sending MacIvor Technical LLC its share of App revenue) are a separate banking relationship that doesn’t carry or involve player data.
7. Who sees this data, and whose policy governs it
We don’t control Discord or the vendors we use — each has its own policy for its own systems. Here’s who we use that touches your data, and what they see:
- Discord — has whatever it has about you already, under its own Privacy Policy, independent of anything in this document. We interact with Discord’s API using your Discord user ID and, for server-scoped actions, the server and channel ID a command came from. Purchases and messaging happen through Discord directly.
- Amazon Web Services (AWS) — the App and its database run on AWS, and so do backups and our content assets (badge art, weekly content graphics). Player data lives here. AWS provides the hosting; it doesn’t use your data for its own purposes.
- Cloudflare — serves the marketing/legal website at stock-market-replay.com. Like any host, it generates ordinary web server request logs (e.g., IP address, page requested) when you visit a page. We don’t receive or process those logs ourselves.
None of these relationships involve us selling, licensing, or otherwise handing your data to a vendor for that vendor’s own marketing or resale purposes. They’re infrastructure we pay to run the App, not data buyers.
Where this data is processed, and international players: Discord is used worldwide, and so is the App. Our systems and the commercial infrastructure we use are based in the United States, so your data is processed there even if you’re playing from elsewhere. We make a good-faith effort to honor data protection laws that may apply to players outside the US — for example, GDPR for EU/UK players.
8. Analytics, ads, and tracking
This section covers two different things — product analytics inside the game, and marketing analytics on the website — because they’re different in scope and purpose.
Inside the App (the Discord bot/game): we track feature and command usage, tied to your Discord user ID, as described in §3. The purpose is strictly internal: understanding what players enjoy versus what gets ignored, and measuring specific product KPIs — the leading example being shop conversion, i.e. how many players who see the shop go on to buy something. Shop views count even when nothing is bought: knowing which badges drew the eye tells us whether our pricing is off and what kinds of items to make more or less of.
Usage events are recorded with your Discord user ID (so we can count unique players rather than raw clicks), but we analyze them in aggregate — across all players, or groups of players — not to study or act on any one person. Specifically, we don’t use this data to:
- target you individually with sales offers, reminders, or nudges (for example, pinging you about a badge you looked at but didn’t buy);
- identify high spenders and single them out for extra promotion;
- show different prices or deals to different players.
Shop announcements, featured items, and weekly drops go to everyone the same way. This is first-party data we use ourselves to make the game better; it isn’t advertising, isn’t used to build an ad profile of you, and isn’t shared with any third party for that third party’s own purposes.
Retention: raw, per-player usage events are kept for 90 days. A nightly job then rolls them into day-level aggregates — counts per command per day, and daily/weekly/monthly active-player totals — with no player identifiers, and deletes the underlying per-player rows.
Opting out: /privacy turns usage-analytics tracking off for your account. It’s an ephemeral command showing your current status with one button — “Opt out of usage analytics” or “Turn usage analytics back on” — reversible anytime, works per Discord user ID across every server and in DMs, and doesn’t require a game account. Opting out stops your activity from being recorded or counted in these figures from that moment on. It isn’t retroactive — events already recorded, and any aggregate they’ve fed, aren’t unwound. It has no effect on the core gameplay data in §3 (balance, trades, purchases, Flare) — that keeps running regardless, because the game needs it.
Separately: we also look at aggregate patterns in that core gameplay data itself — trade volumes, popular positions and tickers, economy-wide events. That’s aggregate analysis of the §3 gameplay data already collected to run the game, not a second tracking system, so /privacy doesn’t exclude you from those views — there’s nothing there beyond what §3 already discloses.
On the website: as of the date above, no analytics are running there. We expect to add basic website analytics at some point (e.g., aggregate page views and referral sources) to understand which marketing channels are working. That’s a separate, lower-stakes category than the in-game usage data above — it measures traffic in aggregate rather than tracking identified players — and it’s a different thing from the no-sale commitment below either way. When it happens, we’ll update this policy per §13’s change-notice process and name the tool in §7.
Cookies: neither the App nor the website uses cookies.
Either way: no advertising, no ad network, no data broker relationship, and no plan to add one. We do not sell, rent, or trade player or visitor data to anyone, for any purpose — including the usage data described in this section and in §3.
This isn’t a hedge, and it isn’t “no sale for now.” We’re simply not in the business of selling data, full stop. If that ever changed, we wouldn’t slip it into a routine policy update — we’d say so prominently, in plain language, naming exactly what’s collected and exactly who it goes to, before it happened. Short version: we’d rather not be in that business at all than be in it quietly.
9. How long we keep this
We keep your game data — balance, trade history, transactions, Flare ownership — for as long as your account exists in our database, because the game itself (your balance, your leaderboard history, what you own) depends on it continuously, not just at the moment you use a command. Usage-analytics events follow the shorter retention described in §8 (90 days, then aggregate-only, no per-player rows).
You can delete everything tied to your account at any time with /forget-me — see §10 for exactly what that deletes, what it deliberately doesn’t, and what’s outside its reach entirely (data Discord itself holds, and database backups).
If we ever shut the App down for good: per the Terms of Service, we’ll announce that at least 60 days ahead of time. During that window, /my-data and /forget-me keep working as normal if you want your data before then. After shutdown, we delete all remaining player data within 30 days — there’s no scenario where the database just sits there, running or not, with nobody able to use or remove what’s in it.
10. Your rights and requests
You don’t have to wait on us to see or remove your own data. Both commands below act only on the Discord account that invokes them — Discord already authenticates that for us, so there’s no separate identity-verification step on our end.
/my-data — get a copy of everything we hold about your account, anytime, with no email or identity step beyond running the command yourself.
- Covers: your account and balance, position and Market Option history with results, your full transaction ledger, custom positions you’ve built, Flare and titles (earned or bought), any “first to reach” milestones you hold, your usage-analytics records, and your analytics opt-out setting.
- Delivered as CSV files in a zip, sent by Discord DM (or as a private message only you can see, if your DMs are closed). Large histories are split across several zip files — nothing is truncated or summarized.
- Limited to one export every 5 minutes.
/forget-me — permanently delete your account and everything tied to it.
- Shows you a warning with your actual numbers first — balance, open positions, Flare count — and states plainly that deletion is permanent, that open stakes are lost, and that all Flare and titles are lost, including anything you paid for, with no refund or restoration.
- To confirm, you click a button and then type
DELETEin a pop-up; that confirmation expires after 5 minutes, so a stray click can’t erase an account by accident. - In one step, deletes: your account and balance, all position and Market Option history, the transaction ledger, custom positions, all Flare and titles, and usage-analytics records.
- Immediate and can’t be reversed by us. Playing again afterward starts a brand-new account — there’s no restoring the old one.
What /forget-me deliberately keeps, and why:
- Your analytics opt-out setting — just your user ID and the opt-out timestamp, no activity — so that if you objected to tracking, a later account under the same Discord ID isn’t tracked again by default.
- A “first to reach” milestone record, anonymized — the row stays so the milestone can’t be claimed a second time, but your identifier is removed from it. The title is consumed; you aren’t attached to it anymore.
- Aggregate usage statistics — these never carried a player identifier in the first place, so there’s nothing to remove.
Not covered by either command:
- Data Discord itself holds about you — that’s between you and Discord, under Discord’s own Privacy Policy, not something we can delete.
- Database backups. Deleted data can persist in backups for up to 30 days before aging out.
11. Children’s privacy
We rely on Discord’s own minimum age of 13. We don’t independently verify age, and we don’t knowingly collect data from anyone below that threshold.
12. Security
We take reasonable technical measures to protect the data described above. In keeping with §7’s approach, we don’t publish the specifics of our security setup — detailing exactly how systems are configured would help an attacker more than it helps a player. No method of storage or transmission is perfectly secure, and we can’t guarantee absolute security.
13. Changes to this policy
For a material change — a new category of data we collect, a new way we use it, or a new vendor in §7 that touches player data — we’ll give at least 30 days’ notice before it takes effect, through the App’s own messaging inside Discord: the same mechanism and the same notice period the Terms of Service uses. We don’t collect email addresses for this or any other purpose. A minor change (wording fixes, clarifications that don’t change what’s actually collected or how it’s used) doesn’t require advance notice. Continuing to use the App after a change takes effect means you accept the updated policy.
14. Governing law
This Privacy Policy is governed by the laws of the State of Ohio, without regard to its conflict-of-laws principles.
15. Contact
MacIvor Technical LLC P.O. Box 406, Hilliard, OH 43026 [email protected]
This document covers data and privacy only. For the shop, virtual currency, and account terms, see the Terms of Service.