Privacy Policy
Last updated: March 2025
Humsana is built to infer context without capturing content. We design our systems so sensitive data is never collected in the first place.
What We Do Not Collect
- Keystroke content or text input
- Messages, prompts, or screen data
- Audio, video, or biometric identifiers
- Personal identifiers (name, email, phone)
- Credentials, passwords, or tokens
What We Observe
Humsana observes behavioral timing signals only, such as:
- Keystroke timing intervals (not characters)
- Typing rhythm and correction frequency
- Scroll velocity and dwell time
- Interaction and task-switch timing
How Data Is Processed
Developer Tools: Processing occurs entirely on-device. No raw data is transmitted. Local audit logs (if enabled) live in ~/.humsana/.
Partner SDK: Signals are processed in real time. Only aggregated, probabilistic indicators are returned. Raw streams are not retained.
What Partners Receive
- Stress, hesitation, or readiness indicators
- Confidence-weighted scores
- Short-horizon behavioral context
What Humsana Is Not Used For
- Surveillance or monitoring
- Employee tracking or scoring
- Psychological or medical diagnosis
- Law enforcement or intelligence use
Compliance
Humsana is designed to align with GDPR and CCPA. Because we avoid collecting personal data by design, compliance risk is minimized.
Contact
Email: contact@humsana.com