Legal
Privacy Policy
Dark Market Watch is a US-based service for Dark and Darker players. This Policy explains the information used for sign-in, alerts, builds, market research, and service analytics, including records retained after you delete an alert or build from the dashboard.
1. Information We Collect
Discord account information
When you sign in through Discord OAuth, we receive your Discord user ID, username, global display name, and avatar identifier. We may also check server membership and roles available to our Discord bot when these determine access to a feature. Dark Market Watch does not receive or store your Discord password.
Alert information
We store the alert settings you create, including the market source, item, rarity, maximum price where applicable, attribute conditions, socket and gem preferences, enabled status, creation and update information, and the Discord account identifier that owns the alert. Records also identify alerts removed from the dashboard.
Saved character builds
Saved builds are linked to your Discord account and can include the build name, class, race, game mode, gear selections, stat targets, watched gear slots, and related alert settings. We retain build history when a saved build is removed, as explained under Data Retention.
Marketplace and Trade Chat records
We obtain market records from data providers such as DarkerDB. These can include listing and item details, prices, in-game seller or sender names, Trade Chat message text and item links, and timestamps. We store market records for matching, research, and troubleshooting, and display listing or chat information in website features and matching Discord notifications. We may retain the underlying provider records internally as well as the fields shown to users.
Alert review copies
Matching alerts may also be privately copied to the Dark Market Watch service owner for quality review and troubleshooting. The owner copy may include the original recipient's Discord user ID, alert ID and name, matched listing details, requested attributes, socketed gem identifiers, inferred socket confidence, and any uncertainty explanation.
Reported alerts and support information
When you use Report Alert, we process your Discord identity, the complete saved alert settings, enabled status, submission time, and any optional note you enter. Reports are sent privately to the service owner and are rate-limited to reduce abuse. Other feedback or support messages may also include your Discord identity, message, and submission time.
If you rate a delivered match, we store your Discord account ID, vote, the listing and delivery it refers to, and timestamps to evaluate match quality.
Session and technical information
We use authentication cookies and functional browser storage described below. Hosting and security infrastructure may record request information such as IP address, browser or device details, timestamps, requested pages, and error logs. Cloudflare also measures page-load performance, including page addresses, navigation timings, and browser performance measurements.
Service analytics and administration
Alert and build records, including records removed from active use, may be used to understand feature use, evaluate matching and delivery, troubleshoot problems, and improve the service. These records remain associated with their Discord account unless identifying information is separately removed. Internal administration can show member identities with saved or active alert counts. We may also count visits to selected pages using aggregate page and date totals without including Discord identity, cookies, IP address, or browser details in those internal counters.
Billing information
When paid membership is enabled, Stripe processes payment information. Dark Market Watch stores the Discord account linked to the subscription, Stripe customer and subscription identifiers, subscription status, plan, checkout-terms acknowledgement, and billing, cancellation, refund, and support records. We do not store full payment-card numbers.
2. How We Use Information
- authenticate users and associate alerts and saved builds with the correct Discord account;
- check access eligibility when Discord server membership is required;
- compare marketplace listings against saved alert criteria;
- save character builds, manage watched gear slots, and provide market research and Trade Chat features;
- infer whether displayed attributes may come from socketed gems;
- send matching alerts, owner review copies, tests, and reported-alert submissions through Discord;
- operate, secure, debug, evaluate, and improve the service using operational records and retained analytics;
- respond to support, privacy, abuse, and legal requests;
- process paid memberships, manage cancellation, prevent fraud, and respond to payment disputes;
- enforce the Terms of Use and protect users and infrastructure.
3. Third Parties
- Discord provides sign-in, account and membership information, notification delivery, and support communication.
- DarkerDB supplies market and item information. Some item or character artwork is delivered to your browser from its content delivery network.
- Cloudflare provides website delivery, security, and page-load performance measurement.
- Google Fonts supplies font styles and files on pages that use remotely hosted fonts.
- Stripe processes payments and provides the Customer Portal when paid membership is enabled.
- Hosting and storage providers operate the website, databases, bot, backups, and operational logs.
When your browser requests fonts, artwork, scripts, or other resources from a provider, that provider receives the request information needed to serve them, such as your IP address, browser headers, and referring page information subject to your browser's settings. Cloudflare processes performance measurements from its browser beacon; Cloudflare describes that beacon as operating without reading or writing cookies or other stored browser data.
We do not normally send your Discord identity or saved alert criteria to DarkerDB when retrieving the global market feed. Local item and stat snapshots may also be used to avoid fetching the same information for each alert. Third parties process information under their own policies.
4. Cookies and Browser Storage
We use one authentication cookie and temporary cookies during Discord sign-in. These first-party cookies support authentication and security and are not advertising cookies:
sessioncontains signed basic Discord profile, session and activity-time information so your sign-in can continue across service restarts. By default, it is a browser-session cookie: sign-in expires after 30 minutes without activity or eight hours after signing in, whichever comes first. If you select the optional Remember me checkbox beside Sign in with Discord, the cookie is saved for a fixed 30 days from that sign-in instead, without the inactivity limit. The eight-hour maximum and the 30-day remembered deadline do not extend as you use the service.dmw_oauth_<nonce>validates a Discord sign-in attempt and carries your Remember me choice during that attempt. It has a 10-minute lifetime and is removed when the attempt is consumed or expires.
Remember me is off by default. For a default sign-in, loading a visible page or interacting with the site can refresh the inactivity timer; background market polling and other automatic reads do not keep you signed in. Your browser controls when a browser session ends and may restore session cookies when reopening, but the inactivity and maximum limits still apply. Closing a browser window does not guarantee sign-out. Use Log out to end sign-in in the current browser.
Existing sign-ins from an older version may temporarily include a session_data cookie. When a valid older sign-in is migrated, that cookie is removed, the original expiry is preserved or shortened, and Remember me is not enabled automatically.
We also use local browser storage for a guest alert draft during sign-in, saved Builder stat templates, and Live Alerts selections, sound, volume, and update preferences. Live Alerts preferences can be stored under a key containing your Discord account ID. The guest draft is removed after successful restoration. Templates and preferences have no fixed automatic expiry and can remain across visits until changed or cleared. Where session storage is used as a fallback, it lasts for that browser session.
You can remove cookies and local storage through your browser's site-data settings. Removing authentication cookies signs you out of that browser; clearing functional storage removes the preferences or draft saved there. Logging out does not automatically clear all functional browser storage or erase server-side records.
5. Data Retention
Deleting an alert or saved build removes it from active use; it does not erase its stored history. The service marks those records as deleted and stops the related active alerts or build watches. Their settings, associated Discord account ID, and historical information remain stored for service analytics, administration, and troubleshooting. These histories currently have no fixed automatic erasure deadline. Records may be removed through maintenance or separate data handling, including where required by applicable law.
Trade Chat collection uses a seven-day retention window by default. Finalized bot delivery records are normally eligible for cleanup after 30 days. These defaults can differ with service configuration, and deleting a delivery record does not remove a message already sent through Discord.
Match-quality votes remain associated with their Discord account and currently have no fixed automatic erasure deadline.
Owner review copies, reports, support information, operational logs, and backups have separate lifecycles and are not automatically erased by dashboard deletion. They may remain available for investigating matching or delivery problems, operating and evaluating the service, preventing abuse, handling disputes, and meeting legal obligations. There is no single automatic deletion period for all of these records; hosting and communication providers may also apply their own retention settings.
When paid membership is enabled, checkout acknowledgement, subscription, cancellation, refund, and dispute-support records are retained for at least three years after the latest related transaction. They may be retained longer when reasonably needed to resolve a dispute, comply with law, or enforce an agreement.
6. Data Security
We use reasonable technical and organizational safeguards, including signed session cookies, restricted backend access, internal API authentication, and keeping private credentials out of the browser. No system can be guaranteed completely secure.
7. Your Choices and Requests
- Delete individual alerts or saved builds to remove them from active use, with history retained as described above.
- Log out to end sign-in in the current browser, or clear its site data to remove locally saved preferences.
- Revoke Dark Market Watch access through your Discord authorized-app settings.
- Request access, correction, or deletion through support.
For privacy requests, contact [email protected], the Support page, or the Dark Market Watch Discord. We may ask you to verify control of the relevant Discord account before acting on a request.
8. Children
Dark Market Watch is not intended for anyone below the minimum age required to use Discord in their location. We do not knowingly collect information from users who are not permitted to use Discord.
9. International Use
The service and its providers may process information in countries other than your own. Privacy rights and legal requirements may differ by location.
10. Changes to This Policy
We may update this Policy when the service, providers, or legal obligations change. The “Last updated” date will identify the current version.
11. Contact
Billing and support: [email protected]
Privacy requests: [email protected]
Discord support: market.sentinel