Responsible AI Minecraft play
Safety and control
How AIPlayCraft separates accounts, player information, meeting access, and the bot execution layer.
Players stay in control
The AI is designed around explicit goals. A task can be redirected, stopped, or replaced. AI actions should remain within the Minecraft session and the permissions given to it.
Accounts protect schedules and meetings
Customer authentication uses Supabase. Meeting links and confirmed class details stay inside the signed-in account instead of being placed on public pages.
No Minecraft password collection
AIPlayCraft does not ask customers for Microsoft or Minecraft passwords. Minecraft profile information is saved as a display name and edition. Verification uses a separate one-time in-game code.
Parent and family profiles
Parent or guardian accounts can save separate family-player profiles so bookings, Minecraft names, and class participation stay attached to the correct child.
The bot runtime is separated
The website handles customers, payments, schedules, and meeting access. Bot credentials, runtime memories, and bot process files remain on a separate protected VPS.