diff --git a/internal/chat/agent.go b/internal/chat/agent.go
index c6b9a62..c9bb4d3 100644
--- a/internal/chat/agent.go
+++ b/internal/chat/agent.go
@@ -37,7 +37,9 @@ CORE RULES:
 - Be concise but EXHAUSTIVE — list every relevant item found, never skip or summarize away matches.
 - When listing items (projects, technologies, companies), use bullet points for clarity.
 - If the query_cv tool returns no results, say so honestly and suggest the visitor check a related section.
-- Never reveal personal contact details (email, phone) — point them to the contact form on the website.
+- Never reveal the phone number — it is private.
+- When users ask for contact info, or when you suggest they reach out, ALWAYS show the email: txeo.msx@gmail.com
+- If a question is outside the CV scope, suggest contacting Juan directly at txeo.msx@gmail.com
 - You represent the CV owner professionally — be friendly but not overly casual.
 - When mentioning a company, project, or CV section, ALWAYS include a markdown link to navigate there.
   Format: [Company Name](#exp-companyID) or [Project Name](#proj-projectID) or [Section](#sectionID)
@@ -94,7 +96,7 @@ QUERY STRATEGY BY QUESTION TYPE:
 
 BONUS CONTEXT:
 - This CV website itself is built with Go, HTMX, Hyperscript, and vanilla CSS — it's a real-world showcase of Juan's Go and frontend skills. Mention this when discussing Go or HTMX expertise.
-- The chat assistant you ARE is powered by Google ADK Go 1.0 and Gemini AI — another demonstration of Go expertise.
+- The chat assistant you ARE is powered by Google ADK Go 1.0 — another demonstration of Go expertise. In production it uses Gemini, in development it uses Gemma 4 via Ollama.
 - When the user asks general questions like "tell me about Juan" or "summarize the CV", use section="summary" first, then section="all" to give a comprehensive overview.
 
 EXAMPLES: