Privacy note for Control Realms

Information We May Collect

Guests receive a random first-party identifier. If you create an account, we collect authentication and profile details. We also process scenario activity, saved progress, subscriptions, feedback you submit, organization or cohort information where applicable, and basic technical context such as route, device class, release, and application version.

How We Use Information

We use information to deliver free Prologues and paid Realms, preserve progress, manage subscriptions and access, prevent abuse, diagnose failures, improve content and usability, operate pilots, and respond where you explicitly permit follow-up.

Payments, Authentication, And Storage

Stripe processes checkout, recurring payments, invoices, cancellations, refunds, and payment-method updates; Control Realms stores Stripe customer and subscription identifiers but not full card details. Supabase supports authentication and progress storage. Hosting and infrastructure providers process technical data needed to deliver and secure the service.

Analytics And Feedback

We use limited first-party funnel events, including Directory visits, Prologue starts and completion, account and checkout steps, paid chapter activation, feedback, and return activity. Analytics events do not contain email or free-text feedback. Feedback may include the message you submit and disclosed technical context; decisions and private notes are not attached automatically.

Retention, Access, And Deletion

We retain account, progress, transaction, security, and support records for as long as needed to provide the service, meet legal and financial obligations, resolve disputes, and protect the platform. You may request access, correction, or deletion by contacting us. Some transaction or security records may be retained where law or legitimate operational needs require it.

Scenario And Team Context

Individual scenario choices, notes, and related activity may be used to run the experience and show personal progress. Team or classroom pilots may include seat, invitation, engagement, and approved reporting views for managers or instructors.

Service Providers

Control Realms may rely on third-party hosting, authentication, database, email, analytics, and infrastructure providers to operate the landing page, app, and related services.

Contact

For privacy questions about Control Realms, contact Prosperus Risk Consulting at info@prosperusrisk.com.

Last updated: August 10, 2026.