Terms & Conditions

By accepting a proposal, quotation, invoice, or making an initial project deposit, the client confirms that these terms have been read, understood, and accepted. They apply from initial discussions and discovery through development, validation, handover, support, and any renewal period.

These terms provide a shared baseline for scope, communication, payments, asset usage, data security, and each party's responsibilities. Acceptance may be expressed through a signature, written reply, invoice approval, payment, or another action that clearly indicates acceptance of the engagement.

Where a quotation, proposal, invoice, or signed agreement contains project-specific conditions, that document governs the operational details of that project. These terms continue to apply to matters not expressly addressed in the project document.

Oketa.id Studio delivers digital products according to the scope agreed in the proposal, quotation, brief, or Minimum Viable Product (MVP) document. Depending on the engagement, this may include planning, information architecture, interface design, baseline copywriting, development, configuration, testing, deployment, and technical support.

The approved project document is the reference for deliverables, boundaries, dependencies, and acceptance criteria. Differences between a visual example, an informal assumption, and the written scope should be confirmed before work begins to avoid mismatched expectations.

Features, integrations, data migrations, approval workflows, architectural changes, or technical requirements not listed in the initial scope are treated as additional work. Additional work starts only after its impact on fees, schedule, and capacity is agreed in writing.

Projects normally move through requirements and scope finalization, structure and design planning, development, testing and validation, then production release and handover. The number and duration of stages may differ by project, but the next stage will be communicated before work proceeds.

Development officially starts after the initial payment is received and the core requirements are sufficiently clear. Oketa.id Studio may request confirmations, materials, access, or decisions before continuing work that depends on them.

Completion dates are estimates and depend on feedback speed, asset readiness, approvals, third-party availability, and technical conditions. Delays in providing logos, copy, images, data, credentials, or decisions may move the schedule without being treated as a unilateral delay by Oketa.id Studio.

Payment follows the quotation or invoice issued for the project. Custom engagements may use milestone payments, such as an initial payment before work begins, a progress payment when the main work is ready for testing, and a final balance after validation before handover. Simpler projects may use a shorter structure as agreed.

Work on a milestone may begin after the related payment or agreed payment condition is satisfied. Each payment supports the allocation of planning, development, communication, testing, infrastructure, and operational time for the engagement.

Final handover, master access, production credentials, repository access, or public deployment occurs after validation is complete and the final invoice is settled. Late payments may delay a milestone, pause work, or defer handover until the outstanding obligation is resolved.

Where stated in the proposal, the initial project fee may include domain registration or configuration, server infrastructure, SSL certificates, and other infrastructure required for the initial service period. The exact coverage follows the approved project document and does not automatically include unrelated third-party services.

After the initial period, renewal is required to keep the domain, server, SSL, backups, and technical support active. Renewal is a continuing service separate from the initial development fee unless the proposal clearly states otherwise.

Renewal fees may change based on storage and traffic requirements, security needs, provider pricing, registrar policy, tax, or exchange-rate fluctuations. Renewal information will be provided before processing. If renewal is not completed, the service may be suspended or exposed to provider-specific data and configuration retention policies.

A revision is an adjustment to work that remains within the agreed direction and scope. Examples include copy corrections, minor layout refinements, responsive fixes, visual detail changes, or small workflow corrections that do not alter the foundation of the work.

For an efficient process, feedback should be consolidated and submitted through the agreed communication channel. Fragmented feedback, repeated reversals, or withdrawn approvals may require rescheduling and can affect the estimated completion date.

Requests that change the primary concept, add pages or modules, alter data structures, introduce new user roles, or replace an approved workflow are treated as scope changes. Oketa.id Studio will describe the expected impact before requesting approval to proceed.

After all payment obligations are settled, the client receives ownership and usage rights for the content, custom visual materials, business data, and final deliverables created specifically for the project, subject to the agreed scope. The client is responsible for ensuring that supplied materials may lawfully be used.

Oketa.id Studio retains rights to internal libraries, base components, templates, methods, architecture patterns, and general technical knowledge that are reused across projects. This does not reduce the client's rights in materials and final work made specifically for their business or organization.

Oketa.id Studio may display public project names, visuals, summaries, or links as part of its official portfolio after publication, unless a confidentiality agreement or written restriction applies. Confidential materials and internal data will not be displayed without appropriate permission.

Oketa.id Studio treats business information, organizational data, member or user records, internal documents, credentials, and non-public materials received during a project as confidential information. They are used only as needed to understand, build, test, operate, or support the service.

Access to project information is limited according to work requirements. We use reasonable access-management practices, avoid exposing credentials unnecessarily, and reduce access when the technical need or engagement ends.

Information may be shared with technical providers required to operate the service, such as domain, server, email, analytics, or API providers, when relevant to the project. Oketa.id Studio does not sell confidential client information or use it for another party's marketing purposes.

After launch, technical support and bug fixes may be provided under the package or service period agreed for the project. A bug means a failure in functionality included in the original scope that does not operate as intended under reasonable usage conditions.

Active maintenance may include basic monitoring, security updates, configuration upkeep, SSL renewal, backups where supported by the infrastructure, and resolution of technical issues related to Oketa.id Studio's work.

Maintenance does not automatically include new module development, major business-process changes, recurring content operations, daily administration, or damage caused by code, access, configuration, or infrastructure changes made by another party without approval. Those requests may be quoted as additional services.

Oketa.id Studio builds and operates services using reasonable technical practices, but cannot guarantee that every service will be uninterrupted, that a website will always achieve a particular search ranking, or that external platforms will remain unchanged.

We are not responsible for issues caused by hosting providers, domain registrars, external APIs, platform policy changes, user devices, third-party actions, credentials shared insecurely, or force majeure events outside reasonable control.

Claims are reviewed based on scope, evidence, chronology, and the applicable project documents. To the extent permitted by applicable law, aggregate liability for proven direct claims is limited to the service fees paid for the relevant project scope.