Terms of use

Your account

Provide accurate account information, keep credentials and recovery codes secure, promptly revoke any exposed API key, and set appropriate project access, expiration, and monthly route and AI-action caps for every automation key. You are responsible for activity under your account. Authenticator MFA is required before starting a paid subscription. Flygon LC cannot recover authenticator or recovery codes from their stored form, so contact support if every second factor is lost. Paid subscriptions must be purchased by an adult or authorized organization.

Your data and permissions

You retain ownership of family trees, notes, files, and private DNA research metadata you enter. You give Flygon LC the limited permission needed to host, process, back up, and return that data as part of GeneaRoute. You must have the right to submit the data and must respect the privacy of living people and genetic relatives.

Private project invitations

A project owner may invite another person by email as an editor, contributor, or viewer. Invite only people authorized to access the project, choose the least access they need, and revoke access promptly when it is no longer appropriate. An invitation activates only for a GeneaRoute account that verifies the exact invited address. Pending invitations expire after 14 days. Project owners are responsible for collaborators' access to living-person, DNA, citation, media, and other private research data.

Professional Engagement Ledger

The Professional Engagement Ledger is a researcher-entered project-management record, not an invoice, engagement agreement, time clock, legal record, or verification that work was performed or billable. Project owners are responsible for accurate scope, time, billable flags, client authorization, retention, exports, configured event-hook recipients, and any invoices or contracts created outside GeneaRoute. Use a non-identifying client or matter label when a full name is unnecessary, and do not enter payment-card data.

Review links and family suggestions

You may create an expiring, unlisted address that lets someone review a sealed, privacy-filtered project snapshot and submit a private correction, memory, or source without an account. New links freeze the shareable packet when created and provide a SHA-256 fingerprint plus JSON download. The fingerprint detects changed snapshot content; it does not prove a historical claim, identify the viewer, or replace your review. You are responsible for choosing recipients and revoking a link sent to the wrong person. GeneaRoute excludes living people and private material according to the visibility settings described in the workspace, but you should still inspect the preview before sharing. Visitors must have the right to share their submission and should not include sensitive details about living people.

Responsible use

Do not use GeneaRoute to stalk, harass, discriminate, expose living people, enter DNA match details without appropriate authority, defeat provider controls, scrape beyond permitted limits, upload malware, disrupt the service, or republish restricted data. Do not upload raw genotype files because GeneaRoute is not designed to store them. Do not configure a webhook destination you do not control or use event delivery to probe networks, evade access controls, or send data to an unauthorized recipient. Follow each connected provider's license and terms.

Research, family, DNA, and AI results

Matches, Research Watch alerts, relationship paths, Connection Explanations, saved connection research plans, Evidence Gap Queue priorities and plans, Evidence Quality Matrix findings and plans, Evidence Maps, Proof Standard Workbench assessments and tasks, possible contradictions, tree-integrity findings, confidence signals, family-submitted suggestions, DNA relationship hypotheses, documentary DNA correlations, Evidence Q&A answers, transcriptions, and document leads may be incomplete, misleading, or wrong. An Evidence Q&A source binding records which saved source the model referenced; it does not make the statement or source true, reliable, independent, or sufficient. The evidence-snapshot hash detects whether the exact minimized input changes, but it is not a proof certificate. Same-name profiles may be different people. DNA metadata is one evidence layer, not automatic proof. A recorded or explicitly biological tree route does not prove genetic inheritance, segment identity, a continuous paternal or maternal line, or that an entered cM value supports the route. Source, information, evidence, and shared-origin classifications are entered by the researcher. GeneaRoute does not infer that a record or conclusion is reliable from those labels. An Evidence Map edge shows a recorded project link; it does not establish source independence, reliability, historical truth, or a proved relationship. Saving a Connection Explanation creates a private unproven hypothesis, route context, and tasks. Saving an Evidence Gap plan creates private source-finding tasks for currently unsourced claims. Saving an evidence-quality or proof-standard plan creates deduplicated private tasks for documentation elements that do not pass the current deterministic checks. These actions do not add or change a person, fact, relationship, citation, confidence value, hypothesis, conclusion, or public profile. A five-of-five workbench result means ready for qualified human review, not certification that a conclusion meets the Genealogical Proof Standard or is historically true. Research Watches, Connection Explanations, Evidence Q&A, Evidence Gap audits, evidence-quality assessments, proof-standard assessments, tree-integrity checks, family suggestions, Evidence Lens, and document extraction never apply a genealogical claim or relationship automatically. Document-to-tree review changes the private tree only after the user matches the affected people and explicitly accepts the quoted candidate. Verify every lead against appropriate documentary and genetic evidence before saving, publishing, or making consequential decisions.

Subscriptions and cancellation

Paid plans are sold by Flygon LC and billed in advance through Stripe. Subscriptions renew monthly until canceled. Customers can manage or cancel through the Stripe billing portal in the workspace. Cancellation stops future renewals and access continues through the paid period unless Stripe or applicable law requires otherwise.

Refund requests

If a first charge was accidental or the paid service was materially unavailable, contact genearoute@flygonlc.com within seven days. Refund requests are reviewed in good faith and do not limit rights required by law.

Usage limits and commercial access

Plan limits shown on the pricing page apply to routed searches, recurring Research Watches, AI research actions such as briefs, Connection Explanations, and private document analyses, projects, imports, Tree Time Machine checkpoints, collaborators and pending invitations, Professional Engagement Ledger changes, open agent change sets, Genealogy Event Hook endpoints, and keys. Each automated watch check consumes one routed search. Commercial API use and creating or changing a Professional Engagement Ledger require the Professional plan. Existing ledger data remains readable, exportable, and deletable after a downgrade. We may rate-limit abusive or unusually costly traffic and will try to provide clear upgrade or retry information.

Third-party services

Stripe, Railway, Vercel AI Gateway, model providers, and genealogy providers are independent services with their own terms. Provider availability can change. GeneaRoute will not present an unavailable connector as live.

Identity conclusions and merges

The Identity Resolution Lab organizes recorded agreements, conflicts, gaps, citation coverage, relationships, and associate context, but it does not determine that two records describe the same person. You are responsible for reviewing original records and writing an accurate reason statement. A saved conclusion can become stale when project evidence changes. GeneaRoute preserves conflicting claims and keeps an undo snapshot when its web workspace performs a reviewed merge, but later tree edits can prevent automatic undo.

Provider identity mappings

A reviewed provider mapping records your conclusion that one saved provider profile does or does not describe one person in your private tree. Provider confidence scores, evidence counts, profile data, and automated comparison signals are not proof. GeneaRoute does not automatically copy a provider claim, citation, or relationship into the tree. Recheck a mapping when GeneaRoute marks its evidence snapshot stale.

Source integrity checks

A source fingerprint can show that a cited public URL became unavailable or that its normalized response changed. It cannot determine why the page changed, whether an archived copy exists, whether the cited passage changed, or whether the source is accurate. Review the live or archived evidence before accepting a new baseline. Do not use monitoring to probe private networks, bypass access controls, or exceed a source website's permitted use.

Tree checkpoints and restore

A Tree Time Machine checkpoint is a private review and recovery aid, not a complete account backup. It covers the core tree and citation structure described in the workspace, but not uploaded files or other non-tree data. You are responsible for naming checkpoints, reviewing every comparison, giving an accurate restore reason, and exporting important work before major imports, automated edits, or collaboration sessions. Guarded restore updates matching records only. It refuses after records or citation links have been added or removed because silently deleting later work would be unsafe. A successful restore does not prove that the earlier genealogy was correct and does not undo changes to excluded data.

Agent change sets

Agent change sets are proposed work, not verified genealogy. An API key can stage and inspect a fingerprint-sealed batch but cannot accept or reject it. GeneaRoute displays the proposing key, every submitted field, and citation coverage for new facts and relationships. A signed-in owner or editor is responsible for checking every operation, source, quotation, relationship direction, privacy setting, living-person detail, and uncited-claim warning before entering a review reason. A valid content fingerprint shows that the stored proposal matches the submitted batch, not that its genealogy is true. Acceptance is atomic but does not prove that the applied claims are correct. Rejection leaves the tree unchanged. Do not give an agent access to material you are not authorized to process.

Genealogy Event Hooks

Only a project owner may create an outbound event endpoint. You are responsible for controlling the destination, protecting the one-time signing secret, checking signatures and timestamps, deduplicating event identifiers, securing downstream logs, and deleting or pausing an endpoint that is no longer authorized. Event payloads are deliberately metadata-only, but identifiers and change timing can still be sensitive. GeneaRoute retries temporary failures and may automatically pause an endpoint after repeated failures. Successful delivery means the destination returned an HTTP success status, not that it processed or retained the event correctly.

Beta service and availability

GeneaRoute is an actively developed beta. Features can change, and uninterrupted availability is not promised. We may suspend access to protect users, providers, or the service.

Warranty and liability

To the extent allowed by law, the service is provided as available without implied warranties. Flygon LC is not responsible for decisions based on unverified genealogy, third-party content, provider outages, or indirect losses. Any liability will not exceed the amount paid for GeneaRoute during the prior three months, except where law does not allow that limit.

Ending use

You may export and delete private account data from the workspace after canceling an active subscription. Flygon LC may terminate accounts that materially violate these terms. Provisions concerning ownership, payment, disclaimers, and liability survive termination where applicable.

Contact and changes

Questions can be sent to genearoute@flygonlc.com. Material changes will be posted here with a new effective date.