Learn
AvailablePrivacy and Living People
How AINMAX thinks about privacy, living people, and safe presentation.Family history can include sensitive information. AINMAX treats living people and private facts conservatively by default.
What this means
- Living-person details should be protected unless the user has permission.
- Unknown living status should be handled cautiously.
- Frontend pages should not infer or reveal hidden facts.
How AINMAX supports this
- Privacy center and low-risk consent controls are accepted in production.
- Timeline APIs are auth-required and protect unauthenticated access.
- Visual states distinguish protected, demo, and planned content.
What is available now
- `/privacy/` read-only and low-risk consent controls are accepted.
- Unauthenticated privacy/consent APIs return authentication-required responses.
- Visual foundation avoids fake public/private data displays.
What is planned
- Authenticated privacy QA when approved credentials are available.
- Higher-risk consent domains only after separate planning.
- More detailed privacy education resources.
This page is educational and not legal advice. It does not replace jurisdiction-specific legal review for privacy, consent, or data protection obligations.