Terms

Terms that stay practical.

The baseline rules for using the Cirakes website and working with Cirakes International.

These terms govern use of the public Cirakes website and the initial stage of contacting or evaluating Cirakes. Customer-specific agreements control where they differ.

Terms of use

These terms apply to the public Cirakes website and related pre-engagement communication. Signed proposals, statements of work, and other written agreements take precedence where they differ.

EntityCirakes International
Applies toPublic website use and early-stage commercial interaction
Last updatedMarch 30, 2026
Contacthello@cirakes.com
Overview

One clear page.
No hidden legal fog.

Key point

Public website terms first

These terms govern the public Cirakes surface and the first layer of interaction before a project-specific agreement exists.

Key point

Delivery depends on scope

Actual delivery terms, responsibilities, timing, and pricing should be agreed in writing for the relevant engagement.

Key point

Use the site responsibly

The website and its materials are intended for legitimate business evaluation, contact, and communication, not misuse or abusive automation.

01

Website use

You may use the Cirakes website to learn about the company, review public information, and contact Cirakes about potential work or collaboration.

  • Do not attempt to disrupt, probe, overload, scrape at abusive scale, or misuse the website or related systems.
  • Do not submit unlawful, deceptive, infringing, or harmful material through public forms or communication channels.
  • Do not represent that Cirakes has approved a relationship, partnership, or commitment unless it has been confirmed in writing.
02

Engagements and proposals

Nothing on the public website creates a delivery commitment by itself. Work begins only when Cirakes and the relevant customer agree on scope and terms.

Proposals, commercial discussions, and planning conversations are part of evaluation and scoping unless and until a final agreement is signed.

Cirakes may decline, pause, or re-scope work if the requested outcome, timeline, access model, or operating conditions are not workable or responsible.

03

Customer inputs and approvals

Strong delivery depends on accurate inputs, timely decisions, and access to the right context.

  • Customers are responsible for the accuracy, completeness, and legality of the information they provide.
  • Where approvals, access, credentials, brand assets, copy, or dependencies are required, delays in those inputs can affect timing and output.
  • Cirakes may rely on customer-provided materials and instructions unless there is a clear reason to question them.
04

Intellectual property

Cirakes retains ownership of its pre-existing methods, know-how, tools, frameworks, and materials unless a separate written agreement states otherwise.

Customer materials remain the customer's responsibility and property to the extent they already owned or controlled them before sharing them with Cirakes.

Rights in specific deliverables, drafts, or implementation outputs should be governed by the relevant signed agreement, proposal, or statement of work.

05

Liability and changes

Cirakes intends to operate responsibly, but the public website and early-stage information are provided on a general and evolving basis.

Cirakes does not promise that every public page, draft, or example will always be complete, current, or error-free.

To the maximum extent permitted by applicable law, Cirakes is not responsible for indirect, incidental, or consequential loss arising from public website use alone. Customer-specific liability should be addressed in the signed contract for the relevant work.

Cirakes may update these terms as the public surface and legal review mature. Material changes should be reflected by updating this page.

Contact

Need terms clarified before engagement?

Use the contact page if you want the commercial, delivery, or approval model clarified before work begins.

Email hello@cirakes.comBack to main site

Questions tied to a specific workflow, page, or request are easiest to answer when the exact context is included.