Your game.
Your information.

Who is responsible

Jamb is operated by DM Projects. For privacy questions or requests about your information, use our contact form and mention Jamb. You can also contact us through Feedback & Support in the app. You do not need a Jamb account to play.

At a glance

Your saved games, score sheets, personal high scores and appearance preferences are stored on your device. The app also sends usage events to PostHog, error reports to Sentry, and purchase information to RevenueCat and the relevant app store. If you contact support, the information you submit is stored in our support system.

App analytics starts automatically in configured release and test versions. The app currently has no analytics consent prompt or in-app opt-out switch. We do not record your screen or enable session replay. The separate website analytics choice does not control analytics inside Jamb.

Games and settings on your device

Jamb saves ongoing games, completed score sheets, personal rankings, selected language, themes and dice preferences locally so you can continue playing. Purchase entitlements are also cached locally. We do not provide a cloud game account or server-synchronised high-score leaderboard in this version. Some game information, including a completed game's total score, is included in the usage events described below.

Your operating system may include eligible app data in a device backup, depending on its settings. Removing the app normally removes its local app data, but does not necessarily remove device backups, secure keychain entries, store purchase records or information already sent to our service providers.

Usage analytics: PostHog

We use PostHog to understand how Jamb is used and where the experience can be improved. The app reports installation and application lifecycle events, games started, resumed, abandoned and completed, and storage migrations. Game events can include a generated game identifier, manual or solo mode, the number of score sheets and the final total score.

Events also include a persistent, randomly generated analytics identifier and technical context such as app version, operating system, device model, language, screen dimensions and event time. The identifier is stored on your device. It is pseudonymous: it lets events from the same installation be associated without asking for your name. It should not be understood as a guarantee of anonymity.

Jamb is configured to use PostHog's European ingestion service. Requests necessarily involve your IP address; the provider may derive approximate location from that address according to the project's configuration. We do not request GPS access for analytics. Our game event payloads do not include your name, email address or support-message content, and we do not enable session recordings.

See PostHog's privacy notice for information about the provider.

Error reporting: Sentry

We use Sentry to investigate crashes and technical failures. Reports may include error messages, stack traces, app version, operating system, device information and technical events preceding an error. The app disables Sentry's default personally identifiable information option and performance sampling. It filters support-related data and private support links out of error reports and breadcrumbs.

These measures reduce the information sent; they do not mean that every technical error report is necessarily anonymous. Network connections also expose an IP address to the receiving infrastructure. See Sentry's privacy notice.

Optional purchases: RevenueCat, Apple and Google

Additional designs are optional one-time purchases. We use RevenueCat with Apple App Store or Google Play to retrieve products, validate purchases, maintain access to purchased designs and restore eligible purchases. RevenueCat can receive a generated app-user identifier, product identifiers, transaction or purchase-token information, purchase history, entitlement status and technical app/device information. Its SDK may connect when purchase access is checked, even if you have not just made a purchase.

We do not supply RevenueCat with a named Jamb account. Automatic device-identifier collection is disabled in our RevenueCat configuration. Payment details such as your full card number are handled by your store or payment provider, not entered into Jamb or received by DM Projects through the app.

Further information: RevenueCat, Apple and Google.

Feedback, support and feature suggestions

Opening Feedback & Support connects to DM HQ, our hosted support portal. The app creates a random installation identifier and a secret stored in secure device storage. These let you return to your own requests without creating an account. The portal also receives your selected language, app version and platform.

We process the messages, optional email address and images you choose to submit, our replies, ticket status and feature votes to answer your requests and manage improvements. Providing an email address allows ticket confirmations and updates to be sent by email. Support messages and attachments are private; only separately written, moderated feature summaries and aggregate vote counts appear on the public ideas board.

DM HQ uses Vercel for hosting and Convex in EU West (Ireland) for its database and file storage. Resend handles incoming and outgoing support email. A ticket's private link grants access to that conversation; keep it private. The portal uses essential access cookies. You can also contact us through the website form, whose handling is explained in our website privacy information.

Delivering the app and updates

Apple and Google deliver the app and handle their own store services. Jamb also uses Expo's update service to check for and download compatible app updates. These requests involve technical information such as platform, app runtime, update channel, installed update and IP address. See Expo's privacy notice.

Purposes and legal grounds

We use information to provide the game and purchased features, respond to support requests, protect our services, diagnose failures and understand product usage. Where the GDPR applies, information necessary to fulfil a purchase or a requested service may be processed to perform that contract; security and proportionate reliability work may be based on legitimate interests; legally required records may be retained to meet legal obligations.

Product analytics is described separately above because it starts automatically in the current app. Reading this notice or continuing to use Jamb does not, by itself, constitute consent. Where applicable law requires consent for a particular use of information or access to device storage, this notice does not replace that requirement.

Service providers and international processing

The providers identified above process information to deliver their services. European hosting for a particular service does not mean that all providers, support operations or subprocessors are exclusively in the European Economic Area. Providers may process information in other countries, including the United States. Applicable safeguards, processing locations and subprocessors depend on the relevant service and agreement. Contact us if you need further information about a particular data flow.

We do not use Jamb's analytics identifiers to serve advertising or combine your activity with other companies' apps for advertising. This notice does not describe app-store or operating-system processing carried out independently by Apple or Google.

How long information remains stored

Local game data and preferences remain until they are replaced, removed through available app functions or removed with the app's storage. Support conversations and attached images remain in DM HQ until removed; there is currently no automatic conversation deletion period. Unsubmitted staged support images are removed after 24 hours.

Analytics, diagnostic, email and purchase records remain subject to the relevant service's project settings and retention arrangements. This version of Jamb does not implement an app-wide automatic deletion period for those server-side records. Uninstalling the app does not delete them. Purchase records may need to remain available to restore access, resolve disputes or meet legal obligations. You can contact us to ask about retention or request deletion of information associated with you.

Your choices and rights

You can choose whether to buy a design, contact support, provide an email address or submit an image. You can change your device's backup settings separately. There is currently no in-app switch for PostHog analytics; contacting us or changing the website's cookie choice does not automatically stop events from your app installation.

Depending on the law that applies, you may have rights to access, correct or erase personal information, restrict its processing, receive a portable copy, or object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. You can complain to the data-protection authority where you live, work or believe an infringement occurred.

Send requests through our contact form or in-app support. Explain which information your request concerns. We may need proportionate information to locate records and verify your entitlement to them; we may not be able to link a pseudonymous analytics record to you from your name alone. Do not send passwords, payment-card details or private ticket links through public channels.

Children and shared devices

Jamb does not require a date of birth and does not verify a player's age. A store age rating describes content and is not a statement that no personal information is processed. Parents or guardians can contact us about information a child may have submitted.

Changes to this policy

We update this page when Jamb's data handling changes and show the revision date above. Material changes may require additional notice or choices in the app. This notice covers version 2.0; older releases may use a different set of features and services.