Terms of Service for the entire Aibiz ecosystem.

1. Acceptance and authority

Individual users must have legal capacity and authority to represent an organization or use the service. Anyone accepting these terms for a healthcare provider or business represents that they can bind the organization. A person who does not agree must not access the services.

2. Scope of Aibiz services

3. Accounts, workspaces, roles, and security

Organizations are responsible for accurate registration data, owner designation, users, permissions, branches, locations, and module settings. Each user must use an individual account and protect credentials, devices, sessions, API tokens, and connected third-party accounts.

• Owners and admins must disable access when personnel are no longer authorized.
• Users may not share passwords, conceal identity, bypass permissions, or access another workspace.
• Activity may be recorded in audit trails for security, compliance, support, and investigation.

4. Healthcare-provider responsibilities

Healthcare providers remain responsible for care delivery, licensing, professional credentials, privacy notices, legal bases, consent, medical-record content, retention, disclosure, reporting, and patient-rights handling under applicable law.

• Allow only authorized personnel to use data and clinical functions.
• Verify patient identity, clinical data, prescriptions, orders, results, billing, and information sent externally.
• Define SOPs, escalation, schedules, capacity, patient communications, and emergency handling.
• Use features within provider licenses, professional competence, and Ministry of Health requirements.

5. Terms for patients and consumers

Bookings, conversations, forms, reminders, and public channels help connect patients or consumers with a provider or business. Schedule confirmation, healthcare prices, identity checks, eligibility for care, and clinical decisions remain with the relevant provider.

• Users must provide accurate information and may not misuse another person's identity.
• Automated messages may be generated or assisted by AI and can be handed to a human agent.
• Aibiz Wagen, WhatsApp, Instagram, and public forms are not emergency channels.

6. Clinical use and patient safety

Aibiz is workflow-support software and does not replace examination, diagnosis, judgment, decisions, or the responsibility of a healthcare professional. Professional users must independently assess information, check contraindications, and approve output before using it in care.

7. AI features, Scribe, and automated output

Transcripts, summaries, SOAP drafts, classifications, responses, insights, data extraction, and workflow recommendations generated by AI may contain errors or lose context. Output does not automatically become a final medical record.

Users must review, correct, and approve output before final storage, delivery, clinical decisions, transactions, or other action. Organizations must provide human handoff and escalation for conversations requiring human assessment.

8. WhatsApp Business, Instagram, Facebook, and Meta APIs

An organization connecting a Meta account instructs Aibiz to access and process data within granted API permissions. The organization remains responsible for account ownership or authority, communication content, recipient lists, consent, templates, message categories, frequency, and opt-out handling.

• Do not send spam, deceptive messages, illegal content, or communications without the required rights and consent.
• Comply with the WhatsApp Business Terms, WhatsApp Business Messaging Policy, Meta Platform Terms, and relevant channel policies.
• Protect number and account quality, respond to blocks or reports, and stop messaging when requested.
• Avoid unnecessary sensitive health data in templates, notifications, or channels that another person may see.

9. Integrations, interoperability, and external systems

Services may connect to SATUSEHAT, HIS, primary-care or clinic systems, LIS, RIS, PACS, Orthanc, DICOM, medical devices, local servers, email, calendars, payments, and other APIs. The organization is responsible for access rights, data compatibility, destination readiness, mapping, testing, and the legal basis for data exchange.

• Availability depends on configuration, connectivity, credentials, API versions, and third-party services.
• Third-party API or policy changes may require technical changes, revised schedules, or additional fees.
• Data to be sent must be checked by the user or source system under the organization's SOP.

10. Implementation, configuration, and migration

Implementation, migration, integration, training, go-live support, and acceptance follow the proposal or project document. The organization supplies required data, access, personnel, devices, connectivity, and configuration decisions. Migration quality depends on the completeness and consistency of source data.

11. Fees, subscriptions, usage, and taxes

Pricing, modules, quotas, locations, users, subscription terms, implementation fees, API or communication usage, taxes, and payment terms follow the proposal, order form, invoice, or agreement. Late or failed payment may result in feature restriction or suspension after reasonable notice, subject to data and legal obligations.

12. Support, maintenance, and SLA

Support channels, service hours, incident priorities, response targets, maintenance, and recovery follow the agreed package or SLA. Aibiz may perform scheduled or emergency maintenance for security and reliability. The organization must provide a reachable technical contact for significant incidents.

13. Prohibited use

• Accessing data without authority, bulk extraction, or attempts to defeat security or workspace isolation.
• Uploading malware, disrupting service, prohibited reverse engineering, or unreasonable system load.
• Fraud, harassment, discrimination, spam, illegal content, privacy violations, or intellectual-property infringement.
• Presenting unreviewed AI output as a verified professional decision.
• Reselling, renting, or granting service access outside the license without written consent.

14. Data, licenses, and intellectual property

Organizations and data owners retain their rights in submitted data and grant Aibiz a limited right to process it as needed to deliver, secure, support, and comply with the service. The organization represents that it has the necessary rights and authority over submitted data.

Aibiz software, designs, models, general configurations, documentation, brands, materials, APIs, and developments remain the property of PT Aplikasi Alday Indonesia or its licensors. Suggestions or feedback may be used to improve the service without disclosing confidential customer information.

15. Confidentiality, privacy, and security

The parties must protect confidential information and personal data according to their roles, agreements, and law. Data use is further governed by the Privacy Policy and, where applicable, an NDA or DPA. Each party must promptly notify relevant security incidents through agreed channels and cooperate in response.

16. Third-party services and external changes

Aibiz does not control third-party availability, policies, account decisions, pricing, usage limits, API changes, or provider actions. Use of Meta, WhatsApp, Instagram, SATUSEHAT, cloud, payment, device, and external systems is also subject to each provider's terms.

17. Availability, feature changes, beta, and sandbox

Aibiz works to keep services available and secure but does not guarantee uninterrupted operation. Features may be fixed, changed, replaced, or retired for security, compliance, performance, or development. Beta, trial, sandbox, or preview features may have limitations and must not be used for critical processes without approval and risk controls.

18. Suspension, termination, export, and deletion

Access may be restricted or suspended for violations, security risk, legal requests, failed payment, third-party disruption, or harmful use. On termination, export, transition, retention, deletion, and related fees follow the agreement, Privacy Policy, technical capability, and medical-record and legal duties.

19. Warranties and limits of liability

To the extent permitted by law, services are provided within the agreed scope without a guarantee that every output is error-free or fits every special requirement. Aibiz is not responsible for clinical decisions, incorrect user or source-system data, unauthorized use, third-party failure, or indirect loss. Other limits follow the commercial agreement and do not reduce rights that cannot lawfully be excluded.

20. Governing law, document order, disputes, and changes

These terms are governed by the laws of the Republic of Indonesia. The parties first pursue good-faith discussion and the dispute mechanism in the applicable agreement. For a specific subject, a signed special agreement prevails, followed by the order form or proposal, DPA or SLA, these terms, and the Privacy Policy according to the matter governed.

Aibiz may update these terms for service, legal, security, or platform-policy changes. The revision date appears on this page and material changes may be communicated through an appropriate channel.