Privacy policy
Last updated October 30, 2026
DX Master ("DXM", "the app") is a tabletop role-playing companion: it holds character sheets, lets a Game Master ("GM" or "DM") run a campaign, and lets players join a DM's campaign over the local network or, with an invite link, over the internet.
The short version
- We collect almost nothing. DX Master has no accounts, no sign-in, no analytics, no advertising, and no crash-reporting service. The one thing the developer keeps is for playing over the internet: the relay's records of a GM's hosting subscription and of the tables it opens, with store IDs only hashed ("What the relay keeps", section 2). The relay can't read what passes through it and keeps no log of it. The only other things the developer receives are a feedback report or a Report that you choose to create and send yourself (section 3).
- Your characters, campaigns, and settings stay on your device.
- Buying a content pack goes through your app store. Google Play, the Apple App Store or the Microsoft Store takes the payment and knows your store account. The app keeps only a record of which packs it holds, on your device. There is no server for it and no account of ours (section 6).
- Free packs come from GitHub, and only when you open the Rules Store. Opening the Rules Store in Settings (the first time each time the app runs), or tapping Refresh, Free or Update there, downloads files from DX Master's public repository on GitHub. GitHub (Microsoft) sees your device's IP address and which files it downloads; nothing about you is sent (section 6).
- When you play with others on your local network, data goes directly between your devices, never through the developer or any cloud service. The one exception is a check you start yourself: Settings > Network can ping a public internet address to test your connection (section 6).
- Playing over the internet goes through DX Master's relay. A GM can turn on Play over the internet for a campaign, and players anywhere join with its invite link. Then what their devices send each other passes through the relay at relay.dexxfm.app, which the developer runs on Cloudflare - sealed, so neither the relay nor Cloudflare can read it. They see table ids, network addresses and the sizes and times of requests; never names, sheets, rolls, messages, content files or the invite link's secret ("Playing over the internet", section 2).
- Some of that local traffic is not encrypted (a campaign's listing and a join request). What a DM shares with players - including the content files a campaign hands its table - and the character sheet a player sends the GM once admitted, are encrypted. A GM whose campaign you join can read your whole character sheet, and keeps a copy on their device. The details are below, so you can decide what you're comfortable sharing and on which network.
1. What is stored on your device
DX Master stores the following in the app's private storage on your device (or, on Windows, in a .dxmaster folder in your user profile):
| What | Examples |
|---|---|
| Characters | Name, ruleset, ability scores and every other field on the sheet, the feats, modifiers and debuffs on the character (including the ones a GM has applied to it, which are removed when the character leaves that campaign), what the character carries (each item as it was when it was added - its name, description, properties and modifiers, never a GM's private notes - with how many, how many of its charges have been spent, and whether it is stowed, equipped or attuned), and - for a character that has joined a campaign - that campaign's name and session code, the DM's network address, the campaign's session key, and a second key shared only with that GM, and the journal entries that GM has shared with the players, kept to read offline, which power sets that campaign plays with (their IDs), what that campaign lets its players look up in the Reference (the GM's setting, which item sets and bestiaries it plays with, and the creatures your party has met as the GM lets you read them - see "Campaign updates" in section 2), and the private messages you've sent that GM with their answers. All of it is removed when the character leaves the campaign or the GM ends it |
| Campaigns and encounters you create as a GM | Names, and each campaign's ruleset, chapters, level range, description and your private GM notes, and which item sets, bestiaries and power sets are attached to it, whether the campaign shares its content with the table, what its players may look up in their Reference - a level for each section, whether formulas and art show, and the entries you set apart - and its Global overrides (line of sight, shared sight, explored areas, looking at another level, how long marks last, whether players measure) (none of these is sent to players, except that content itself when it is shared, the IDs of the power sets it plays with, the Global overrides, and the Reference setting with what it lets players read: see "The campaign listing", "A campaign's content files" and "Campaign updates" in section 2); the campaign's journal: each session's title, date and notes, and the people the party met in it (a name, who they are and notes), and whether you have shared the entry with the players - an entry you haven't shared is never sent to them; which characters are in each encounter, which bestiary creatures are planned as its enemies and how many, which of your maps each encounter is played on and where each of its combatants starts on it (never sent to players); once an encounter runs on its map, the map as played - where each token stands, the fog and the doors as you have played them, what the party (or, with own sight only, each player) has explored, the heights you set for tokens, which levels the party has reached, the lines you drew on it at the table, whether the players are shown the map and which of its layers, and what players may do on it, everyone's and each player's own (only what a player may see of it is sent: see "Campaign updates" in section 2) - while the players' highlights and points, their door requests and each token's trail this turn are kept in memory only, never stored; and - while you run one - its turn order: each combatant's initiative, whose turn it is, the round, each enemy's hit points as you keep them, which of an enemy's facts you have chosen to reveal, and the action an enemy is holding and who it is aimed at, if you readied one |
| Players' characters, if you are a GM | For each player admitted to one of your campaigns: their character's name and ruleset, the whole sheet as it was when it last arrived from their device (every field on it, everything the character carries, including any notes they wrote), and when that was - plus what you have applied to them yourself, which never comes from their device: the effects you've applied (their name, kind, duration and what they change) and every item you have awarded them remotely, as it was when you awarded it, with how it was granted (a reward, or an encounter bonus) and, for a bonus, which of your encounters granted it - and the private messages they have sent you, with your answers - and a value worked out from the key their device was last admitted with, which lets that device back in without asking you (see "Admitting players" in section 2; it opens nothing they sent). Kept so you can read it after they disconnect or you stop broadcasting; removed when you delete the campaign or remove the player, or when their device tells yours they left (see section 2) |
| The table you are hosting, if you are a GM | While one of your campaigns is broadcasting: its session code, the campaign's session key and its number, each player's own key (and, for a player you removed from the table, the key they were admitted with), each join request it has had (the character's ID, name and ruleset, and the temporary public key it was made with), who may join (Ask each time or Anyone with the code), when you last switched to another app and the grace period you had then, what the table has sent players that they haven't answered yet, the IDs of the requests and purchases it has already taken (so one sent again isn't taken twice), and how far it had counted its changes. Kept so that when the system closes the app - or the app is closed while it broadcasts - opening it again takes up the same session: the same code, and your players' devices reconnect without asking you again. It is one file in the app's own storage (on iOS, in the app's Library, not its Documents; on Windows and the Mac, table_session.json in the .dxmaster folder), never in a backup the app makes (Settings > Backups) or in an export, and it is deleted when you stop broadcasting or end the campaign, or when you open the app and that campaign is gone |
| TVs you cast to, if you are a GM | For each LG or Samsung TV you allowed DX Master on (see "Casting to an LG or Samsung TV" in section 2): its name, its kind, its address on your network, the identifiers it announced there (from its AirPlay announcement or its device description), and the key (LG) or token (Samsung) it gave, which lets DX Master open the TV's browser without the TV asking again. It is one file in the app's own storage (on iOS, in the app's Library, not its Documents; on Windows and the Mac, tv_pairings.json in the .dxmaster folder), never in a backup the app makes (Settings > Backups) or in an export. To make a TV ask again, remove DX Master from the TV's own list of connected devices; uninstalling the app removes the file |
| Internet play | As a player, for each character that joined a campaign over the internet: the invite link it joined with (the relay, the table's ID, the link's secret and the fingerprint of the GM's key) - Rejoin uses it - and the ID its device uses at the relay; removed when the character leaves the campaign, or when you Forget it in Settings > Internet play. As a GM: each campaign's invite (the relay, the table's ID, the link's secret, the GM's key pair, when the link was made, and the tables of links you replaced until the relay has closed them) and whether Play over the internet is on for it - never in a campaign's export; and this device's GM key, which every invite from this device names, never in a backup the app makes. Who you blocked: as a player, each GM by the fingerprint of their device's key, with the campaign's name and when; as a GM, each character by its ID, with its name, the campaign and when - kept on this device only, sent to no one, and removed when you unblock them in Settings > Internet play. In a test build, the relay and the host token entered in Settings > Internet play. As a GM with the hosting subscription: the store's latest proof of it - the App Store's signed transaction and renewal info, or Google Play's purchase token - with its plan and when it was bought, and what the relay last said of it (the pass, and until when); kept so that a store that can't be asked for a moment doesn't end your hosting, replaced when the store gives a newer one, and never in a report or a backup the app makes |
| Rulesets | The ruleset files you add, and the rulesets you make or change in Editors > Ruleset, with any pictures in them (art you add in an editor, or that a file carries). A change that does not pass the app's checks yet is kept as an unfinished draft in a folder of its own until it does (it then replaces the installed ruleset) or you discard it |
| Item sets | The item sets you import or make: a name, the ruleset each is for, and every item's description, properties, modifiers, picture (if it has one) and your private GM notes (kept on this device unless you include them in an export; see section 3) |
| Bestiaries | The bestiaries you import: each one's stat-block fields, and every creature's name, description, values, traits, actions and picture (if it has one), and your private GM notes (kept on this device unless you include them in an export; see section 3) |
| Power sets | The power sets you import or make: the ruleset each is for, and every power's name, description, properties, effects and picture (if it has one), and your private GM notes (kept on this device unless you include them in an export; see section 3) |
| Maps | The maps you import, copy or make: each map's name, its grid and scale, its levels with their pictures (if they have them), what is drawn on them - walls (with their colors), doors, stairs, areas, lines and labels - where its fog starts, your GM-only layer and your GM notes on the map and its levels (kept on this device unless you include them in an export; see section 3). A map you link to one of your encounters goes to your players' devices as its players' copy only (see "A campaign's maps" in section 2) |
| Maps from a table, as a player | Each map a campaign's table sent your device (see "A campaign's maps" in section 2): its players' copy - the map's name, its grid and the scale the table plays at, its levels' names and pictures, and where its fog starts - never the GM's notes, GM-only layer or anything drawn on it. Kept for that table, apart from your own maps: it is not in your Rules Manager, your Editors or an export, and it is in the backups the app makes (Settings > Backups) |
| Pictures of creatures your party met | As a player: the picture of each creature your party met in a campaign, as your GM's device sent it while the GM shows art, kept so your Reference shows it offline - each picture alone, with its alt text, never the rest of the bestiary |
| App preferences | Player/GM role, theme, spacing, motion, which tips you've seen, how you've arranged your sheet's cards, what you looked up last in each campaign's Reference, as a GM how long the table waits when you switch apps and whether the screen stays awake while you broadcast, the content you hold by purchase (for each file of a pack you bought: the pack's product ID, the store it was bought through, and that store's proof of the purchase - Google Play's purchase token, the App Store's transaction ID, the Microsoft Store add-on's Store ID), which free packs you got and their versions (so the app can offer an update), and the reference of your last feedback report |
| Content packs you bought | The pack's ruleset, power sets, item sets and bestiaries, installed from the copy inside the app when your store says your account holds the pack, and locked against editing, removal and export |
| Free packs you got | The pack's ruleset, power sets, item sets and bestiaries, downloaded from GitHub when you got or updated the pack and installed like files you import: you can edit, duplicate, share and remove them |
| App logs | A record of what the app did, for troubleshooting: when it started, broadcasts and discovery results, join attempts, which content files a campaign shared or a device fetched (their names and versions, never their contents), campaign polls, whether a character's sheet was sent to a GM, on a GM's device the kind of each request a player made on the map at the table and what came of it (with that character's ID, never where), errors, and crash reports. It holds technical details (network addresses, the names of the TVs and other displays found, session codes, error messages) and no character contents. Daily logs are deleted after 7 days; the poll log is size-capped; only the 20 newest crash reports are kept |
The developer never receives this data, apart from the store's proof a GM's device shows the relay to host over the internet ("Playing over the internet", section 2). You control it: delete a character in the app, or uninstall the app, to remove it (on Windows, delete the .dxmaster folder in your user profile).
2. Playing with others: what a DM and players can see
On a local network, DX Master works directly between devices. A GM's device runs a small server while broadcasting a campaign, and players' devices connect to it. The developer is not part of this connection and cannot see it. Over the internet, the same table runs through DX Master's relay: see "Playing over the internet" below.
Finding a campaign
While a GM is broadcasting, their device announces itself on the local network (mDNS / Bonjour, under the service type _dxmaster._tcp) so players' devices can find it automatically. Players can also type the GM's address by hand. The announcement is named after the campaign's session code and includes the port number. Any device on the same network can see it.
What is and isn't protected
| Information | Who can see it | Encrypted in transit? |
|---|---|---|
The campaign listing: session code, campaign name, ruleset, number of players connected, the GM's temporary public key, the name, kind and version of each content file the campaign shares (never the files), for a map, how many levels it has, the scale it plays at, about how big it is and a short fingerprint of each of its pictures (which tells a changed picture from one a device already has, and shows nothing of it), the IDs of the power sets the campaign plays with, the product ID of each store pack it plays (only the ID, never the pack's files: content bought from a store is never shared, so a player's device can offer to buy its own copy),, the version of DX Master's table protocol the GM's app speaks (the network announcement carries it too), and - on a GM's device that has made an invite link - the fingerprint of its GM key, the same k= every invite from that device carries, so a player who blocked that device refuses its campaigns on the network too | Any device on the same network that can reach the GM's device while it is broadcasting | No |
| A campaign's content files, when the GM shares them (on unless switched off in Editors > Campaign > Content): the campaign's ruleset, the power sets it plays with, and the item sets and bestiaries attached to it - each exactly as it would be exported, never the GM's private notes, their pictures only while the GM's Art switch is on, and never content the GM bought - sent one at a time to a device that asks, with no need to be admitted, since a device with no character yet needs the ruleset to make one. What the GM lets players look up decides two of them (Editors > Campaign > Reference): a bestiary is sent only while the Reference's Bestiary shows every creature - by default it shows only the creatures the party has met, and the bestiary itself stays on the GM's device - and an item set only while the Items section shows every item, or a player's device needs it to make a character (an item a class starts with, a starting kit) | The device that asked for it | Yes - AES-256-GCM, sealed to a temporary key that device sends with its request, so other devices on the network cannot read it. Any device that can see the campaign listing can ask for these files |
| A campaign's maps, when the GM shares the campaign's content: each map one of its encounters is played on, as its players' copy - the map's name, its grid and the scale the table plays at, its levels' names and their pictures, and where its fog starts. Never the GM's notes, the GM-only layer, the pictures' file names, or anything drawn on the map (walls, doors, stairs, areas, lines and labels), and never where the encounter's combatants start. The map comes without its pictures, then each picture on its own, and only the ones that device doesn't already hold (an update sends a picture only if it changed). A player's device holds every level's picture, including levels the party hasn't reached yet, and shows none of it that the table doesn't show. A map the GM bought, or the one built into the app, is never sent | The device that asked for it | Yes - as a campaign's content files are. Any device that can see the campaign listing can ask for them |
| A join request: the character's ID and name, its ruleset, a temporary public key created for that join, the version of DX Master's table protocol your app speaks, and - when the character is coming back to a campaign - a proof that your device holds the key it was last admitted with, which gives away nothing of that key and is good only for this request. Your device then asks whether it has been admitted, naming the character's ID and that public key - every 4 seconds while the app is open, whatever screen it shows, until the GM answers or you cancel | The GM's device, and anyone able to observe traffic on the local network | No |
| Delivery of the campaign key and of your own player key to a player the GM has admitted | Only that player | Yes - sealed to that player's temporary key |
| Leaving a campaign: your character's ID, as proof that it is your device asking to take your character out | The GM's device | Yes - sealed with the key only you and the GM hold; the GM's device takes a leave only when it opens with that key |
| Campaign updates, which a player's device keeps asking for while the app is open - it keeps one request open to the GM's device, which answers it as soon as anything changes (or after about 20 seconds with nothing new), and the device asks again at once; a GM's device that does not hold requests is asked every 4 seconds instead: the campaign's name, the current and completed chapter names, house rules, the IDs of the power sets it plays with, a number that tells your device the GM has pressed Update now (Sync all), whether the GM has ended the campaign, the party - each player's character name, level, hit points and armor class, as read from the copies of their sheets the GM's device holds, kept current without waiting for a Publish - and the encounter the GM is running, once they press Publish (or press Next turn): the round, whose turn it is, and everyone in the turn order (the party's character names, IDs and each one's initiative, the enemies' names and initiative, how hurt each enemy looks: unharmed, bloodied or down, whether it is holding an action - never which - and what it looks like at a glance, such as "Beast ยท Large", from its bestiary entry). Of an enemy, only the facts the GM has revealed are in it - armor class, exact hit points, traits, damage rolls - and the rest is not sent at all - and the effects the GM has applied to players: for each player who has any, that character's ID and each effect's name, kind, duration and what it changes - and the journal entries the GM has shared: each one's title, date, notes and the people met in it (never an entry the GM keeps to themselves) - and what players may look up in their Reference: the GM's setting for each section, the IDs of the item sets and bestiaries the campaign plays with, and - unless the Bestiary shows every creature - which of the ruleset's conditions its creatures put on (their IDs, never which creature) and only the creatures the party has met or the GM shows: each one's name, its description, the facts the party has learned of it and, where the GM shows its full stats, its stat block, never the GM's private notes and never a creature the party hasn't met. With the Bestiary hidden, no creature at all: outside the encounter the GM is running, players are sent nothing of the GM's creatures, not even what earlier fights revealed - and the campaign's Global overrides (line of sight, shared sight, explored areas, looking at another level, how long marks last, whether players measure) - and your own copy of the map the GM shows while an encounter runs on it, made for your character alone: the map's name and version and the encounter's name, which levels the party has reached (their IDs), your own level and - while the House rules let you look - each other level a party member stands on (never another), what you know of each (what the GM revealed and, while line of sight is on, what is in sight - the party's, or with own sight only your token's alone - and what was explored, with the shape of what is in sight now), what is drawn on them where it touches a cell you know - walls, doors and whether they are open, which doors are in sight, stairs, areas, lines and labels - and the lines the GM drew at the table, the party's tokens on those levels and the enemies the GM hasn't hidden that are in sight on your own level (each one's name and where it stands, whether it is out of the fight, where it moved from this turn, and which party members see it, by character ID; with line of sight off, an enemy on a revealed cell), the players' highlights with each one's character name, the players' requests to open or shut a door with their character names, what players may do on the map (everyone's, and a player's own by their character ID), and the GM's device's clock, which marks fade by. Never the GM's notes, the GM-only layer, anything under the fog, an enemy out of sight or the GM hides, an enemy on a level you only look at, or a player's point (a point goes to the GM alone). Your copy of the map is sealed with the key only you and the GM hold, inside the update: another player's device can't read it | The GM and admitted players only | Yes - AES-256-GCM with a key generated fresh each time the GM starts broadcasting. Every admitted player's device holds that key, so it can read all of these updates - the party and the effects applied to any player - though it acts only on its own character's. Beside each update, unencrypted, is the number of changes the GM's device has counted so far, which your device uses to tell a new update from an old one; it is sealed with the update, so it can't be changed |
| Whether the GM stepped away (in each campaign update): when the GM switches to another app on a phone or tablet, how long the table waits for them (the GM's grace period: 5, 10 or 15 minutes), how long they have been away, and - once the wait is up - that the table is on standby. Lengths of time only, never what the GM is doing or which app they switched to | The GM and admitted players only | Yes - inside the campaign update, as above |
| Your character sheet, sent by a player's device to the GM's: the whole character - every field on it, everything it carries, including any free-text notes and the private messages you've written the GM - when you join, whenever it changes, every 15 seconds while the app is open, and when the GM presses Sync all. It leaves out the campaign key, your player key, and the GM's address | The GM's device only | Yes - AES-256-GCM with a key only that player and the GM hold. Other admitted players cannot read it |
| Your own award inbox, which your device asks for on the same schedule as campaign updates: any item the GM has awarded you remotely - its name, description, properties and modifiers (never a GM's private notes), whether it's a reward or an encounter bonus and, for a bonus, which encounter granted it - and the ids of any of those you already hold that the GM has since taken back, because the encounter that granted them finished - and what the table sent you (see the next row): another player's power or item used on you, until you accept or decline it, and damage or healing the GM sent you, until your device has applied it - and the GM's answers to your private messages, until your sheet shows your device has them - and the campaign key the campaign updates are sealed with now, and its number (see "The campaign key and your player key are temporary" below). Once the GM has removed you from the table, your inbox holds only that: that you're no longer at it | You only, not other admitted players | Yes - the same private key your device and the GM's share for sending your sheet, used the other way; every admitted player's device holds the shared campaign key, but only yours can open this. It carries the same unencrypted count of changes as the campaign updates |
| A picture of a creature your party met, when the GM's Bestiary shows only the creatures met and the GM's Art switch is on: the campaign updates name each met creature's picture, and your device asks for each one it doesn't have, once - the picture alone (its image, size, alt text and credit), never the rest of the bestiary | That player's device | Yes - AES-256-GCM with a key only that player and the GM hold, as the award inbox is. Only an admitted player's device can ask for one |
| A power or an item used on someone else at the table, when you pick another player or an enemy as its target: your character's name, the power's or item's name, what it does as your device worked it out (dice already rolled, amounts, conditions and the DC to resist them), who it is for (their character ID, and in an encounter the turn-order IDs of you and of them), and an ID for the request. The GM's own damage or healing for a player is sent the same way. Your device then says in the sheet it sends the GM which of these it has accepted or declined | The GM's device. One aimed at another player is passed on to that player's own inbox, and held on the GM's device only until their sheet shows they answered it, and only while the GM is broadcasting. One aimed at an enemy stays with the GM, kept with their encounter | Yes - sent to the GM's device with the key only you and the GM hold; passed on in the other player's inbox, sealed with the key only they and the GM hold. Other admitted players cannot read it |
| What you do on the map at the table: a move of your token, a highlight, a point, asking to open or shut a door, or clearing a highlight of yours - your character's ID, what kind it is, the level, the cells, the door's ID, whether you keep a highlight, and an ID for the request; the GM's device answers what came of it (made, asked of the GM, turned down and why in a word, or no map) | The GM's device, which decides it by the GM's permissions. What it makes is then in the campaign updates as the map now stands - a highlight with your character's name, seen by every player until it fades or is cleared; a point is seen by the GM alone | Yes - sent with the key only you and the GM hold, and answered the same way. Other admitted players cannot read it |
Things worth knowing:
- What the GM learns about a player: before being admitted, only what's in the join request - the character's ID, name, and ruleset. Once admitted, the whole character sheet, including free-text notes, and every change to it while your app is open. Joining is what shares it: the join screen lists what will be sent before you join, and the Campaign tab says so for as long as it is being sent. Nothing is sent for a character that is not in a campaign.
- What the GM's device keeps: the latest copy of each player's character, and when it arrived, in the app's private storage. It stays after the player disconnects or the GM stops broadcasting - so the GM can read it between sessions - and is removed when the GM deletes the campaign or removes the player, or when the player leaves while the GM's device can hear it (see "Leaving and ending"). It is never sent anywhere else. It is held by the GM, not the developer: ask them to delete it if you want it gone, and note that deleting your character, or leaving while the GM isn't broadcasting, does not reach into their device.
- Leaving and ending. A player can leave a campaign from the Campaign tab, and a GM can end one while broadcasting; either sends the character back to not being in a campaign, and your device stops sending its sheet. Leaving also tells the GM's device, when it can be reached, which then forgets its record of you - your sheet, what it applied and awarded, and your messages. Only your own device can ask for that: the request is sealed with the key only you and the GM hold, so nobody else who knows your character's ID can take you out. Ending is announced through the campaign updates above, so only players connected at the time are told - one whose app is closed or away has to leave themselves. Ending removes nothing from the GM's device: the copies of players' characters stay until the GM deletes the campaign.
- Private messages to the GM: what you write the GM from the Campaign tab (a question or a request) goes only to the GM, inside the sheet your device sends them, and the answer comes back only in your own inbox - both sealed with the key only you and the GM hold. Neither is ever in the campaign updates every player reads, and no other player's device can open either. A message written while the GM can't be reached waits on your device and goes with the next sheet it sends. Both ends keep the conversation with the campaign; leaving the campaign removes it from your device, and from the GM's when their device hears you left.
- What players learn about each other: never each other's sheets, never each other's private messages to the GM, and never what the GM has awarded another player, or applied to them - your own award inbox and the campaign's shared updates use different keys precisely so that a device that can read the party list and applied effects still cannot open another player's awards. What they see is the party list the GM's device keeps current - each character's name, level, hit points and armor class, as of the sheets the GM last received - and, in a published encounter, the party's IDs and initiative numbers. The action a player readies in an encounter stays on their own device: it is neither stored nor sent. A power or an item one player uses on another is the exception: the player it is used on sees the user's character name and what it does, so they can accept or decline it. If a later version shows more of party members' status to each other, this policy will be updated first.
- What a GM shares with the table: with "Share content with players" on, the campaign's ruleset and power sets go to any device on the network that asks while the GM is broadcasting - so a player can get the game they need before joining - and so do its item sets and bestiaries, as far as the campaign's Reference setting allows (see "A campaign's content files" above). A bestiary holds every creature's full stat block, including what the GM has not revealed in play, so it goes only while the GM lets players see every creature; otherwise players get only the creatures they have met, through the campaign updates that only admitted players can read - and with the Bestiary hidden, none at all, not even what fights revealed (only the encounter they are in shows its enemies, as the GM reveals them). The files' pictures go only while the GM's Art switch is on (Editors > Campaign > Reference): with it off, each file goes without its pictures, as it goes without GM notes. The campaign updates never carry pictures: while the switch is on, they name the picture of each creature the party met, and a player's device asks for each one on its own. A section the GM hides that a player's sheet still needs (the rules, the powers, an item set a character is made with) is still sent, and only hidden in the player's Reference. On a player's device, a file is checked the same way as one imported from a file, and installed only after its player reviews it and presses Install; nothing is installed on its own.
- A file can't be taken back: a file a player installed from a GM's table stays on their device when the GM later hides it - it may also be theirs for another campaign, or one they run themselves. From then on their Reference shows only what the GM's setting allows; the file itself is theirs to delete (Settings > Rules Manager).
- The GM's private notes on powers, items and creatures are never in a file the table is sent, a campaign update, an award or the store, and a player's Reference never shows GM notes, whatever a file on their device holds.
- Admitting players: the GM chooses either to approve each player individually ("Ask each time") or to admit anyone who requests to join ("Anyone with the code"). Because the session code is visible to any device on the network (see the first row of the table), "Anyone with the code" effectively means anyone on the same network. Use "Ask each time" on networks you don't trust.
- Coming back to a campaign. A character the campaign already holds is let back in without asking the GM only when its device proves it holds the key that character was last admitted with - the device it was played on, or a copy of it. Any other request for that character waits for the GM, even with "Anyone with the code", and the GM's screen says it couldn't prove it is the same player. Such a request never pushes out the player who is in: only the GM can let it take the character over.
- Every encrypted message is sealed for where it belongs: its kind, the session, the character it is for, and - for campaign updates and your inbox - the count of changes. One recorded on the network can't be played back to your device once it has heard a newer one, or passed off as another kind of message or as another player's, and a store purchase or a power used on someone is taken once however often it arrives.
- The campaign key and your player key are temporary. New ones are generated every time a GM starts broadcasting, and a new player key each time a player is admitted; they are discarded when the GM stops. A new campaign key is also made each time someone leaves the table - the GM removes or blocks a player, or a player leaves - and each player still at the table receives it in their own award inbox, sealed with their player key, so a device that left can't read the campaign updates from then on. The campaign updates carry the key's number unencrypted, which tells a device only to ask for the new one. The GM's device keeps, for the rest of that session, the player key of each player it removed, only to tell that player's device it's no longer at the table. A player's device keeps its copies, along with the GM's address, with the character so the Campaign tab can keep updating and the sheet can keep being sent - but they stop working once the GM ends that session. Deleting the character removes them. The GM's device keeps, with its record of each player, a value worked out from that player's key, so the player's device can prove it is them when they come back; it can't open anything the player sent.
- Few identity checks. The encryption protects the campaign updates from people who are not in the campaign; it does not prove who a GM or a new player really is - only that a returning character's device holds the key it was last admitted with. A device on the same network that intercepts the very first exchange could impersonate a GM, and so receive what players send. Only play on networks you trust, and don't put information in a campaign that you couldn't tolerate the network's other users seeing. Over the internet, the invite link names the GM's key, so a player's device refuses anyone else who answers as that GM.
Casting the encounter to a display
As a GM you can cast the running encounter to a display: a TV or monitor plugged into your device, a wireless display your system joins (Miracast, Smart View, AirPlay), a Chromecast, Google TV or Nest Hub on your network, or an LG or Samsung TV on your network (see "Casting to an LG or Samsung TV" below).
- What a display gets is only what your players see: the turn order, the round, and what you have revealed. Enemies you hide, unrevealed facts and your GM notes never reach it. A Chromecast gets it straight from your device over your local network, encrypted (TLS), through DX Master's own code on every platform: the app contains no Google Cast library or SDK, and sends Google nothing. One that can't run DX Master's own receiver shows a picture of it, which your device serves on your local network only (never to an address outside it).
- The Chromecast's own page. The Chromecast loads DX Master's receiver, a web page, from
cast.dexxfm.app, the developer's site, hosted by Cloudflare. That request comes from the Chromecast, not from your device: Cloudflare sees your network's public IP address, as for any web page. The cast view itself never goes there. The picture's fallback runs on the Chromecast's own photo viewer (Google's Default Media Receiver), which fetches each picture from your device on your local network. - Looking for displays. While the Cast list is open, the app looks for displays on your local network, and checks what would stop it from finding any, so it can say so. Nothing it reads leaves your device:
- On Android, whether a Wi-Fi or wired network is connected, and whether Samsung's Smart View is installed (to open it from the list). Android shows the app only that one app and Android's own Cast settings, nothing else that is installed.
- On iPhone and iPad, whether Local Network is on for DX Master: the app sends one empty, one-byte message to your network's router (its discard port) and reads only whether iOS let it go.
- On a Mac, the same for the Mac's Local Network, with an empty message to your network's own discovery address.
- On Windows, whether your network is set to Public, and - when no display has answered - whether Windows Firewall has a rule letting DX Master hear the displays' answers. It reads these settings and changes nothing; the card that says so opens Windows' own settings.
Casting to an LG or Samsung TV
A GM can cast to an LG (webOS) or Samsung (Tizen) TV from Cast. The GM's device and the TV talk directly over the local network; the developer, LG and Samsung are not part of it.
- Finding TVs. While the Cast list is open, the GM's device asks the local network for LG and Samsung TVs (SSDP; on an iPhone or iPad only once Apple allows the app to), and on every platform it listens for the TVs' AirPlay announcements (mDNS / Bonjour,
_airplay._tcp). From a TV that answers, it reads the TV's name and model, and its device description (a request to the TV on the local network). Nothing about you or your device is announced. - The TV's permission. The first time, the TV asks on its own screen whether to allow DX Master. An LG TV is asked for one permission: to open an app - its web browser - at a web address. A Samsung TV is asked for its remote control channel, under the name "DX Master". The key the TV gives back (LG) or its token (Samsung) is kept on the GM's device (see "TVs you cast to" in section 1), so the next cast doesn't ask again. The connection is encrypted where the TV offers it (TLS, on LG's port 3001 and Samsung's port 8002). A TV makes its own certificate, which nothing can check, so the app accepts the one the TV presents, and only at an address on the local network; an older TV answers on a plain, unencrypted port.
- What the TV gets. The TV's browser opens a page on the GM's device,
http://<the GM's device>:7341/cast/<a random code>. It shows a picture of the cast view, drawn on the GM's device and replaced about once a second while it changes: only what the players see (no enemy the GM hides, no fact the GM hasn't revealed, never the GM's notes). The code is new for each cast (128 random bits); the page answers only devices on the local network, and only for the cast that is showing. When the GM disconnects, the page says the cast ended, an LG TV is asked to close its browser, and nothing more is served. The page and its pictures are plain HTTP, not encrypted: another device on the same network could see the pictures as they pass - what the players see on the TV anyway. - What the TV may keep. Its browser may keep the page's address in its history, as any browser does; the address stops working when the cast ends.
Playing over the internet
A GM can turn on Play over the internet on a campaign's broadcast, and players who aren't on the same network join with the campaign's invite link. Then the GM's device keeps one connection open out to DX Master's relay, relay.dexxfm.app, and the players' devices send it their requests; no one opens a port. The relay is a service the developer runs on Cloudflare (Cloudflare, Inc. hosts it, under its own privacy policy). Players on the GM's network play as before, directly.
- What is sealed. Everything a player's device and the GM's send each other through the relay is sealed (encrypted with AES-256-GCM) with a key made from the invite link's secret, before it leaves the device. Inside, the table works as it does on a local network, with each player's own encryption too. So the relay and Cloudflare cannot read campaign, character or player names, sheets, rolls, messages, the journal, content files, maps or art, or the link's secret, and cannot change what they pass on without the apps refusing it.
- What the relay and Cloudflare see. Table IDs, the network (IP) addresses of the devices, and the sizes and times of requests. When a GM's device opens a table, it also sends its proof that it may host (in a test build, a host token; with the subscription, the store's proof of it) and the fingerprint of the GM's key (the invite link's
k=), so that DX Master can close a table that breaks the Terms, and refuse that GM's new tables, after a Report. The store's proof is, from the App Store, the subscription's latest signed transaction and its renewal info, as Apple signed them (the product, its dates, whether it is a test purchase, and Apple's ID for the subscription - never your name or Apple Account); from Google Play, the purchase's token, which the relay looks up with Google (so Google knows the relay asked about that purchase). Settings > Internet play shows the same proof to the relay to ask what it is worth, without opening a table. - What the relay keeps. For each table: which host opened it and whether it was closed, deleted 90 days after its GM last left. With the subscription: each store proof it has checked - the store, whether it is a subscription or a test purchase's beta pass, the store's environment, the product, until when it is good and when it was checked, with every store ID (Apple's subscription ID, Google's purchase token) only hashed - kept until 90 days after it is good until; each subscriber's one open table while it is open, by an ID of the relay's own (never the table's); and the list of tables, hosts and GM keys DX Master has closed out. What passes through is never stored. The relay keeps no log: its own lines are seen only live, by the developer while debugging, and never hold an address, a whole table ID, a key, a store's proof or anything from a request. Cloudflare's network spans many countries, so these records and what passes through may be handled outside yours. To have your records deleted sooner, see section 8.
- Players never pay. The subscription is for a GM hosting over the internet. Joining a table, over the internet or on your network, and hosting on your network, are free, and a player's device sends no store proof at all.
- The invite link. The part after
#is the link's secret: no browser or app sends it to a server, the relay included. The service you send the link through (a chat app, a text message) can see all of it, the secret too. Anyone with the link can ask to join; the GM admits each player (Ask each time, unless they choose Anyone with the link). New invite link makes a new one, and the old one stops working. Tapping an invite link opens DX Master where it is installed: your phone checks two small files on the relay that name the app, and nothing about you. - Block. A player can leave and block a campaign's GM: their device then refuses the campaigns of that GM's device, by invite link or on their network alike. A GM can remove or decline and block a character: their device then declines it in every campaign it hosts. Both are kept on that device only - nothing goes to the relay or to the person blocked - and undone in Settings > Internet play.
3. Files you import, and the files you can send
Importing a ruleset. Settings > Rules Manager's Import opens your device's own file picker, and the app reads only the files you choose. Before anything is installed the app checks the file, and one that fails the checks is discarded. An installed ruleset is stored in the app's private storage; it is not uploaded anywhere. The one way DX Master sends files between devices is a campaign's content, to a player's device that asks for it while the GM is broadcasting (section 2); it is checked in the same way and installed only when the player presses Install.
Sharing and exporting. The same screen's Share and Export send the installed files you select - rulesets, power sets, item sets, bestiaries and maps - as separate files or one .zip. Your GM notes are left out of every exported file unless you turn on "Include GM notes", which is off each time you export: the notes on powers, items and creatures, and a map's notes, its levels' notes and the labels on its GM-only layer. A map's .dxxm file keeps its pictures and its GM-only layer's walls, doors and areas either way: they are for whoever runs the map. Share opens your device's own share sheet; Export opens your device's own save dialog, or a folder picker for several files (the Windows app has Export only), so you choose where they go; DX Master uploads nothing itself. Files bought from a store and the built-in Template are never shared or exported. A ruleset's .dxxr file holds the ruleset's own definition (its sheet layout, formulas, options and settings) and never your characters, campaigns, or app settings. A copy of a shared or exported file stays in the app's temporary storage until your device clears it.
Making a ruleset. Editors > Ruleset changes a ruleset on your device: its sections, fields and formulas. Nothing is uploaded, and a ruleset you make leaves your device only if you export it, as above. Changes are stored as you make them. One that does not pass the app's checks yet is kept as a draft, separately from the installed ruleset (which keeps building character sheets as it was) until it passes or you discard it.
Item sets. Settings > Rules Manager and Editors > Item work the same way. Importing opens your device's own file picker and reads only the files you choose, checking each before anything is installed. Exporting writes a .dxxi file and hands it to your device's own share sheet or save dialog so you choose where it goes; DX Master uploads nothing itself. An item set holds item names, descriptions, properties and modifiers. The private GM notes you write on an item are left out of an export unless you turn on "Include GM notes" (off each time you export): otherwise they stay on your device. A copy of the exported file stays in the app's temporary storage until your device clears it. Editors > Power exports a power set the same way, with the same switch for the notes on its powers.
Network details report. Settings > Network has a "Send all network details" button. When you tap it, the app writes a plain-text file describing your connection and opens your device's own share sheet (on Windows, a save dialog) so you choose where it goes - a message to whoever is helping you, for example. The app itself uploads nothing. The file contains: the app version, your device model and OS version, whether you're on Wi-Fi and its band, channel, signal strength and speed, your device's local network addresses (IP address, subnet, router, DNS servers, IPv6), whether a VPN is active, the result of your last connection test, and - if you're a GM broadcasting - your session code and address. It does not contain character, campaign, or ruleset data. Android also hides the Wi-Fi network's name from apps without location access, which DX Master does not request, so the name is not included. A copy of the file stays in the app's temporary storage until your device clears it. Anyone you send it to will see those addresses, so treat it like any other network information you share.
Bestiaries. Settings > Rules Manager works the same way for them. Importing opens your device's own file picker and reads only the files you choose, checking each before anything is installed. Exporting writes a .dxxb file and hands it to your device's own share sheet or save dialog so you choose where it goes; DX Master uploads nothing itself. A bestiary holds its own stat-block fields and its creatures' names, descriptions, values, traits and actions. The private GM notes you write on a creature are left out of an export unless you turn on "Include GM notes" (off each time you export): otherwise they stay on your device. A copy of the exported file stays in the app's temporary storage until your device clears it.
Campaigns. Editors > Campaign can export a campaign and import one, in the same way. Exporting writes a .dxxc file and opens your device's own share sheet (on Windows, a save dialog) so you choose where it goes; DX Master uploads nothing itself.
- What the file holds: the campaign, its chapters, store listings and starting kit; the journal entries you've shared with the players; its encounters as they were before they were run; and the content files it uses (its ruleset, the power sets it plays with, and its item sets and bestiaries), each as it would export on its own - with their pictures, unless you turn off "Include art" when you export.
- What it never holds: the campaign's players or their characters, what its table learned of the creatures, or content bought for your device.
- GM notes: your campaign notes, the journal entries you haven't shared and the GM notes in its content files are left out unless you turn on "Include GM notes" when you export (off each time you export).
- Importing opens your device's own file picker and reads only the one file you choose. The content it carries is checked as a file of its own would be, and installed only if you pick it. A copy of an exported file stays in the app's temporary storage until your device clears it.
Feedback report. Settings > Feedback zips what the app has recorded so you can send it to the developer. The screen lists exactly what is inside, with sizes, before anything is made: the app log (last 7 days), the campaign poll log, crash reports, a device and network snapshot (the same details as the network report above), a snapshot of your ruleset and settings choices (which rulesets are installed, your role, theme and spacing, and which rulesets' sheet cards you've rearranged, not the rulesets' content), and whatever you type in the "what is wrong" box and the optional reply address. Character sheets are left out unless you switch "Character sheet data" on. No part of the report holds a key or a secret, an invite link's included: the keys and links that let a character into its campaign are taken out of its sheet first, and wherever one was, the report says "(secret removed)". The app then opens your device's share sheet (on Windows, a save dialog) with the zip attached and, where the platform allows it, the developer's address (dexxfm@outlook.com) filled in. You choose whether and how to send it; DX Master uploads nothing itself. If you send it by email, your mail provider and the recipient's handle it under their own policies, and the developer will use it only to look into the problem you describe.
A Report. Over the internet, a player can report the table they play at, and a GM a player at theirs (Report to DX Master). It makes one zip: report.txt, with the table's ID, the campaign's name - on a player's report, the fingerprint of the GM's key; on a GM's, the player's character name as the sheet gives it - the reason picked and what you write. Under "Also include", each part stays out until you turn it on, with its size shown: the network details (as above, with the relay connection's state - they hold IP addresses), the app log and the poll log, the crash reports, and the ruleset and settings snapshot. It never holds a character sheet, a roll, a message, a key or the invite link's secret. The app opens your device's share sheet with the zip, addressed to dexxfm@outlook.com where the platform allows it; you choose whether and how to send it, and DX Master uploads nothing itself. The developer uses it to look into what you report, and may close that table at the relay and refuse its GM's new tables.
A GM can also award an item to a remote player directly, without exporting anything - see the award inbox row in section 2, which is sent only between the devices at your table and encrypted so only that one player can read it. A campaign's content files - its ruleset, power sets, item sets and bestiaries - can likewise reach a player's device directly while the GM broadcasts, when the GM shares them and as far as the campaign's Reference setting allows (see "A campaign's content files" in section 2). If a future version lets you export or share other content, such as whole campaign bundles, it would go only where you send it using your device's own sharing tools, and this policy will be updated first.
4. Permissions the app asks for
| Platform | Permission | Why |
|---|---|---|
| Android | Network access | To connect to a GM's device (and, as GM, to accept connections) on your network |
| Android | Change Wi-Fi multicast state | To find nearby GMs automatically (mDNS). Without it you can still type an address |
| Android | View network state, view Wi-Fi state | To show your device's address, router, and Wi-Fi band and signal in Settings > Network, and to reconnect a table played over the internet as soon as the network is back. Neither shows a prompt, and neither gives the app your location |
| Android | Run a foreground service (connected device) | While you host a campaign as a GM, so the table keeps going when you switch to another app: it shows the "DX Master is hosting your table" notification and stops when you stop broadcasting, end the campaign, or your grace period runs out. No prompt |
| Android 13 and newer | Notifications | Asked the first time you broadcast, to show that hosting notification. Refuse it and you host just the same, without the notification. The app posts no other notification |
| Android 15 and newer | Detect screen recording | So a GM is warned when their whole screen is being cast or recorded (Cast screen, Smart View) while they cast the encounter to a display: the table could then see the GM's view. It reads nothing of the screen, only whether it is being captured. No prompt |
| Android 17 and newer | Nearby devices (local network access) | Android 17 blocks every connection to other devices on your local network until you allow this. It is needed to join a GM's campaign, to host one, and to cast to a Chromecast, and the app asks with an explanation the first time it is needed |
| iOS / iPadOS | Local Network | To find and connect to a GM's device on your Wi-Fi, to host as a GM, and as a GM to find the TVs and Chromecasts you cast to. Also declares the _airplay._tcp, _dxmaster._tcp and _googlecast._tcp Bonjour services |
| macOS | Local Network | The same as on iOS, with the same Bonjour services. macOS asks the first time the app looks on the network |
| Windows | Firewall prompt | Windows may ask whether to allow incoming connections when you host as a GM |
DX Master does not request your location, contacts, camera, microphone, photos, or files. (Android withholds a Wi-Fi network's name from apps that don't have location access, so DX Master shows the Wi-Fi band and signal but not the name.)
5. Backups made by your device
Your device's own backup may include DX Master's data - for example Android Auto Backup to your Google account, or an iCloud or computer backup on iOS. Those backups are controlled by your device settings and governed by Google's or Apple's terms, not by DX Master. They would include your character files, including the stored keys if a character is in a campaign, and - on a GM's device - the copies of players' characters described in section 1, with the values that let each player's device back in, and, while a campaign is broadcasting, the table being hosted with its keys (section 1), until you stop broadcasting. A backup DX Master makes itself (Settings > Backups) holds your maps, and - on a player's device - the maps your tables sent you.
6. Third parties
DX Master contains no third-party analytics, advertising, or tracking code, and its own network connections go only to the GM or player devices you choose to play with - with three exceptions that only happen when you use them: playing over the internet, through DX Master's relay on Cloudflare (see "Playing over the internet" in section 2), the connection test below, and free packs (see "Getting free packs"). Settings > Network has a "Run connection test" button, which sends a single ping (a small echo request that carries no information about you or your data) to your own device, to your router, and to 1.1.1.1, a public address run by Cloudflare, to check whether the internet is reachable. Like any internet address you contact, 1.1.1.1 can see the public IP address your network uses; DX Master sends nothing else and does not do this unless you tap the button. If you install it through an app store or a testing service (Google Play, the Apple App Store, the Microsoft Store, TestFlight) or download it from GitHub, that service collects its own information under its own privacy policy, and may provide the developer with aggregate statistics or - if you choose to send it - crash reports or feedback.
Buying content packs
Settings > Rules Store sells content packs (a game's ruleset with its power sets, items and creatures) through the store your copy of the app came from.
- The store handles the purchase. The store's own purchase window takes the payment, under its own terms and privacy policy; DX Master never sees your payment details. The store knows the store account that bought the pack, what was bought, when and for how much, as it does for anything you buy there, and may give the developer the sales records its terms allow (such as order numbers, dates, prices and countries).
- What the app tells the store: the product ID of the pack you ask to buy, and that a bought pack was installed. It asks the store which packs your account holds when the app starts, when it comes back to the front, and when you tap Restore purchases.
- What the app keeps: the packs themselves are already inside the app, so nothing is downloaded. When the store says your account holds a pack, the app installs it on your device and records which pack it holds, from which store, with the store's proof of the purchase (see "App preferences" in section 1). That record never leaves your device: it is not shared with a GM's players, and it is left out of the backups the app makes.
- Each store:
- Google Play (Android). Google takes the payment and knows the Google account that bought the pack. The app's proof of the purchase is Google Play's purchase token.
- The Apple App Store (iPhone and iPad). Apple takes the payment and knows the Apple Account that bought the pack. The app's proof of the purchase is the App Store's transaction ID.
- The Microsoft Store (the Windows app). A pack bought in DX Master from the Microsoft Store goes through Microsoft's own purchase window. Microsoft takes the payment and knows the Microsoft account that bought it. The app asks the Store which of its add-ons that account holds, and keeps the add-on's Store ID as its proof of the purchase.
- No server, no account of ours. The developer runs no server for pack purchases and has no account for you, and the app sends the developer nothing about what you buy.
The hosting subscription
A GM hosts over the internet with a subscription bought in Settings > Internet play, through the store your copy of the app came from (Google Play on Android; the App Store on iPhone, iPad and the Mac - one subscription covers that Apple Account's devices, and Family Sharing members). Windows hosts on your network only until the Microsoft Store release.
- The store handles the purchase. As for packs: the store's own window takes the payment, a free trial or an offer code, under its own terms; DX Master never sees your payment details. Restore purchases, Redeem a code and Manage open the store's own sheet or page.
- What the app asks the store: the plans and their prices, and which hosting subscription your account holds (when a GM's device starts, when you open Settings > Internet play, and before your table opens on the relay). It keeps the store's proof (section 1) and shows it to the relay only.
- Test builds: a store's test purchase (TestFlight's or App Review's sandbox, a Google Play license tester) is free; the relay then gives a 30-day beta pass from that purchase.
Getting free packs
The Rules Store in Settings lists free packs beside the packs for sale. They come from DX Master's public repository on GitHub (github.com/dexxfm/dxmaster-free-packs). Apart from the connection test above and playing over the internet, this is the only part of the app that reaches the open internet, and it does so only when you open the Rules Store or get a pack.
- Only when you open the Rules Store. Nothing is downloaded when the app starts or in the background. The app asks GitHub for the list of free packs when you open the Rules Store (the first time each time the app runs) or tap Refresh, and downloads a pack only when you tap Free or Update.
- What GitHub sees. GitHub (owned by Microsoft) sees your device's public IP address and which files it downloads - the list, its signature, and the packs you get - as any website sees what is downloaded from it, under GitHub's own privacy policy. GitHub may also give the developer download counts for each file.
- What is sent: nothing about you. These are plain downloads. There is no account, no sign-in and no ID; the requests name the app only as "DXMaster", carry no cookie, and say nothing about you, your device's content, or what you already have.
- What the app keeps: the packs you get, installed like files you import (see "Free packs you got" in section 1), and which free packs you got with their versions, so it can offer an update (see "App preferences"). It sends none of it anywhere.
- Checked before it is used. The list is signed by the developer, and the app checks that signature with a key built into the app before it shows anything from it; each pack must match the size and fingerprint the signed list gives it.
7. Children
DX Master is a general-audience game companion. It does not knowingly collect personal information from children under 13. The only record the developer keeps of anyone is the relay's record of a GM's hosting subscription (section 2), and a subscription is bought by the holder of a store account, under that store's parental controls.
8. Your rights
Everything on your devices is under your control (see section 1). The relay's records are the only data the developer holds ("What the relay keeps", section 2), and they delete themselves on the schedule given there. To see or delete yours sooner, write to dexxfm@outlook.com with your store and the order number on your receipt: the developer will find the record from it, delete it and confirm. If you host over the internet again, your device shows the relay its proof and a new record is made. We do not sell or share personal information.
9. Changes to this policy
If the app's data practices change - for example, if it adds file sharing, an account, or any online service - this policy will be updated first, and the "Last updated" date above will change.
10. Contact
Questions about this policy: dexxfm@outlook.com