Which AI features respect my Wally sovereignty choice

When you switch Wally to a BYO endpoint, every customer-facing AI surface routes through your endpoint. Here's the full list, and the small set that stays on Turtini's account by design.

Covered by sovereignty (routes through your BYO endpoint):

• Wally chat — the primary chat surface, including every tool call Wally makes
• Wally drafts — emails, copy, social captions, headlines drafted from a hint
• Wally Insights fixer — when you ask Wally to fix or improve a flagged insight
• AI Builder Review — itemized critique-and-replace across Docs, Sites pages, Deck slides, Design canvases, and Social posts
• Builder Docs — selection-scoped rewrites in the document editor
• Builder Sites — full-site generation and the editorial review tool
• Builder Translations — page-level translations into other languages
• Builder Design — magic design from a prompt, magic resize, text rewrite, palette swap, design chat, and reference-image generation (vision)

Stays on Turtini's account by design:

• Help-article authoring — the help library you're reading right now is generated by Turtini-side tooling that has no concept of a specific org
• Admin briefings + market refresh — platform-wide operational reports that don't touch any single org's data
• Onboarding describe / recommend — runs before your org has a wallyModel config (you can't BYO a setting you haven't set yet)
• Recipe parser, inbound email-to-bill parser, inbound trip parser — content arrives from the outside world via Turtini's own integrations
• Wally on the marketing site (logged-out chat) — there's no org context to attach
• Image moderation — runs against every uploaded image for trust-and-safety reasons; not org-specific
• Site importer vision — when Wally imports a competitor's site as a template

The rule of thumb: if the AI call is processing your org's data, it respects your sovereignty choice. If it's processing platform data or world-facing data with no single-org identity attached, it stays on Turtini's account. That split is intentional — we don't want platform operations like writing help articles or scanning uploaded images to be silently routed through a customer's bill or a customer's compliance boundary.

If a specific surface needs to move into sovereignty coverage for a compliance reason that's not listed above, contact your account team — we treat sovereignty coverage as a moving target and expand it as customer needs surface.