Terms of Service
Purpose. These terms apply to visitors, leads, clients, and project participants who engage with PT XIPTOR SOFTWARE SERVICE through our website, email, messaging channels, invoices, or project systems.
Order of precedence. If there is a conflict between these page terms, a signed statement of work, and a project invoice, the signed project document controls for that engagement.
Clear records. We may keep written records of approvals, scope changes, and delivery confirmations so the engagement stays traceable and easy to manage.
Defined scope. Each project is delivered according to the agreed brief, proposal, statement of work, or written email confirmation. Anything not listed there is treated as out of scope.
Out-of-scope work. Additional features, integrations, revisions, migrations, investigations, or deployment changes may require a new estimate, new timeline, or separate approval.
Delivery format. Deliverables may include source files, compiled builds, documentation, access credentials, handover notes, or configuration details, depending on the project.
Accurate information. The client must provide correct contact details, project information, access permissions, and source materials needed to complete the work.
Timely input. Delays in feedback, approvals, access, or required assets may shift delivery dates and can pause work until the block is resolved.
Rights to materials. The client confirms that any content, dataset, brand asset, or third-party material provided for the project can be used for the intended purpose.
Backups. The client remains responsible for keeping backups of their own systems, data, and environments unless backup duties are explicitly assigned in writing.
Commercial terms. Payment terms follow the service type and project size. Larger builds commonly use milestone-based payment, while smaller or support-based work may require a higher upfront commitment so resources can be allocated immediately and safely. Fees, milestones, reserved engineering capacity, deposits, and expenses are governed by the written quotation, invoice, or service agreement for the project.
Payment timing. Unless stated otherwise, invoices are due on the schedule shown in the written commercial terms. Late or unpaid balances may pause work until the account is settled.
Third-party costs. Cloud services, licenses, hosting, payment processing, travel, shipping, and similar third-party costs are charged as agreed in the project documents.
Refunds. Refund handling is defined per agreement. In most cases, once work has started and resources are allocated, payments are treated as non-refundable, with revisions and scope management used to protect the outcome.
Pre-existing IP. Each party keeps ownership of its pre-existing tools, frameworks, code, designs, and know-how.
Project outputs. Ownership, licensing, and transfer of project outputs are determined by the written agreement and any project-specific addendum.
Open-source and third-party components. Components that come from third parties remain subject to their own license terms and usage restrictions.
Reference materials. Unless the agreement says otherwise, PT XIPTOR SOFTWARE SERVICE may keep general non-client-specific know-how, methods, and reusable internal patterns developed during the work.
Confidential information. Both sides should protect non-public business, technical, financial, and operational information shared during the engagement.
Use limits. Project data may be used for engineering delivery, support, administration, and related operational purposes unless otherwise agreed in writing.
Storage and safeguards. We may use vetted third-party tools, subprocessors, or cloud services where needed, with controls that fit the sensitivity of the project.
Cross-border handling. When information must move across borders, we apply appropriate technical and organizational safeguards for the project context.
No harmful use. The client may not use our services or deliverables for unlawful, deceptive, harmful, abusive, or unauthorized activities.
Examples. Prohibited use includes malware, phishing, credential theft, fraud, unauthorized access, and other activity that could harm people, systems, or data.
Risk checks. We may pause or refuse work if a request appears unsafe, unclear, or outside the agreed business purpose.
Compliance. Each party remains responsible for its own compliance obligations related to the way the services are used.
Professional care. Services are delivered with reasonable professional skill and care based on the agreed scope.
No guaranteed outcomes. We do not guarantee specific business results, approvals, search rankings, platform acceptance, or outcomes controlled by third parties.
Support windows. Response times are best effort unless the project includes an explicit service level agreement.
External dependencies. Issues caused by third-party platforms, hosting providers, devices, or client-side changes may require a separate review or additional work order.
Pause or end. Either party may pause or end an engagement for material breach, non-payment, material risk to systems or data, or completion of the agreed scope.
Good-faith resolution. Before escalation, both parties should try to resolve concerns through direct written communication and a reasonable review period.
Updates. We may update these page terms when our services or operating practices change. The posted version is the active version unless a written agreement says otherwise.
Final note. Nothing in these terms removes any mandatory right that cannot be waived under applicable law.