LAST UPDATED: OCTOBER 28, 2026
Privacy in the beta.
CastleOm uses real-world location to create a shared game world. Here's what that means for the early beta and this website.
Who operates CastleOm
CastleOm is an independent game project developed by Austin Akerley. For privacy questions and requests, use the developer contact provided in CastleOm Beta's App Details in Apple TestFlight. The support page explains how to find it.
This website
The marketing website does not request your location or camera, does not create game accounts, and does not run advertising or analytics scripts. It is hosted by Microsoft Azure, which processes requests needed to deliver the site, including network information such as your IP address. Following a TestFlight link takes you to Apple's service.
Beta account and gameplay data
The game processes your email address and account credentials, profile and character choices, castle placement and outline, inventory, progress, and game actions. Passwords are stored as password hashes rather than plaintext. Server-side account and game records allow your world and progress to persist between sessions.
Location and the shared world
The app requests location to show nearby game content, validate movement and actions, and establish castles. Castle coordinates and saved footprints can reveal sensitive places, including a home. Other players may see nearby game entities and castle information. The game uses a stable offset for certain published castle coordinates, but that is not a guarantee of anonymity or protection against inference. Do not place a castle somewhere you are uncomfortable associating with gameplay.
Camera and AR
AR is required for combat and active encounters. The game uses the camera and device sensors to position game content in your surroundings. Taking part requires an AR-compatible device, camera permission, and working AR tracking; there is no non-AR combat fallback. Camera permission is separate from location permission. You can revoke it in your device settings, but doing so prevents AR combat. The website itself does not request camera access.
Notifications, maps, and service providers
If you enable notifications, the app registers a device push token to deliver game alerts. The beta uses Microsoft Azure for backend hosting and storage, Mapbox for maps, and Apple and Expo services where configured for beta distribution and notifications. These providers also process data under their own policies.
Feedback and diagnostics
Feedback you choose to send through TestFlight can include comments, screenshots, device information, and crash reports. Apple explains what it shares in its TestFlight privacy information. Hosting and game services also generate operational logs to diagnose failures and operate the beta. Avoid including private addresses, location details, or credentials in feedback.
Data choices and removal
You can change location, camera, and notification permissions in your device settings. For requests to access, correct, or delete beta account data, contact the developer through TestFlight's App Details. An in-app account-deletion flow is not yet available. Uninstalling or leaving TestFlight does not automatically remove server-side data. We do not specify a fixed retention period in this notice; beta storage and backup arrangements are still being developed.
A changing beta
Beta accounts and progress are distinct from the future production game. This notice will be updated as features, service providers, and data practices change. Please review it before sharing sensitive information or participating in a new beta feature.