ReadyCare Systems logo ReadyCare Systems
Agency Login
Draft — pending legal review. This document was drafted to give prospective and current agencies an honest, real starting point, not left blank while a real Terms of Service exists nowhere. It has not been reviewed by an attorney and should not be treated as final or legally binding until it has. Effective date will be set once reviewed.

Terms of Service

ReadyCare Systems, LLC. Draft version, not yet effective.

1. Who this agreement is between

These Terms of Service ("Terms") are between ReadyCare Systems, LLC ("ReadyCare Systems," "we," "us") and the agency or organization that signs up to use the ReadyCare Systems platform (an "Agency," "you"). ReadyCare Systems is a whitelabeled clinical-documentation and agency-operations workspace, provided as software-as-a-service.

2. What ReadyCare Systems is — and isn't

ReadyCare Systems provides clinical forms, client record-keeping, visit documentation, a shared document library, secure staff messaging, and time tracking, under your agency's own branding. ReadyCare Systems is not a certified Electronic Medical Record (EMR) platform and does not represent itself as one. Features described as "Planned" or "Roadmap" on our website are not currently available; only features labeled "Active" are live today. See our Roadmap and Security & honest product boundaries pages for the current, honest state of the product.

3. Onboarding, accounts, and access

ReadyCare Systems is onboarded directly, agency by agency — there is no self-service signup or automatic account creation. Your agency's administrator(s) are responsible for managing which staff members have accounts, and for promptly notifying ReadyCare Systems when a staff member's access should be revoked (e.g., they leave your organization). You are responsible for keeping login credentials confidential and for all activity under your agency's accounts.

4. Protected Health Information (PHI) and the BAA

If your agency will enter real client data that constitutes Protected Health Information under HIPAA, a Business Associate Agreement ("BAA") between your agency and ReadyCare Systems, LLC must be signed before that data is entered. The BAA (not this document) governs how PHI is handled, in accordance with HIPAA's Privacy, Security, and Breach Notification Rules. Testing or demonstration use of the platform must use fake/demo data only, never real client names, dates of birth, diagnoses, or other PHI, until a BAA is on file.

5. Fees and payment

Fees are per-seat, agreed directly with your agency during onboarding (see our Pricing page for representative, non-binding starting figures). Payment is currently collected manually, outside of any automated billing system built into the ReadyCare Systems application itself — your specific billing arrangement, cycle, and method will be confirmed in writing separately from these Terms. Fees are non-refundable except as otherwise agreed in writing.

6. Acceptable use

You agree not to: use the platform for any unlawful purpose; attempt to access another agency's data; attempt to circumvent or probe the platform's access controls or security; or use the platform to store or transmit data you are not authorized to hold. We reserve the right to suspend access for a violation of this section.

7. Data ownership and portability

Your agency owns the client and clinical data it enters into ReadyCare Systems. Upon termination, your agency's own administrators retain read access to your data for a reasonable transition period to be confirmed at the time of termination — see our Privacy Policy and, once entered into, your agency's BAA for specifics. Client records and clinical submissions cannot be deleted through the application itself by design; this protects the integrity of the clinical record but should be understood as a real product characteristic, not just a policy.

8. Service availability

ReadyCare Systems is provided on an "as available" basis. We do not currently offer a formal, contractual uptime Service Level Agreement (SLA) — this is a real, honest limitation as a small operation, not something to overclaim. Real infrastructure protections that ARE in place today (multi-datacenter replication, scheduled backups, point-in-time recovery) are described on our Roadmap page.

9. Limitation of liability

[Placeholder — standard SaaS limitation-of-liability language, capping damages and excluding indirect/consequential damages, belongs here. This needs an attorney's specific language for Ohio/applicable jurisdiction, not a generic template pasted in without review.]

10. Termination

Either party may terminate service by written notice, subject to any minimum term agreed during onboarding. Sections of these Terms that by their nature should survive termination (data ownership, confidentiality, limitation of liability) continue to apply.

11. Changes to these Terms

We may update these Terms as the product and business evolve. Material changes will be communicated to agencies directly, not just posted silently.

12. Governing law

[Placeholder — governing law/jurisdiction clause, to be confirmed with an attorney.]

13. Contact

Questions about these Terms: readycare@londo.tech.