Security & trust
Your care visibility should feel safe.
Kinse is built for respectful handling of sensitive day-to-day information. Here is how we protect it, and what we never claim to be.
Responsible practices, explained plainly
We use industry-standard encryption in transit and at rest, access controls aligned to care circle roles, and monitoring designed to catch issues early. Formal attestations (for example SOC 2) will be listed here when complete. We do not claim badges until verified.
You decide who sees what
Caregivers, invited helpers, and the person receiving calls each have boundaries defined in product settings. We explain, in plain language, what we collect, why, and how to request changes or deletion subject to legal requirements.
Security practices
How we protect data at each layer.
Encryption
Data encrypted in transit and at rest using modern standards.
Access controls
Role-based permissions for care circle members; least-privilege by default.
Monitoring
Systems monitored for anomalies; incidents handled under documented procedures.
Secure development
Security considered in design, review, and deployment, not bolted on after.
Important limits
Kinse is not an emergency response service. It does not diagnose conditions or replace clinicians. For emergencies, call local emergency services immediately.
Questions about security?
Reach out or read our policies.