TableSync
TableSync — Privacy Policy
Last updated: 23 October 2026
TableSync is a family of apps for tabletop role-playing games, published by Adam Mosley. This policy covers every one of them:
- TableSync Player (
style.tablesync.player), the character sheet, for Android and iOS and as a web app; - TableSync DM (
style.tablesync.dm), the game master's screen, for Android and as a web app; - TableSync Solo (
style.tablesync.solo), solo adventures, for Android and as a web app; - TableSync Map (
style.tablesync.map), the battle map, for Android and as a web app; - TableSync Codex (
style.tablesync.codex), the rules reference, for Android and as a web app; - and the TableSync desktop and browser applications.
The short version
TableSync has no servers. There is no TableSync account, no TableSync back end, and nothing you do in any of these apps is sent to the developer. What you make is stored on your own device. Something leaves your device only when you send it: when you join a game master's (DM's) table, which goes to that DM's computer and nowhere else, or when you send a character, a map, an adventure or another item to another app or person yourself. Looking up a join code sends the code alone to a small address service the developer runs; it never sees your key or your characters.
TableSync Solo and TableSync Codex go further: their Android apps declare no internet permission at all, so they cannot send anything anywhere.
What each app stores on your device
| App | What it keeps, on your device only |
|---|---|
| Player | Characters you create (names, ability scores, spells, equipment, a player name if you enter one, a portrait image if you add one), content packs you import, and preferences such as which character you last opened. |
| DM | Campaigns, party cards, fights in progress with their log, saved encounters, session prep, the campaign notebook, and the last desktop table address you used (never its key). |
| Solo | Heroes, adventures you import or write, your progress and save slots, and journals with your notes. |
| Map | Map images you import, their grid alignment, your scenes, the screen calibration for each display, and the last desktop table you opened, with its player key, so it can open it again. |
| Codex | The records you opened recently, the lists you pin records into, and your reading settings. |
This is held in each app's own storage on your device; for a web app, in your browser's storage for this site. Uninstalling an app, or clearing the site's data in your browser, removes it. The developer cannot see it, and it is not sent to any service operated by the developer.
Android backup. TableSync Player allows Android's own backup system to include its data, the standard behaviour that lets your characters survive moving to a new phone. Where that is enabled on your device, the backup goes to your Google account, under Google's terms, not to the developer; you can turn it off in Android's system settings under Backup. TableSync DM, Solo, Map and Codex opt out of Android's backup: use the app's own export or backup file to move your data.
What is sent off your device, and when
Nothing is transmitted unless you take one of these actions:
- Joining a DM's table (Player). You enter an address and a key that the DM gives you. Your character sheet is then sent to, and kept on, that DM's computer so the DM can see your character during play. That computer is not operated by the developer. What the DM does with it is between you and your DM.
- Joining by a join code (Player). A DM can hand you a short code instead of an address. To turn it into the table's address, the app asks a small redirector service run by the developer (
undeployedadam.com) where that code points. That request carries the code and nothing else — not your key, not your name, not your characters — and the service keeps no record of who asked. Your key then goes only to the DM's own table, exactly as in step 1. - Opening a desktop TableSync table (DM and Map). TableSync DM can open the DM screen, and TableSync Map the projector view, of a desktop TableSync that you or your DM run. The app connects only to the address you enter, a computer run by you or your DM, not by the developer.
- A table reached over the internet. A DM can publish their table through a tunnel, so the address you join may be a public
https://…name rather than a local network one. The connection is encrypted to the tunnel provider and terminated at the DM's machine; the tunnel operator (Cloudflare, for the launcher's built-in option) can see the traffic in transit as any relay can. The developer is not on that path. - Sending something to another app or person (every app). The apps hand each other one item at a time — a character, a party, an encounter, session prep, an adventure, a map or a rules record — as a TableSync Link. On Android, Send passes it straight to the other TableSync app on the same device. Otherwise it is a file you save or share, or a code you copy and paste. It goes only where you send it: if you paste a code into a chat or share a file by email, that service carries it under its own terms.
- Exporting to a file (every app). The file goes where you put it.
The apps make no other network requests. They contain no advertising, no analytics, no crash reporting, no tracking of any kind, and no third-party SDK that collects data.
TableSync Player, DM and Map are able to use plain HTTP connections, because a DM's table on a local network runs on a plain address rather than a public HTTPS site. Those connections go only to the address you type in; a published table's https:// address is used as given and never downgraded.
The web apps. Opening a web app under undeployedadam.com/tablesync/ is an ordinary visit to a web page: the site's host (Hostinger) and its content delivery network handle the request as they would for any website. Your browser then keeps the app's files so it works offline. Nothing you make in a web app is sent back to the site.
Other TableSync apps on the device. On Android, each app can check which other TableSync apps are installed, so it can say "Installed" or offer the app's page. That check happens on the device and is not sent anywhere.
Children
TableSync is not directed at children under 13, and collects no personal information from anyone, including children.
Permissions
| Android app | Permissions it declares | Used for |
|---|---|---|
| Player | INTERNET, VIBRATE | Reaching the DM's table address you enter and looking up a join code; vibration for the dice and your turn. |
| DM | INTERNET, VIBRATE | Reaching a desktop TableSync address you enter, and nothing else; vibration for the dice. |
| Solo | VIBRATE | Vibration for the dice. No internet. |
| Map | INTERNET, VIBRATE | Reaching a desktop TableSync address you enter, and nothing else; vibration. |
| Codex | VIBRATE | Vibration for the dice. No internet. |
Each build also carries an internal signature-level permission generated by the Android support libraries (DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION), which grants no access to anything on your device and cannot be used by other apps. None of the apps requests location, contacts, camera, microphone, or storage permissions. Choosing a portrait or a map image, or a file to import, uses the system's own picker, which hands the app the single file you chose.
Your data, your control
Because everything is on your device, you are in control of it:
- Delete a character, campaign, adventure, map or list in the app.
- Export to a file to keep or move it.
- Uninstall an app, or clear the site's data in your browser, to remove everything at once.
For a sheet you have sent to a DM's table, ask that DM to remove it — the player app deliberately cannot delete from a DM's machine. An item you sent to someone else's app is theirs to delete.
Third-party content
The apps include game rules content from the System Reference Document 5.1 and 5.2.1, published by Wizards of the Coast LLC under the Creative Commons Attribution 4.0 International License. That content is bundled in the apps and involves no data collection. Full attribution is in each app under About, and in the NOTICE file shipped with the desktop download.
TableSync is an independent project. It is not affiliated with, endorsed by or sponsored by Wizards of the Coast LLC.
Changes
If this policy changes, the date at the top changes with it, and the updated policy ships with the next release of the apps.
Contact
Questions about this policy: adamisdeployed@gmail.com