1. Operator and scope
Fully Mental Madness develops Willowbrook and Willowbrook.ai and operates this website. Team admin: ManualCoyote. Contact Support@fullymentalmadness.com for privacy and support requests.
This policy covers our website and current development builds. A person operating a separately installed village controls its local saves, AI setup and optional Discord connection. Downloading the game does not automatically send us those local records.
2. Website visits and support
The website offers information and downloads without a visitor account. Fully Mental Madness has added no advertising trackers or analytics code. Download progress and file verification occur in the browser and are not sent to a separate analytics service.
OpenAI Sites and Cloudflare provide hosting infrastructure and may process IP addresses, request URLs, browser/device information, timestamps and technical access or security logs to deliver and protect the website. Infrastructure retention is controlled by those providers. See OpenAI's policy and Cloudflare's policy.
Email links open your mail application. Emailing us shares your address, message and attachments with our team and Google Workspace email service so we can respond. We retain relevant support correspondence for handling requests and administration; we have no universal automatic deletion schedule.
3. Information saved by the game
Local village records can include resident needs, inventory, money, property, relationships, fictional beliefs, activities, selected player messages, generated replies, summaries and memories. These records may persist across restarts. AI summaries can be inaccurate.
Standalone Android B1 stores a separate local village and recovery checkpoints; it does not automatically import or synchronize a PC world. Checkpoints and operator-created backups may preserve older states. Device preferences are also stored locally.
4. Optional Discord integration
When enabled by its operator, the PC bot receives Discord events under its configured permissions and intents. It checks server, channel, user, message and interaction identifiers, bot status, command names and supplied values to authorize requests, prevent duplicate handling and respond. Events may be received before these filters are applied.
The current private configuration accepts commands only from the configured owner account in the configured server and channel. Its handler ignores other messages, does not intentionally archive unrelated conversations, and does not use DMs for village commands. Accepted commands can contain a villager name, message text or a status/recording request.
Bot credentials and configured identifiers are kept in the operator's local settings, outside downloadable packages. Queues, recent identifiers and temporary interaction tokens are held in memory while needed for operation.
Enabled sharing sends logs, replies, status and requested animated recordings to the configured channel, where people with channel access can see them. Status or dialogue can include the configured weather location and real-world date/time. Recordings capture the rendered village through a separate camera, not the desktop, webcam or microphone. Discord processes the resulting information under its privacy policy.
5. AI and weather services
The current PC release sends relevant dialogue and village context to Ollama running locally on that PC. Prompts can include accepted player messages and retrieved memories. Its default does not send this dialogue to a cloud model provider.
Standalone Android B1 has no connected AI service. Internet AI is planned and is not enabled by this website or policy. A future cloud provider and its handling must be disclosed before enabling that configuration.
The game can contact Open-Meteo for configured town and weather information. This configured town is not an automatic GPS reading. Third-party providers have their own privacy practices.
6. Retention and controls
We do not sell personal information. Local world data has no universal expiry: some lists are bounded or consolidated, while important memories may remain until the operator removes them. Backups and recovery checkpoints can retain older copies.
Disabling sharing stops new posts, but does not delete earlier Discord posts or local memories. Discord controls its own retention and available deletion tools. Website infrastructure logs follow the hosting providers' practices. Avoid submitting sensitive information to a fictional AI simulation.
7. Access, correction and deletion
Email Support@fullymentalmadness.com identifying the service, account or information concerned. Requests are handled manually; we may ask for sufficient information to establish that the request concerns you. We can address records controlled by Fully Mental Madness. A separate village operator must address their local saves and bot messages.
The current bot has no automatic privacy/deletion command. Removing a Discord message does not automatically remove a saved memory or recovery checkpoint, and deleting local information does not automatically delete its Discord counterpart. Independently retained copies may be outside our control. Applicable privacy rights remain available.
8. Changes and contact
We will update this page and its effective date when the described practices materially change. It describes current handling rather than authorizing unspecified future collection. Questions can be sent to Support@fullymentalmadness.com.