Unofficial DM Screen Connector Privacy Notice
Effective October 2, 2026
The connector handles selected game-page data only when you request a sync. It transfers that data only to the hosted or native Dungeon Master Campaign Console you are using. It does not collect D&D Beyond or Roll20 credentials, operate an analytics or advertising service, or send game data to the developer for independent use.
Purpose
The connector has one purpose: keeping one Dungeon Master's own tabletop tools in sync. It moves user-requested campaign, character, initiative, inventory, note, homebrew, and dice-roll data between the DM Screen, supported D&D Beyond pages, Roll20, and the local Loremaster's Compass desktop app. It can apply reviewed journal or inventory changes, or create a private D&D Beyond magic item, only after the user chooses the corresponding action.
Data access
- D&D Beyond: the supported character, campaign, monster-browser, collection, or private homebrew editor page URL and identifier plus visible character names, statistics, conditions, inventory, coin containers, equipped or attuned items, campaign rosters, tagged DM notes, and user-entered magic-item builder fields. The encounter catalogue reads only monster names, creature types, Challenge Ratings, source labels, D&D Beyond links, and whether an entry is partnered or subscribed homebrew; it does not copy full creature stat blocks.
- Roll20: visible Turn Order names and initiative values, DM Screen party names and scores that the user explicitly exports into the open Turn Order, plus local Compass dice text that the user asks Roll20 to resolve.
- DM Screen: the requested sync command, its result, and the game data needed to update the active table profile.
The connector does not read or copy passwords, browser-saved credentials, cookies, authentication tokens, payment details, private messages, unrelated browsing history, or content from unsupported websites.
Data handling
- Hosted DM Screen: requested results pass from the connector to the open DM Screen page and may be saved in the user's active DM Screen profile. The hosted console and its infrastructure providers process that profile data only to provide the console.
- Native Windows DM Screen: requested results pass through a relay bound to
127.0.0.1on the same computer and are stored in the user's local profile. - Loremaster's Compass dice: only while a Roll20 chat box is on screen, the connector can poll a local-only Compass relay on
127.0.0.1, ports 21356–21358, and post the dice text the user sees into that chat. This connection cannot leave the device. The connector never reads or writes the clipboard. Roll20 performs the roll natively; the connector does not calculate or invent a result. - Roll20 initiative export: only after the user selects Export PCs, the connector uses Roll20's visible Turn Order controls to add the DM Screen party names and numeric initiative scores. It updates an existing exact-name entry rather than creating a duplicate.
- D&D Beyond updates: approved changes are applied inside the signed-in D&D Beyond page; account credentials remain in Chrome and are never copied to the DM Screen.
- Account-bound catalogue safety: the connector hashes the visible signed-in D&D Beyond account label on this device. The DM Screen stores only that one-way fingerprint for comparison, not the label itself. A positively confirmed change to a different signed-in account clears prior D&D Beyond-derived characters, inventories, catalogues, encounter rosters, initiative imports, and builder history. Failure to reach D&D Beyond or identify an account does not trigger deletion.
- Loremaster's Compass creatures: only when the user sends one, a creature from their Compass catalogue is written into the Roll20 journal as a character sheet and placed on the map, optionally joining the Turn Order. A journal entry the connector did not create is reported and left untouched.
- Spell area effects: only when the user casts from the DM Screen, an area is drawn on the Roll20 map as a token sized from the page grid, using artwork the user selected or the game's own art library. To decide who an effect reaches, the connector reads the positions, sizes and status markers of tokens on the open map; those are used for that evaluation and reported to the console, and the extension keeps no copy.
- Linked tokens: only when the user links them, the connector records which Roll20 tokens travel together, such as a rider and a mount, so moving one moves the others. The link is a list of token identifiers held in the user's console profile.
- Compass preferences: small JSON documents the DM Screen keeps in the Compass through the local relay, holding spell-template and effects settings only. They contain no character or campaign data.
- Turn tracking: while a Roll20 turn tracker is open, the connector can report whose turn it is to the Compass tracker on the same computer, so the two show the same combatant.
The extension itself retains no separate copy after a request completes. DM Screen snapshots and notes remain in the selected hosted or native profile. The connector does not sell or transfer data for independent purposes, use it for advertising or creditworthiness or lending decisions, or allow the developer to read it except with the user's explicit consent for a specific support request, as necessary for security, or as required by law. Its use of information received from supported pages adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
For supported character, campaign, account-check, and catalogue requests, Chrome may load a selected D&D Beyond page in a temporary inactive tab so the connector does not switch away from the user's current page. The temporary tab closes after the request. D&D Beyond writes use the signed-in page workflow and report their verification result in the console.
User control
Chrome displays the requested permissions before installation. On DM Screen load, the connector performs only the account-fingerprint comparison needed to prevent reuse of another D&D Beyond account's cache. Character, campaign, monster, inventory, and homebrew content is otherwise scanned only after the user selects the corresponding control. Each write reports its verification result in the console. Removing or disabling the connector in Chrome immediately ends its access to supported pages.
Independent, unofficial tool
The DM Screen connector and Loremaster's Compass bridge are independent, unofficial tools. They are not affiliated with, endorsed by, or sponsored by Google, D&D Beyond, Wizards of the Coast, Fandom, or Roll20.
Contact
Questions and support requests should be submitted through the distribution page where the Dungeon Master Campaign Console was obtained.