Skip to content
GeroQubit, de novo longevity drug design
Security, data & IP

What we build on, and what stays yours.

Precise about what is in place today versus available on request. If something here matters to your programme, ask. We would rather scope it than overstate it.
Where your data goes

One job, one boundary, nothing retained downstream.

You send
A target and a scope

Which programme, which tissue, how many candidates. Encrypted in transit.

Runs in an isolated job
Your inputs, your job only
  • Per-job isolation
  • Encrypted at rest
  • Deterministic, same inputs, same outputs
  • Registration hash per candidate
You get back
Candidates you own

Structures, routes, scores and provenance, exportable as SDF or CSV, deletable on request.

What never happens
Your inputs never train a model
Your candidates never reach another customer
No fine-tuning on your chemistry, ever
No retention after you ask for deletion

Your IP stays yours

Now

Your targets and candidates are yours. Never reused for another customer.

We don’t train on your inputs

Now

Your submission runs your job. No training, no fine-tuning.

Encrypted, isolated, deletable

Now

TLS in transit, encrypted at rest, deleted on request. SOC 2 is roadmap, not claimed.

Every result reproduces

Now

Registration hash per candidate. Any result audits from its inputs.

Cloud, VPC or on-prem

On request

Managed cloud today. VPC and on-prem scoped per engagement.

NDA + DPA available

On request

Mutual NDA and DPA on request. Internals reviewable under NDA.

Research-use

GeroQubit generates hypotheses to support medicinal chemistry and target evaluation. It is not a medical device and does not provide clinical, diagnostic, or treatment advice; all output requires independent scientific and regulatory validation before use.

Sign upAsk a security question