jonbarson.cz is a personal, non-commercial set of tools for tabletop Dungeons & Dragons. This page explains what data the site processes, the terms of use, and the licenses of third-party content.
Jan Barták, operator of jonbarson.cz. Contact: hello@tablemimic.com.
| Data | Why |
|---|---|
| E-mail and account ID (uid) | Sign-in and linking your data to your account |
| Your content (campaigns, notes, library, settings, pets) | Running the tools and syncing across your devices |
| The character sheet you send to a DM table (name, class, race, level, AC, hit points, conditions, concentration, inspiration, initiative, death saves, resistances, immunities, vulnerabilities, active effects, summons) | Running the game: only that table's DM can read it, the other players cannot reach it. It is sent only once you join a table yourself; leaving stops the updates and the last state stays at the table until the DM removes you from it. |
| A small card for the party at the same table (name, class, race, level, whether you are connected; hit points only while you share them) | The Party roster module: the other signed-in players at that table read it, and they keep that access until the DM removes them from the table; their own disconnect does not end it. It is a separate record, not a slice of the DM's card, so nothing else about your character reaches them. You can switch the hit points off in the table chip on your character sheet; they are then not in this card at all, and leaving the table takes them off it too. The DM sees them either way, in the card above. |
| The DM's session brief (a short recap your DM sends to the table) | The DM writes it in the Campaign Planner and puts it on the table with an explicit button; their private session notes are not part of it. Only signed-in players at that table read it. The last brief you received is stored on your character sheet and synced across your devices so it stays readable after you leave the table; only the next brief replaces it. |
| Handouts from the DM (a title, text and a link to an image in the DM's storage) | The DM sends a handout into your private channel at that table, which only the two of you can see. Keep stores it on your character sheet, where it syncs across your devices and stays until you delete it; Close stores nothing. The image itself stays in the DM's storage, so if the DM deletes it, it stops showing for you too. |
| Uploaded maps / images (Connector) | Showing them on your table display |
| Technical visit data (page path, device category, source bucket, hour; IP only truncated and transiently) | Cookieless server-side traffic statistics and bot filtering |
| Anonymous usage data (only with your consent) | Traffic statistics — which tools get used |
We measure traffic in two ways. (1) Our own cookieless server-side measurement: it stores only the page path, a coarse device category, a source bucket (e.g. “google”), the hour, a coarse country (derived server-side from the IP, which is discarded right away), the browser language, a human/bot class, aggregate page-load speed (Web Vitals) and aggregate script-error counts (type and file, never message contents) — never your IP address, user-agent or any identifier on your device. To tell short visits (sessions) apart, the server derives a transient pseudonym from a truncated IP (IPv4 /24, IPv6 /48) and the browser; the key rotates daily and the pseudonym is deleted within 24 hours, so you cannot be linked across days. (2) Google Analytics runs only with your consent (the banner on your first visit) — without consent it does not start. We do not use advertising cookies and we do not sell or share data with anyone beyond the processors below.
The card-game apps on jonbarson.cz (Riftbound, Manaforge) work without signing in — your data (card collection, decks) then stays only in your browser's storage and is not sent anywhere. After signing in it syncs to Firebase under your account (keys such as collection, decks, preferences) so you have it on all your devices. Submitted feedback stores the uid, name and e-mail of your account so we can reply to you.
Separately from your personal data, the site serves a public game-reference database (the Compendium — monsters, spells, items and equipment, built from SRD 5.1, SRD 5.2.1 and Open5e). It is static reference content, contains no personal data and is not tied to any account. Its sources and licenses are listed in section 3 below.
We process the data to provide the service you sign up for (Art. 6(1)(b) GDPR). Your data is kept as long as your account exists; when you delete the account, the associated data is deleted too. A guest (anonymous) account stores data only in your browser.
Cookieless traffic measurement and abuse protection (rate limits, bot filtering) rely on legitimate interest (Art. 6(1)(f) GDPR). Daily traffic statistics without personal data are kept for 90 days; transient technical records (session state, rate-limit buckets) for a few days at most.
Under the GDPR you have the right to access, rectify, delete („be forgotten“), export (portability), restrict and object to the processing of your data. To exercise them, write to the contact above.
We only use technical local storage that is necessary for the tools to work — the interface language, the sign-in token and your saved content. If you allow traffic measurement in the banner, Google Analytics additionally stores its cookies; you can withdraw consent anytime by clearing this site's data in your browser (the banner reappears). No third-party advertising cookies.
IP geolocation for traffic statistics: DB-IP Country Lite (CC BY 4.0) — coarse country only, the IP is never stored.
The full Open Game License 1.0a text and the complete Section 15 — generated from each source's metadata — are on the dedicated licenses & attributions page.
Reproduced as required by the licenses. Full license texts: Open Game License 1.0a — open5e.com/legal; CC-BY-4.0 — creativecommons.org/licenses/by/4.0; ORC License — paizo.com/orclicense.