Frequently Asked Questions

The initial beta is designed for AncestryDNA-style raw DNA files. Support for additional consumer DNA providers is planned, but they are not part of the first public upload workflow.

No. DNA_CHECKS is not a sequencing laboratory and does not collect a biological sample. It interprets supported raw DNA data that you already obtained from another provider.

Additional provider formats are part of the planned direction. MyHeritage and other SNP-array formats can be added through dedicated input adapters, while whole-genome sequencing is intended to become a first-class input later.

Different providers use different file formats, marker sets, reference assemblies and conventions. DNA_CHECKS treats those differences explicitly rather than assuming that every raw DNA file is interchangeable.

The current report can include Origins & History, Genetic Curiosities, Important Clinical Findings, Medication & Pharmacogenomics, Further Evidence & Research Context, a Technical Evidence Appendix and source provenance.

Each section asks a different scientific question and relies on different markers and evidence. Consumer SNP arrays also measure only selected positions in the genome, so coverage varies substantially between clinical, pharmacogenomic, ancestry and trait analyses.

DNA_CHECKS is designed to fail cautiously. Evidence may be withheld, demoted or moved into supporting context when genotype coverage, variant identity, evidence quality or interpretation rules do not justify a stronger conclusion.

Accuracy depends on the type of result. DNA_CHECKS evaluates the data available in the uploaded SNP-array file and applies deterministic quality and evidence rules. However, a consumer SNP array is not the same as clinical sequencing or whole-genome sequencing, and important clinical findings may require independent confirmation.

Yes, the long-term model is to allow re-analysis when the knowledge base or report improves. Because uploaded raw DNA is not intended to be retained after processing, a future rerun would normally require you to upload the file again.

The Origins & History section compares your available DNA with reference populations using population-genetic methods. It contains separate ancient and modern comparison systems because those analyses answer different questions.

No. The current Ancient Origins section reports genetic affinity to dated ancient reference neighbourhoods within chronological windows. It does not claim that a stated percentage of your genome comes from a named ancient population.

No. A close reference indicates similarity within the comparison model. It is not proof of direct descent, tribal identity or membership of a historical population.

They indicate which modern reference populations are genetically nearby within the available population-structure model. They do not define nationality, ethnicity, citizenship or personal identity.

No. Clinical content in DNA_CHECKS is screening-oriented information derived from the available consumer DNA data and supporting evidence. It is not a clinical diagnosis.

Consumer SNP arrays are designed differently from clinical genetic testing. An important result may therefore need confirmation using an appropriate clinical-grade test before it is used in healthcare decision-making.

Pharmacogenomics studies how genetic variation can influence drug metabolism, response or dosing. DNA_CHECKS evaluates supported pharmacogenomic evidence where the uploaded genotype data provides sufficient coverage.

No. A DNA_CHECKS report is not a prescription and should not be used by itself to start, stop or change medication. Medication decisions should be made with an appropriately qualified healthcare professional.

The intended beta workflow uses the uploaded raw DNA only to generate the requested report. Once processing is complete, the raw DNA file is deleted from the processing workflow.

DNA_CHECKS is intentionally being designed around minimal retention. The raw DNA file is not intended to become a permanent account asset or a long-term project dataset.

Not by default. Uploading DNA for a report does not automatically authorise research reuse, AI training, advertising or product profiling. Any future programme involving voluntary data contribution would need to be clearly separate and explicitly optional.

No. The project model does not include selling genetic data or building advertising profiles from uploaded DNA.

The final beta retention period will be stated clearly before public launch. The aim is temporary secure delivery rather than indefinite online storage.

Yes. The public beta will include a route for privacy and deletion requests. The exact procedure will be documented in the Privacy Policy and Data & Security pages before real uploads are enabled.

AI does not determine which variants you carry, whether a genotype matches, whether clinical evidence reaches the report, or how ancestry comparisons are calculated. Those scientific decisions are made by the deterministic DNA_CHECKS pipelines.

AI can be used as an optional narrative layer to improve wording and explanation after the scientific result has already been determined. The underlying evidence remains locked upstream.

No. The deterministic report is the underlying product. AI-assisted wording is not required for the scientific analysis to run.

No. Uploaded DNA is not intended to be used for AI training as part of the standard DNA_CHECKS report workflow.

The planned beta price is £3 for one generated report. It is a one-off beta contribution rather than a subscription and helps support running costs and continued project development.

The final public processing estimate will be published once the beta job workflow has been tested under real conditions. The analysis engine itself runs locally and the first beta is intentionally designed for a modest number of reports rather than large-scale instant processing.

The upload workflow will validate supported files before processing as far as practical. Unsupported or malformed input should fail clearly rather than silently producing an unreliable report.

DNA_CHECKS is still being developed. The core analysis and report are usable, but provider support, public infrastructure, documentation and parts of the user experience will continue to evolve.

No. The current model is a small one-off beta fee per generated report. There is no planned requirement for an ongoing subscription.

DNA_CHECKS is currently an independently developed project rather than a large genetics company or health-tech platform.

Yes. Technical contributions, bug reports, scientific criticism, feature ideas and feedback are all part of the intended community direction of the project.

Yes. The Request a Feature page is intended specifically for this. Requests can include new traits, ancestry comparisons, DNA providers, report improvements or other useful additions.