Clients
Request their own journeys after identity is verified. Any family access must identify the recipient and permitted information.
carewayPRIVACY, PERMISSIONS & TRUST
Clear permission.
Thoughtful care.
Understand who may act, what information is requested, and when a permission request ends.
Return to fictional loginsDevelopment rehearsal · Fictional details only. Real signup and identity verification are not enabled. This is not a HIPAA authorization, Notice of Privacy Practices, legal signature or grant of access. The live service is not represented as HIPAA compliant.
Who is authorized to do what?
Representatives & family
Family status alone does not grant access. Identity, legal authority or the applicable basis for sharing must be verified. Access must stay within that authority.
Workers
Explicit account grants and assigned jobs define private access. Profile roles, phone numbers and this form cannot create a grant.
Owners
Manage their own operation and review authority. Ownership does not automatically authorize every disclosure or activate a worker’s location.
MULTIPLE PEOPLE. CLEAR RESPONSIBILITY.
People authorized to help.
Try adding several fictional representatives for one client. ID establishes identity; client designation or legal authority is a separate review. These sample checkboxes cannot grant access to private records.
Fictional browser roster only. Do not upload a real government ID. Secure ID upload, real verification and saving verified people to real client accounts are not enabled yet.
Production reviews must use trusted reviewer accounts and a server-enforced audit history. A typed reviewer name and browser checkbox are not proof. Verified people must later be bound to the correct real client account, permission scopes, expiry and revocation checks.
Practice your signup permissions.
Choose each scope separately. Nothing is preselected. These requests remain pending verification and never override server access checks. AI chat, voice processing, messages and tracker visibility each keep their separate choices.
Your rehearsal receipts
Notice version: careway-development-2026-10-15-v1. Expiry and withdrawal do not erase the original record. Private history shows the latest 50 requests; the recorded role remains self-declared.
No receipts loaded in this view.
Building toward HIPAA readiness.
Careway uses encrypted private record contents, scoped worker APIs, activity records and separate processing choices. A production HIPAA program also requires an applicability assessment, documented risk analysis, policies, workforce training, incident response, recovery and retention controls, and appropriate vendor agreements. Encryption and a consent checkbox alone do not establish compliance.
Before real client or medical information is accepted, Careway needs verified identities and authority, an approved privacy notice and authorization process, a confirmed legal basis for each use or disclosure, and completed operational and vendor safeguards.