Terms of Service
Shared terms for the app2care website, platform, developer integrations, and CareFlow.
Last updated:
1. Covered services and agreements
These Terms of Service govern use of the public app2care website, app2care platform and developer integration services, and CareFlow when provided by app2care, inc. (app2care, we, us). By using these services, you agree to these terms. If you do not agree, do not use them. A product not named here is not automatically covered.
If your organization has a separately executed agreement with app2care, that agreement controls any conflict for the services within its scope. A business associate agreement (BAA) controls protected-health-information obligations where applicable, and mandatory law continues to apply. These terms do not replace a required BAA, patient authorization, or healthcare-provider privacy notice.
Independently operated marketplace apps, electronic health records, and other third-party services have their own terms. Their presence in the platform does not make app2care their operator.
3. Permitted use and restrictions
Subject to applicable agreements and permissions, you may use the services for their intended lawful business, integration, and healthcare-support purposes. Do not bypass access controls, access another organization’s information without authority, impersonate others, introduce malware, send spam, interfere with service operation, or use the services in violation of law or another person’s rights.
Do not put patient records, passwords, or integration secrets in public forms, app listings, screenshots, or ordinary support email. Use only the channels and environments authorized for the information involved. Do not send identifiable patient data to a sandbox unless your agreement and its approved configuration expressly permit it.
4. Customer data and privacy
You and your organization retain your rights in information and content you provide. You grant app2care the limited permission needed to host, process, display, and transmit that information to provide the authorized services, subject to applicable agreements and law. This permission does not override restrictions on health information or grant a right to unrelated advertising, sale, or model training.
You are responsible for having the rights, instructions, permissions, and patient authorizations required to submit or disclose information through your use of the services. Where a BAA is required, it must be in place before the relevant processing begins. Our Privacy Policy explains handling of information across the covered services; it is not patient consent or a substitute for a BAA.
5. Developers and integrations
Developers are responsible for their apps, submitted listings, integration behavior, published privacy practices, security contacts, and compliance with applicable technical requirements. Keep information accurate and obtain permission for submitted content. Content approved for public publication may be displayed in the App Library.
Protect credentials and webhook endpoints, respect granted scopes and organization/environment boundaries, validate information received, and send only information authorized for the intended recipient. App review or listing does not transfer responsibility for the developer’s app to app2care or guarantee legal compliance, security, availability, or clinical suitability.
Third-party integrations depend on the relevant providers and customer configuration. Access may change when credentials, permissions, subscriptions, or provider interfaces change.
6. Healthcare organizations and CareFlow
CareFlow supports clinical-order, enrollment, monitoring, communication, documentation, eligibility, and billing workflows. Authorized healthcare professionals and organizations remain responsible for care decisions, patient identity, required consent, appropriate access, reviewing records and automated calculations, and the accuracy of claims and submissions.
Software output is assistance and requires appropriate professional review. Neither public content nor service output guarantees a clinical outcome, insurance coverage, reimbursement, or regulatory compliance. You must verify applicable clinical, coding, payer, documentation, and recordkeeping requirements for your circumstances.
The services are not an emergency response service. Do not rely on them for urgent intervention; contact local emergency services when needed. Using the software does not itself establish a clinician-patient relationship with app2care.
7. Access, pricing, and service commitments
An access request expresses interest and does not create a paid subscription or guarantee approval. Use may require verification, onboarding, a service agreement, and additional configuration. Fees, payment obligations, service levels, support commitments, and early-access benefits are those expressly agreed for the relevant service.
Public descriptions and catalog listings do not amend an existing agreement. These terms do not independently establish a charge, payment-processing arrangement, or guaranteed service level.
8. Ownership and third-party materials
app2care and its licensors retain their rights in the services, software, branding, and documentation. Your permitted use does not transfer ownership. Keep ownership notices intact and do not use app2care branding to imply an endorsement without permission. Third-party names and materials belong to their respective owners.
You may view public information, share links, and make reasonable copies for internal evaluation. Rights to use platform software and integrations remain subject to your access permissions and applicable agreements. Third-party apps and content remain subject to their operators’ terms and policies.
9. Suspension, ending access, and records
Subject to applicable agreements and law, we may restrict access to address security risks, unauthorized use, violations of these terms, or service discontinuation. Contractual notice, service-continuity, and termination obligations continue to apply.
Customer organizations should plan for continuity of care and required recordkeeping. Ending a user’s access does not automatically delete clinical, billing, audit, or previously delivered records. Return, export, retention, or deletion of customer information is governed by the applicable service agreement or BAA and law. Contact us to coordinate available offboarding options; these terms do not promise an export feature that is not available in your service.
10. Warranties and limitations
Except as expressly provided in an applicable service agreement and to the extent permitted by law, the services and informational content are provided “as is” and “as available,” without implied warranties of merchantability, fitness for a particular purpose, or uninterrupted or error-free operation.
To the extent permitted by law and subject to the applicable service agreement, app2care is not liable for indirect or consequential losses arising from use of the services. Nothing in these terms excludes rights, warranties, liability, or duties that cannot lawfully be excluded, or reduces obligations under a BAA or a separately executed agreement.
11. Updates and contact
We may revise these terms as services change and will provide notice or seek acceptance where required by law or an applicable agreement. The last-updated date identifies this revision. Revised online terms do not automatically amend a separately executed agreement or BAA.
Questions about these terms or service agreements: support@app2care.com.
See also: Privacy Policy.
