Customer products, clearly separated
Merlin products are intentionally scoped. Your account, conversations, contacts, and connected chats stay within the product and permissions you choose.
Web workspace
A chat-first workspace for questions, plans, files, voice, images, and the tools available to your account.
Boundary by default
Web context belongs to your current web identity. It does not automatically become channel-bot context.
Customer-owned channel assistant
A separate customer bot for reminders, routines, summaries, and coordination in WhatsApp or Telegram chats you explicitly pair.
Boundary by default
Each bot is account-scoped. It starts with only the chats you approve and does not automatically merge with web chat or other customer bots.
Standalone social product
An adults-only experience for nearby discovery and one-to-one conversations, with its own identity and consent controls.
Boundary by default
Meet direct chats are person to person. Merlin AI does not join them, and Meet context is not shared with Chat or MerlinBot.
James’s private personal or family spaces and Merlin’s internal team operations are not public products. They are not available through these entry points, and customer products do not imply access to their conversations, memory, contacts, automations, or connected services.
Context stays in the web workspace, paired bot, or Meet experience unless a product presents an explicit, scoped control.
A customer MerlinBot is owned by its account and starts without another customer’s or an internal workspace’s data.
MerlinBot setup currently starts with WhatsApp or Telegram. Discord self-serve setup is not presented as available.