Privacy
Data use should be visible, limited, and boringly clear.
KRENOS stores account data, sessions, and AI usage metadata in our own Postgres backend. App inputs are processed to produce results; health-style inputs should not be treated as medical records or professional advice.
What We Store
- Account identity: email, display name, role, and sign-in provider.
- Security data: hashed session tokens and authentication metadata.
- Usage data: app slug, model/provider label, status, input size, output size, and timestamp.
- Operational audit events as the backend expands.
What We Avoid
- We do not store raw session tokens.
- We do not intentionally store full healthcare prompts by default.
- We do not claim medical diagnosis, triage, or treatment decisions.
AI Providers
AI calls are routed server-side through the Krenos AI Gateway. The active provider is configured by the server and may change as the platform evolves. Public model labels should reflect what is actually configured.