People make clinical decisions.
The automated assistant supports scheduled conversations and organizes responses. Licensed clinicians interpret routed concerns and determine follow-up. AI does not diagnose, prescribe or independently call 911.
Security & trust
Trust starts
with clear answers.
Who provides care. Where information belongs. What the technology does. These should be easy to understand.
Keep private information private.
This website explains the service and provides contact and portal-access guidance. Medical records and authentication belong in the separate clinical environment. Please keep public inquiries free of medical details.
Make connection easier.
The scheduled voice call uses a mobile phone or landline. This website includes readable text, keyboard access, reduced-motion support, captions and a transcript. Accessibility is part of our website design.
This public website
Information and a first conversation.
The Sign in link helps visitors find their appropriate workspace. This marketing website does not authenticate patient accounts or display clinical records.
- HTTPS and browser security headers.
- Locally served fonts, imagery and overview media.
- No advertising pixels or analytics scripts.
- No medical-record uploads, payments or AI chat.
The clinical environment
A separate layer of responsibility.
Clinical services require the appropriate licensed partner, consent, privacy documentation, access controls and operational safeguards before enrollment.
Clinical partnership inquiries are welcome. BAAs, insurance, risk assessments and applicable clinical arrangements must be verified for the actual services involved.
Our standards and responsibilities.
HIPAA
Clinical privacy requirements
Clinical operations require documented safeguards, risk assessment, policies, training and appropriate vendor agreements. A website design alone does not establish HIPAA compliance.
AES-256
Clinical infrastructure design
Our clinical security requirements specify AES-256 encryption for stored data and TLS for data in transit. The public website serves information over HTTPS. Contact our team for information about clinical-system safeguards.
WCAG 2.1 AA
Accessibility baseline
Our website design follows WCAG 2.2 AA guidance, which builds on WCAG 2.1 AA. Features include keyboard navigation, readable contrast, captions and reduced-motion support. Visit our accessibility page for available features and help with any access barriers.
Medicare enrollment
Independent clinical partner responsibility
KindlyMoments is an administrative and technology organization, not the Medicare billing provider. Each participating clinical provider must hold their own applicable enrollment and credentials. Contact us to discuss a clinical partnership.
Business Associate Agreements
Required before protected data processing
Appropriate agreements and coverage must be verified for each actual service and vendor before protected health information is processed. Ask our team about the agreements and security documentation relevant to your partnership.
Website response is different from care availability.
Our website check requests a small status file from your browser. It confirms that the website responded to that request. It is not an uptime history or a check of clinical availability, calls or patient safety.
Raise a security or privacy question.
Email help@kindlymoments.com with a general description and public page address. Do not include passwords, tokens or private health information.
Discuss partnership due diligence