SUMMARY
A modular service with clear responsibilities.
Kesekolah provides a School ERP foundation that can be activated in stages. Final usage rights, modules, capacity, integrations, support, pricing, and SLA follow the commercial scope agreed with the customer.
Scope and acceptance
By accessing the website or using Kesekolah services, users accept the terms relevant to that use. For contracted customers, signed commercial and legal documents are the primary reference if there is any conflict.
- The website may be used to learn about the product, request a demo, contact the team, and evaluate service scope.
- Production service only covers modules, tenants, integrations, capacity, and support enabled in the customer's scope.
- Additional terms may apply to integrations, migrations, payment gateways, communication channels, or third-party services.
Organization authority and accounts
Users who create, manage, or use an organization/school account must have sufficient authority from the party they represent.
- Customers are responsible for assigning appropriate administrators, tenant access, roles, permissions, and approval actors.
- Account credentials must not be shared in ways that remove user accountability or violate organization policy.
- Activity performed through an account may be recorded in audit/activity logs according to the available resource and configuration.
- Customers should promptly address suspected unauthorized access, users who are no longer authorized, or incorrect permission configurations.
Permitted and prohibited use
The service is intended for lawful education and operational processes. Users must preserve platform integrity and must not use the service to harm the system or other parties.
- Use the service only for lawful processes within your authority and related to education organization needs or customer scope.
- Do not attempt to bypass authentication, authorization, tenant isolation, policies, workflows, or other security restrictions.
- Do not upload malware, harmful files, unlawful data, or material for which you lack an appropriate basis of use.
- Do not disrupt, overload, scan, exploit, or attempt to access another organization/tenant's data without permission.
- Do not use the service to create false records, disguise transactions, or remove auditability from processes that should remain traceable.
Customer data and input responsibility
Customers remain responsible for data they choose to enter, import, connect, or process through the service and for the authority of users who manage it.
- Ensure student, guardian, staff, vendor, bank, transaction, attachment, and other data is obtained and used lawfully.
- Verify master data, periods, tenants, organizations, account mappings, and business configuration before production workflows are used.
- Input, mapping, or approval errors by authorized users may affect system outputs, journals, statuses, reports, or downstream transactions.
- Customers should retain source copies or evidence required by internal policy or applicable requirements when necessary.
- Data export, correction, or deletion requests follow dependencies, transaction status, audit requirements, and applicable customer procedures.
Modules, integrations, and roadmap
Kesekolah is developed modularly. Not every capability shown in a blueprint, roadmap, demo, or public material is automatically available in every customer deployment.
- Production features follow the source version, active modules, configuration, permissions, and agreed implementation scope.
- Roadmap items, mockups, dummy data, or features marked future/premium are not delivery commitments unless included in a scope document.
- Integrations such as payment gateways, WhatsApp, email, APIs, webhooks, regulatory exports, or Dapodik may require credentials, approvals, or third-party services.
- Customers are responsible for validating integration and reporting outputs against operational or regulatory requirements applicable to their organization.
Pricing, packages, and commercial terms
Website pricing helps prospects understand package structure. Final pricing, taxes, setup, migration, integration, support, capacity, and subscription periods are defined in a proposal or contract.
- Public pricing may be indicative and may change before a proposal or order form is agreed.
- Packages may be adjusted based on school/tenant count, user/data volume, modules, integrations, migration, and implementation needs.
- Payment obligations, invoices, due dates, refunds, renewals, or commercial termination follow the applicable customer documents.
- Marketing material does not replace pricing or obligations expressly stated in a signed contract.
Availability, maintenance, and changes
Kesekolah may perform maintenance, fixes, hardening, security updates, and feature development. Production SLA, maintenance windows, backup, recovery, and support follow the customer's package or agreement.
- Changes may be made for security, compatibility, bug fixes, compliance, or process improvements.
- Features may differ between development, UAT, staging, demo, and production environments.
- Disruptions from external providers, networks, payment gateways, email, WhatsApp, or other third-party services may be outside Kesekolah's direct control.
- Uptime, response-time, recovery-target, and support-escalation commitments are binding only when stated in an SLA or contract.
Intellectual property and license
Rights in Kesekolah software, design, documentation, brand, and materials remain with their respective rights holders. Customers receive usage rights according to a license or contract, not source-code ownership unless separately stated.
- Use of Kesekolah logos, brand assets, screenshots, documentation, or materials must respect owner rights and agreed terms.
- Customers remain responsible for and retain rights in their business data, subject to the agreement and applicable requirements.
- Users must not copy, resell, distribute, or provide service access beyond the rights granted in the contract.
- Rights in third-party components remain subject to each component or provider's license.
Suspension and termination
Access may be restricted or terminated when required for security, terms violations, contract expiration, payment obligations, or other reasons stated in the customer agreement.
- Customer administrators may disable or change user access according to their internal authority.
- Kesekolah may take mitigation action when there is suspected abuse, account compromise, or risk to data and service integrity.
- Data export, handover, retention, and deletion after termination follow the contract and technical conditions of related data.
- Obligations that survive termination by their nature, including confidentiality, payment, audit, and intellectual property, follow the applicable agreement.
Warranties, responsibility, and governing documents
Kesekolah helps run processes based on customer configuration and data, but it does not replace professional judgment, school policy, accounting verification, or customer regulatory obligations.
- Customers should perform UAT and configuration verification before important workflows are used in production.
- System outputs depend on data quality, mappings, configuration, approvals, and integrations in use.
- Liability limits, indemnity, warranties, disputes, governing law, and other special terms follow the customer contract and applicable law.
- If this page conflicts with a signed customer contract, the customer contract governs that commercial relationship.
- Kesekolah may update these public terms when the product, architecture, service model, or operational obligations change and will display the latest update date.
SERVICE QUESTIONS
Need to discuss scope or implementation terms?
Contact the Kesekolah team to discuss modules, deployment, integrations, support, or commercial terms applicable to your organization.