Security & Privacy Schedule
Architecture
• Resident information is intended to exist only in the active care-plan workflow and is not stored as a resident record by WhyCare.
• The person's entered name and preferred name are replaced locally in the browser before anonymised content is submitted to the WhyCare backend.
• The browser presents an anonymised preview and local privacy-pattern checks before AI submission.
• The backend sends anonymised/minimised content to the configured AI provider and returns the response to the browser without intentionally persisting the source text or generated care plan.
Application security measures
• HTTPS is required for production deployment and should be enforced at the hosting/platform layer.
• Passwords are stored using PHP's modern password-hashing facilities; raw passwords are not stored.
• Session cookies are configured HttpOnly and SameSite=Lax, and Secure in production.
• Server-side authentication and role checks protect authenticated/admin functions.
• CSRF tokens protect state-changing forms and API calls.
• Prepared SQL statements and input/output validation/escaping are used to reduce injection risks.
• AI/API secrets are held in server-side configuration/environment variables and are not exposed in browser JavaScript.
• Login attempts and password resets are rate-limited; reset tokens are single-use, time-limited and stored as hashes.
• Application logging is designed to use technical identifiers/status rather than resident care text.
Operational measures
• Administrator access is restricted to explicitly authorised admin accounts.
• Customer accounts can be suspended where security or misuse concerns arise.
• Usage records contain generation metadata/tokens/cost estimates rather than resident content.
• Contract records and signing audit information are retained separately from care-plan content.
Customer responsibilities
• Keep login credentials secure and limit them to authorised staff.
• Review the anonymised preview and remove unnecessary identifiers before generation.
• Do not paste resident data into support emails or tickets unless specifically requested through an agreed secure process.
• Maintain local device/browser security and sign out on shared devices.
Limitations
No internet service can guarantee absolute security or uninterrupted availability. WhyCare reviews its controls as the service develops and may update this schedule to reflect materially improved or changed measures.