Product privacy notice
Samsarix Realms privacy
This notice explains processing specific to Samsarix Realms. It supplements the shared Samsarix Privacy Policy that governs your account and common services.
Who operates Realms
Samsarix Realms is operated by Andrew John Ward as part of the Samsarix service. Use contact@samsarix.com for privacy questions or requests.
Realms and Samsarix Social use the same Samsarix account. Product attribution keeps analytics, push installations, usage limits, and entitlements separately scoped, but signing in to either app does not create a second account.
Information Realms handles
Account and hero data
Account identifiers, profile display information, consent choices, hero name, portrait, archetype, rank, titles, loadout, and app-scoped usage state.
Adventure records
Campaign premises, messages, choices, dice and combat events, party membership, character context, world state, objectives, inventory, locations, generated narration, completion summaries, and related safety records.
Shared-world participation
Server-derived event contributions, participation credits, milestone and raid progress, guild membership, shared Chronicle facts, coarse presence timestamps, and party-lobby participation. Realms does not accept client-written scores as authoritative world history.
Community content
Guild names and mottos, party-lobby titles and notes, host display snapshots, reports, blocks, and other content you choose to make visible to other players.
Device, service, and billing data
Authentication and security events, app version and platform, push installation, delivery state, optional diagnostic data, entitlement state, and a one-way purchase fingerprint. Google Play handles payment credentials; Realms does not store full payment-card details as adventure data.
How and why the information is used
Realms uses this information to create and resume adventures, maintain deterministic game state, generate requested narration, coordinate co-op play, update the shared world, provide guild and party-finder features, deliver notifications, enforce usage limits, restore purchases, provide support, prevent abuse, and meet legal or dispute obligations.
Depending on the processing and applicable law, the legal basis may be performance of the service contract, your consent, legitimate interests in operating and protecting the service, or a legal obligation. Optional analytics, model-improvement, marketing, and connected-service sharing remain off unless the corresponding privacy choice permits them.
AI processing and authoritative game state
To generate a requested turn, Realms sends the prompt and the bounded adventure, character, memory, and safety context needed for that response to a selected AI provider described in the shared Privacy Policy. Do not include information you do not want processed for the requested feature.
AI output is narration, not authoritative history. The server validates game-state changes, rewards, contributions, milestones, and Chronicle facts. Optional Chronicle prose must cite stored structured facts; a deterministic rendering is used when the prose route is unavailable or fails validation.
What other players can see
Invited co-op members can see the shared adventure content and game state needed to participate. Guild directories, party-finder listings, standings, aggregate event and raid progress, and Chronicle entries expose only their defined public projections. Private prompts, credentials, raw purchase identifiers, and unrelated account data are not part of those projections.
Public guild and lobby text is safety-screened and may be moderated. Blocks prevent affected accounts from being matched through the party finder without revealing the block relationship.
Retention, export, and deletion
Adventure and hero records are generally retained while the shared account or feature remains active. Open party listings leave discovery after their bounded availability window. Safety, billing, consent, fraud-prevention, dispute, backup, and legal records may be retained longer where necessary.
The authenticated export is account-wide and can include data from both Realms and Social. Account deletion from either app affects the same shared Samsarix account and removes or de-identifies account-linked data through the published process. Canonical aggregate world state and Chronicle facts that no longer identify you may remain as shared-world history.
Deleting the app or Samsarix account does not cancel a Google Play subscription. Use the subscription-management destination in Settings before deleting the account.
Your choices and rights
Settings provides consent controls, account-wide export, account deletion, app-scoped support diagnostics, push preferences, blocked-account management, and subscription management when applicable. Support diagnostics exclude prompts, replies, tokens, device tokens, and stable account identifiers.
Depending on your location, you may have rights to access, correct, export, delete, restrict, or object to processing; withdraw consent; and complain to a data-protection regulator. Contact contact@samsarix.com or use the in-app controls. Lawful exceptions may limit a request.
Security, age, and changes
Realms uses authenticated access, server-owned game rules, bounded public projections, content screening, product-scoped push and billing identifiers, and encrypted transport. No online service can promise absolute security.
Realms is intended for adults and is not directed to children. The date above identifies this version. Material changes will be communicated through an appropriate account, product, or provider notice; renewed consent will be requested when required.