Scoped access
Portal navigation is designed around authenticated and role-aware destinations.
Portal navigation is designed around authenticated and role-aware destinations.
The demonstrated report experience does not expose unrestricted public sharing.
The frontend repository does not ship with personal genotype or laboratory result data.
This interface demonstrates careful access patterns without making unverified claims about certifications, encryption, hosting, or infrastructure.
The interface shows account gates, role-aware navigation, and privacy-conscious copy. These are product-design boundaries, not evidence of a completed security program.
This preview does not claim a particular encryption standard, certification, audit result, laboratory accreditation, incident-response capability, or regulatory compliance status.
Before launch, the operating team should document architecture, access control, secrets management, encryption, monitoring, backups, incident response, vendor risk, retention, and secure deletion.
A verified security contact and vulnerability-reporting process should be published after operational review. Until then, the contact form is only a demonstration of that handoff.
The contact experience demonstrates how policy and account questions can be routed.
Contact Strandly