Understand heritage data
Use careful documentation to plan trustworthy family and archive workflows.
FOR BUSINESS
Public insight content is informational and not a live marketplace module.
Analytics concepts remain informational unless separately implemented.
Build and protect your brand reputation.
Integration documentation is available; SDKs, webhooks and OAuth are planned.
Verification concepts require accepted permissions, provenance and review.
Use careful documentation to plan trustworthy family and archive workflows.
Preserve provenance, permissions and transparency before publishing claims.
Use accepted documentation and review processes before expanding automation.
API documentation exists; production integrations need their own accepted phase.
Sensitive data areas require encryption, audit boundaries and explicit approval.
USE CASES
Plan source catalogs, collection notes and provenance-safe public education.
Document governance, permissions and data residency before operational use.
Support careful genealogy work with citations, confidence and review trails.
Preserve stories and context without making medical or legal claims.
Teach source literacy, chronology and privacy-aware research practices.
Plan transparent heritage workflows without activating public sharing by default.
Future organization workflows should be scoped, reviewed and accepted before activation.