Who's behind yfull.ai
yfull.ai is built and operated by the team that has continuously maintained the YFull Y-DNA and mtDNA phylogenetic tree since 2014. We've extended this research-grade substrate with AI-driven historical context generation — keeping the same team, the same data standards, and the same commitment to accuracy. This page documents who we are, how our AI agents work, and how we protect your data.
The YFull Team
Genealogists and population genetics researchers needed a phylogenetic tree that kept pace with rapidly accumulating Y-DNA test results — one updated by research criteria rather than consumer appeal. Most commercial ancestry services optimized haplogroup estimates for engagement, not accuracy. YFull was built to fill that gap: a continuously updated, research-grade tree serving the scientific genealogy community.
YFull.com has operated for 12 years, accumulating submissions from users across 220 countries. The YFull tree updates faster than academic reference datasets — new sequencing submissions are incorporated as they arrive, without waiting for scheduled publication cycles.
yfull.ai extends the YFull substrate with AI-generated historical context narratives. The same curated phylogenetic data that powers yfull.com drives narrative generation at yfull.ai. Same tree, same team — a presentation layer that translates haplogroup labels into readable historical context.
The YFull Team has curated the YFull tree continuously since 2014. yfull.ai builds on the same team and the same curated tree — yfull.com remains the research site; yfull.ai is the AI-narrative layer over the same substrate. Currently structured as Genetic History S.L.U. (CIF B24962573, Spain).
AI Agents
yfull.ai operates as an AI-first service: customer support, content generation, site implementation, compliance review, and project coordination are all handled by specialized AI agents. One function is handled by a human: your data protection rights. If a query requires DPO-level escalation, a human responds. We document our agent roster here because transparency about what AI does — and what it does not — is how trust is built, not just claimed.
| Role group | Agent | Function |
|---|---|---|
| Customer-facing | Codex operator | Customer support, refunds, technical help |
| Content | Copywriter | Page content and 5-language adaptations |
| Content | Research Analyst | Scientific paper ingestion and synthesis |
| Implementation | Coder | Site build and infrastructure |
| Implementation | UX Designer | Information architecture |
| Implementation | Visual Designer | Brand and visual canon |
| Compliance | Legal Counsel | Regulatory interpretation |
| Quality | QA Tester | Verification and testing |
| Operations | PM | Coordination and scope |
| Operations | Outreach | B2B prospect engagement |
| Operations | Curriculum Designer | Training methodology |
| Operations | Tree Steward | Cross-team coordination |
Each agent operates on Claude (Anthropic) under documented safety constraints and defined operational boundaries. AI agents do not access raw genetic sequence data; they process haplogroup labels and limited metadata only.
How We Govern Our AI
AI governance at yfull.ai is not a policy statement — it is a set of architectural choices enforced at every layer of our agent stack. Here is how it works in practice.
Task routing
Every type of customer interaction — support queries, technical questions, content requests — is routed to the appropriate AI agent by task type. No single agent handles all functions; each operates within a defined scope.
Escalation paths
When an AI agent encounters a query that exceeds its safe operating scope — privacy decisions, regulatory ambiguity, data subject access requests — it routes to a human Data Protection Officer per Article 22(3) GDPR human-intervention safeguard. This escalation path is architectural and cannot be bypassed.
Authority boundaries
AI agents execute within their operational zones. Actions affecting third parties or involving external commitments — outgoing messages, pricing changes, scope decisions — require human ratification before execution.
Safety rules
Each agent carries a fixed NEVER list: no fabricated data or statistics, no medical or clinical claims, no dark patterns, no skipping accessibility requirements. These constraints are not configurable at runtime.
Audit trail
Every factual claim in customer-facing content traces to a canonical fact reference in our fact registry. AI agents do not invent numbers, client counts, or citation data.
AI and human collaboration
We use AI for operational work that benefits from scale and consistency — content generation, research synthesis, compliance review, site implementation. Human roles are preserved for data protection oversight and for final authority on external-facing decisions.
EU AI Act Compliance
You are interacting with an AI system. yfull.ai uses AI agents to generate haplogroup historical context narratives and to handle service operations. This disclosure is provided in compliance with Article 50(1) of the EU Artificial Intelligence Act.
Permitted purposes. yfull.ai AI systems are used for:
- Historical-context narrative generation based on haplogroup data
- Genealogical interpretation support
- Service operations (coordination, compliance review, content authoring)
yfull.ai AI systems are not used for medical, clinical, or diagnostic decisions.
Provider: Genetic History S.L.U., CIF B24962573, Spain.
EU AI Act Article 50 disclosure requirements take effect on 2 August 2026. yfull.ai complies ahead of the effective date as part of its transparency-forward governance posture.
This disclosure is one of four AI-transparency surfaces on yfull.ai:
- Landing page: «You're interacting with AI» acknowledgment
- Terms of Use — «Use of AI» section
- Privacy Notice — §AI Processing
- This page (combined AI overview surface)
For detailed regulatory questions or data protection matters, see our Privacy Notice.
Contact Us
For general support and technical questions, see our support email. For data protection matters — access requests, complaints, DPO contact — see our Privacy Notice.
General support
Customer questions and technical help. A dedicated support email address is coming soon; until then, please use the DPO escalation path below for any urgent matter.
Data Protection Officer (DPO)
For privacy-related queries, data subject rights, and regulatory concerns: see our Privacy Notice for DPO contact details and data subject request process.