You stay in control
You decide what we can do with your data, and you can change your mind.
Trust centre
Your data,your choice.
Genomic data is deeply personal. That is why Spoke puts you in control of consent, storage, downloads, retention, and deletion from the start.
We ask before use
We only use your data for the service you consented to, or as required by law.
We protect and encrypt
Your data is encrypted, stored carefully, and accessed only when needed.
You can request deletion
Request raw-file deletion from active systems, with backup caveats explained clearly.
How your data is protected
From upload to deletion, privacy is built into every step.
Upload with consent
You decide what you share and what we can do with it.
Protected analysis
Your data is encrypted and used only as you allow.
Reports and deletion
See who accessed your data and request deletion.
Review before release
Reports are reviewed before they are made available.
Privacy-protective
Privacy by design, security in practice.
No sale of personal data
We never sell your personal or genomic data.
Deletion support
You can request deletion of raw genome files.
Transparent and accountable
We publish material trust and security updates.
Security architecture
Your data moves through controlled steps.
The Trust centre makes the data lifecycle visible without turning privacy into paperwork. These are the customer-facing steps behind upload, analysis, report release, and deletion.
We confirm what you want help with before any genome file is used.
Genome and context files are uploaded through the portal, not sent as email attachments.
New files are checked for format, size, checksum, provider, and obvious unsafe content before analysis.
Identity records, raw genome files, derived results, reports, and audit logs are kept apart.
Reports are released only after review, with provenance for the file and workflow used.
You can view reports, request downloads, change consent, and request raw-file deletion through controlled routes.
Consent before processing
The portal records decision-support consent before case submission, and upload and workflow gates refuse processing when required consent is absent.
Pseudonymous case handling
Files and reports are stored against case and subject identifiers rather than names in object paths, keeping identity data away from genomic artifacts.
Encrypted artifact storage
Uploaded files, context notes, and report artifacts are encrypted before storage and kept away from public website data.
Portal-only delivery
Released reports are served through the authenticated portal with short-lived download tokens, rather than being attached to email.
Deletion support
Genome files can be deleted from the case view when processing is not running. The case keeps audit and report state so deletion does not break traceability.
Audit trail by default
Case creation, file upload, consent, compatibility checks, release, download, and deletion actions write audit events with actor and target metadata.
Data controls
What you can see and control.
The useful version of trust is operational: what we collect, what we avoid, how your report is released, and what choices you can change later.
Portal access is authenticated, and case records are not shared across unauthorized users.
Upload links are short-lived and bound to expected file rules. VCF or unusual files receive extra review.
Reviewer approval is required before release, and artifacts are only downloadable after the case reaches released status.
The report workflow keeps raw files, context, derived results, and released artifacts as separate records with explicit status.
Service delivery and secondary research use are separate choices. Research reuse requires separate consent.
Reports are framed as prevention and discussion support, not diagnosis, medication instructions, or clinical genetic testing.
Transparency
Trust claims stay tied to evidence.
Consent before processing, private portal delivery, encrypted storage, upload-policy checks, release review, deletion support for raw genome files, and no research reuse without separate consent.
Customer MFA or step-up checks before downloads, completed subprocessor details, backup restore evidence, external security review, and dated transparency reporting once production intake begins.
We do not claim certification, HIPAA coverage, absolute security, anonymous genetic data, or zero vendor involvement unless there is specific evidence for that claim.
Trust centre policies
Policy pages for the details that matter.
The public page stays short. These pages hold the practical detail: privacy, data controls, research use, subprocessors, security contact routes, and government request handling.
Privacy summary
A plain-language view of what Spoke DNA collects, what it avoids, and how customers can control genomic report data.
Security overviewA plain-language view of how Spoke protects uploads, reports, access, and deletion routes.
Data controlsHow upload, report delivery, retention, deletion, export, and consent changes work for customers.
Research and secondary useThe default position is service delivery only. Research or model training requires a separate opt-in.
SubprocessorsA live register of vendors that may process data to provide the service.
Vulnerability disclosureHow security researchers and customers can report suspected vulnerabilities.
Law enforcement requestsHow Spoke DNA responds to government and law-enforcement requests.
For partners and assurance reviews
Read security overviewDetailed data-zone maps, NIST/Cyber Essentials operating controls, incident classes, evidence registers, launch gates, and restore-test records are maintained as internal assurance material rather than crowding the customer page.
This page describes product and operating controls. It is not legal, medical, clinical, or regulatory advice.
Request pilot access