Trust & Safety
AvailableDNA and Consent
A safety-first explanation of DNA boundaries and consent language.DNA information can be highly sensitive. AINMAX treats DNA-related work as a high-risk domain that requires explicit consent, privacy boundaries, and careful implementation.
What this means
- DNA Matching is optional and uses a separate, revocable purpose-specific consent from Vault storage.
- Raw DNA, genotype data, and private genetic details must not appear in public Resources pages.
- Consent language should be specific and not bundled with unrelated choices.
How AINMAX supports this
- The protected Matches workspace shows only real, authorized, pseudonymous broad estimates.
- Privacy/consent foundation distinguishes low-risk account preferences from high-risk DNA features.
- Timeline and dashboard pages must not expose raw DNA or genotype data.
What is available now
- The public DNA guide and protected DNA Vault remain separate from protected DNA Matching controls.
- DNA matching consent and segment-detail consent are distinct high-risk purposes, not low-risk preference choices.
- Unauthenticated protected APIs remain authentication-required.
What is planned
- Additional provider formats only after separate validation.
- Cross-build conversion and federated matching remain unavailable.
- Medical, ethnicity, trait, and law-enforcement uses remain unavailable.
This public page provides no match result, medical advice, health or ethnicity interpretation, raw genotype detail, or legal advice.