DND Master

Privacy Policy

Prepared: October 20, 2026

This policy describes DND Master and its related app pages. Version 3.1.0 is published. Sections marked 4.0.0 describe the upcoming update. The developer is Vladimir Petrov. For data and privacy questions, contact mister.vladika@gmail.com.

1. Game records and settings

The app stores your campaigns, characters, notes, encounters, custom NPCs and other game records on your device. Settings and web bookmarks are stored locally. Imported audio and playlists are kept in the app’s file storage.

The developer does not automatically receive the contents of these records. The app contains no advertising networks and does not use this content for advertising tracking.

In version 4.0.0, you can choose a photo for a character or custom NPC portrait. The app processes and stores a copy of the selected image for display; choosing an image with the system photo picker does not give the app access to your entire photo library. Saved portraits may sync with records through your private iCloud database when iCloud is available and enabled.

Worlds in version 4.0.0 use Markdown files, images and boards in a folder created by the app or selected by you through Files. The app reads and saves changes in that folder. The folder binding stays on the device; the world record and campaign association may sync through CloudKit. The selected file provider, such as iCloud Drive, controls synchronization of the folder itself under your settings.

2. iCloud and backups

When iCloud is available and enabled for the app, game records may sync through CloudKit in your personal iCloud. They are transmitted to Apple under your account settings and Apple’s privacy policy. The developer does not have access to your private iCloud database.

This does not mean that every app file syncs: music, downloaded models and game libraries are managed separately. The app also creates local storage backups for recovery. System device backups depend on your iOS and iCloud settings.

3. Library downloads

Since version 3.1.0, game system libraries are delivered as asset packs through App Store infrastructure. Downloads and updates need internet access and available storage. Installed content is read locally. Apple receives technical information needed to deliver files; your campaign content is not needed for a library download.

In the upcoming 4.0.0 update, if Apple delivery fails or stalls, the app can download the same library data from a developer-operated GitHub Releases mirror over HTTPS. The mirror contains encrypted archives of text and images, not executable code. The download does not upload your campaigns, notes or portraits. GitHub receives technical connection information under its privacy statement.

4. Local AI and models

AI is optional. The built-in local engine uses models you download separately from Hugging Face and related delivery servers. During downloads, the service receives network information such as your IP address and file requests under the Hugging Face privacy policy. Some models may require accepting service terms and providing an access token.

In version 3.1.0, a Hugging Face token you enter is stored in the device Keychain without iCloud synchronisation and is used for download access. You can remove it in the app’s Hugging Face access settings. Do not share the token in support messages.

When a local model runs, prompts and the game data provided to it are processed on the device rather than sent to a cloud AI provider. If you choose the Ollama integration on Mac, the app contacts a local service on that same computer (127.0.0.1); the Ollama service is installed and managed separately.

In version 4.0.0, the mini-FRIDA semantic search model is bundled with the app. Generative Core AI models download separately from Hugging Face; the pinned product files are available without an account or token. Delivery services receive technical connection information during downloads; prompts to the installed model are processed locally.

5. Local network companion

When the game master starts the companion, the app opens a local server on their device. Connected players receive the campaign, character, current-combat and library information available to them; their actions and rolls are sent to the game master’s device. This session does not use a separate developer-hosted server.

The connection uses local HTTP and WebSocket. Use a trusted Wi-Fi network and share the link or QR code only with your players. The game master can disconnect participants and stop the session. The app cannot revoke copies of previously displayed data, screenshots or files that players save.

6. Websites, import and export

When you open a website in the built-in or system browser, or import an NPC from a link, your device connects to that website. The site may process IP addresses, cookies, sign-in details and other information under its own policy. The built-in browser may retain website data; it is not a private-browsing mode.

When exporting a campaign, character or other file, you choose its destination and how to share it. The file contents become available to the selected app, cloud storage or recipient. The DND Master developer does not control those transfers.

7. Support and this website

If you contact the developer by email or Telegram, the selected service and recipient receive your message and any attachments. Other group members may see Telegram group messages. Use email for personal data questions and avoid sharing more information than needed to resolve the issue.

These pages contain no embedded advertising or analytics scripts, data-collection forms or external fonts. GitHub Pages serves the pages and images and may process technical visitor information under the GitHub privacy statement. Visits to the App Store, Telegram and other sites are governed by those services’ policies.

8. Managing and deleting data

Game records, downloaded libraries, models and backups can be deleted in the corresponding app sections. Synced changes may propagate to your other devices. Apple system settings let you manage iCloud data and app permissions.

Deleting the app removes its local file storage but does not guarantee deletion of iCloud copies, system backups, exported files, previously sent messages or Keychain entries. Remove the Hugging Face token in the app and revoke it in your Hugging Face account. Manage copies held by recipients and third-party services separately.

A world folder selected through Files may be outside the app storage. Disconnecting a world from the app does not delete that folder; you manage its files and copies in cloud file services separately.

9. Policy updates

This page and the date above will be updated when features or data handling change. The app’s age restrictions are shown in its App Store listing.