Privacy Policy

RPG Companion — Last updated: June 8, 2026

This policy describes how RPG Companion (mobile app com.rpgcompanion.mobile) and the optional online campaign service at rpg.kkbtec.com (including the web Campaign Studio at /studio/) handle information.

Summary

RPG Companion is built for tabletop role-playing: character tools, local party features, and optional connections on your network. We do not sell your personal information. The App stores game-related data on your device and may exchange data on your local network when you use party or LAN features. If you configure a backend URL in a custom build, data may be sent to that server as described below.

Information stored on your device

The App may store information locally, including:

• Character sheets, notes, and related RPG data using on-device storage (including a local database).
• Images you choose for character portraits or similar features, saved in the App’s file storage.
• App settings and preferences (for example, values stored with the device’s secure storage APIs).
• Error log entries (error messages, stack traces, screen name, and app version) when the App records a failure. Up to 50 recent entries are kept in local storage until you clear them in Settings → View error log. They are not sent to us automatically; you choose whether to share them using Share report.

This data remains on your device unless you use features that send it elsewhere (see below).

Local network and party features

When you use features that discover or connect to nearby sessions (for example, over Wi-Fi), the App may:

• Use local network permissions to find devices or services on networks you are connected to.
• Open network connections between your device and other devices on the same local network for session or sync features.

That traffic typically stays on your LAN and is used to operate the feature you started. It is not sent to us by default?we do not operate those connections as a cloud service in the standard App configuration.

Online campaign relay (rpg.kkbtec.com)

If you use online campaign features, character snapshots and combat sync messages are transmitted over TLS-encrypted connections (HTTPS/WSS) to our campaign relay on Microsoft Azure. The server routes messages between the DM and players and may temporarily store session metadata and combat state for reconnect (typically up to 24 hours). Cloud account registration stores your email and a bcrypt password hash; we do not store plaintext passwords.

Uploaded maps or custom content bundles are stored in Azure Blob Storage (encrypted at rest by the cloud provider) and linked to your account. Audit logs record connection and authentication events without storing your password.

We do not sell personal information. We do not process payment card data on this service.

Data retention (server)

• Campaign sessions and combat snapshots: expire automatically (default 24 hours).
• Cloud accounts, maps, and bundles: retained until you delete them or request account deletion.
• Server audit logs: retained approximately 90 days.

Encryption

Data in transit between the App and rpg.kkbtec.com uses TLS 1.2 or higher. Data at rest on Azure uses platform encryption (managed disks and blob storage). Secrets on the server are stored in restricted configuration files accessible only to the service account.

Local network and party features

When you use features that discover or connect to nearby sessions (for example, over Wi-Fi), the App may:

• Use local network permissions to find devices or services on networks you are connected to.
• Open network connections between your device and other devices on the same local network for session or sync features.

That traffic typically stays on your LAN and is used to operate the feature you started.

Camera and photos

With your permission, the App may access the camera (for example, to scan QR codes for joining a party) and your photo library (for example, to pick a character portrait). Images are used for the in-app features you choose; they are not uploaded unless you use cloud map upload.

Microphone

The App may request microphone-related permissions only if needed for a feature that uses audio. If you do not use such a feature, the microphone may not be accessed.

Internet and optional backend

The App may use the internet for general mobile platform services, content delivery, or updates as provided by the operating system and app store. Certain custom or development builds may allow configuring a backend URL. If that URL is set, data needed for sync or related features may be transmitted to the server you specify. That server is controlled by you or whoever operates it?not by this privacy policy unless we host it.

Crash and error reporting

The App may save technical error details locally (error messages, stack traces, screen name, and app version) to help you report bugs. You can view and clear this log in Settings and share it using Share report. We do not receive this information unless you send it to us (for example by email or messaging).

Analytics and advertising

The standard App experience described in this policy does not use third-party advertising SDKs or behavioral analytics for sale.

Children

The App is not directed at children under 13. If you are a parent and believe a child has provided personal information inappropriately, contact us at the email above.

Changes

We may update this policy when the App changes. The “Last updated” date at the top will change when we do. Continued use of the App after changes means you accept the updated policy.

Your choices

You can revoke camera, photo, microphone, or local network permissions in your device settings. You may uninstall the App to remove locally stored data (subject to how your device handles app data).

This text is a practical template for store listings and is not legal advice. Have it reviewed if you need compliance assurance for your jurisdiction or audience.