Treat the export as a long-lived personal record

The first decision is whether you need to share raw DNA data at all. A provider's summary report may answer a narrow question, but a portable raw file preserves the option to revisit results as tools and research improve. That flexibility also creates privacy and consent responsibilities.

Create a simple custody log

Download directly from the provider account, preserve the original filename and metadata, and keep one encrypted backup. Record the provider, date, format, and build if known. Avoid ordinary email and public file-sharing links for transfer.

Before uploading, ask what data is retained, whether you can export or delete it, whether it is used for model training or research, and how analysis results remain tied to the original source. Make a deliberate choice for each service and record every upload.

A storage setup that is easy to maintain

Create one encrypted folder for original genomic files and a separate folder for reports produced by other tools. Use filenames that include the provider and download date without exposing the contents in a public sync path. Keep one encrypted backup under your control.

A small text note can serve as a custody log. Record the service, upload date, purpose, data shared, account email, and deletion status. This becomes valuable months later when privacy terms change or you decide to close an account.

Consent questions that deserve a direct answer

Storage and analysis are separate purposes. Research, product improvement, advertising, and model training are additional purposes. Read whether each is required, optional, or controlled through a separate consent setting.

Account deletion and data deletion can also differ. Look for language covering source files, derived results, backups, biological samples, and third-party processors. Save a copy of the terms that influenced your choice.

  • What is required to deliver the service?
  • Which secondary uses are optional?
  • Can consent be withdrawn later?
  • What survives account closure and for how long?

Before sharing raw DNA data

  • Confirm the service supports the exact format and reference assembly
  • Use a unique account password and multifactor authentication where available
  • Read retention, research, model-training, and deletion terms
  • Upload the minimum file needed for the stated purpose
  • Add the upload to your custody log

Keep source data separate from interpretations

WellNizz supports a source-based health data model. Uploaded genetics, biomarker, and wearable inputs remain distinct from derived observations and dashboard outputs. Apps and agents can trace a finding to its origin and method.

Consider the privacy interests of relatives

Genetic information can implicate family members as well as you. Consider their interests before sharing ancestry or hereditary information, and read every service's data policy before upload.

Editorial sources

Read the primary guidance

These sources support the technical and health boundaries in this article. Provider prices, availability, and product terms should always be checked at the provider before purchase.

Questions, answered

FAQ

What format is raw DNA data?

It varies. SNP-array providers often export a text file; sequencing providers may provide VCF, VCF.GZ, BAM, CRAM, or FASTQ files.

Should I upload raw DNA data to every app?

No. Upload only when the purpose, supported format, privacy controls, and deletion path are clear.