Chocolatecake Terms of Use

1. Public website and product agreements

The public website provides information about Chocolatecake and links to email consultation. It does not provide product account registration, payments, package-request submission or access to a Customer’s internal systems. Contact links open your email application; an inquiry is sent only when you send the email.

Product descriptions and inquiries support deployment discussions. Product licensing, delivery, support and any entrusted personal-data processing require a separate agreement. Product illustrations do not establish approval or availability of a particular package.

2. Purpose and application

These terms describe the rights and obligations of Marker Inc., operating under the Markr brand ("we" or "Markr"), the organization deploying Chocolatecake (the "Customer"), and employees or contractors authorized by that Customer ("Users") in connection with Chocolatecake software and related support (the "Services").

These terms apply when incorporated into an agreement with the Customer or otherwise agreed. A separate agreement takes precedence for any conflicting delivery scope, license, fees, support or data-processing terms. Browsing our website or sending an inquiry does not by itself create a product agreement.

3. Services and delivery scope

Chocolatecake is a platform for supplying development software inside an organization. The contracted configuration may include package discovery and supply requests, collection and inspection evidence, review and approval by authorized people, internal publication, distribution and withdrawal, a management console, development-tool integrations and an operations assistant.

Supported ecosystems, versions and environments, installation arrangements, acceptance criteria and delivery dates are specified in the applicable agreement and distribution documentation. A roadmap or product description does not include unimplemented features or universal compatibility with public repositories, packages or projects.

4. Accounts and organizational authority

The Customer assigns User, operator and approver permissions and manages account provisioning, changes, revocation, identity integration and credential protection. Users must stay within their assigned organization, environment and role, and must not share another person’s credentials or misrepresent their authority.

A request submitted by an employee or agent is not organizational approval or authority to enter a contract on the Customer’s behalf. The Customer must promptly adjust access after departure, role changes or credential compromise, and notify Markr of suspected service defects.

5. Inspection, approval and supply

Inspection results are evidence about particular files, versions and environments at a particular time. Passing an inspection is not a guarantee of safety, a grant of legal usage rights or organizational approval. New supply requires valid evidence and policy conditions followed by approval and publication by an authorized person.

The Customer reviews the intended use, target environment and usage scope and complies with package licenses, notices and transfer requirements. Missing mandatory evidence or integrity failures must not be bypassed through discretionary approval. Changes in security information or authorization may require reassessment, a hold or withdrawal.

Withdrawal restricts access through the repository. It does not remotely delete downloaded or installed files or block their execution. The Customer handles affected devices and copies through its own operational procedures.

6. Agents and model connections

Development-tool integrations and the operations assistant help with authorized lookups, explanations of status and evidence, and drafts of requests or handling proposals. Generated text or suggested tool calls do not confer approval, signing or publication authority. Users must verify the target, evidence and authorization and complete the human decisions required by the system.

Model responses may be inaccurate or incomplete, and external material such as package descriptions or logs may contain malicious instructions. Model output alone must not change security policy or approve supply. Coding agents and model services used by the organization are also subject to their providers’ terms.

The Customer manages the endpoints, transmitted information, accounts and costs of its internal model or separately contracted model or gateway. External connections require authorization under the organization’s transfer and privacy rules; saving credentials or testing connectivity is not itself permission to transmit data. Any commitment by Markr to cover model charges or guarantee a provider’s quality requires a separate agreement.

7. Customer data and confidentiality

Rights in request content, project material, operational records and other information lawfully held by the Customer or Users remain with their respective rights holders. Using the Services or providing support material does not transfer ownership or grant Markr a general right to reuse it.

The Customer must have the authority and necessary legal basis to process information it enters into or transfers through the Services. Markr will process supplied material only as needed to perform the agreement or requested support, and will not use confidential Customer material for advertising or general-purpose model training. Support submissions should be minimized and stripped of passwords, signing keys and unnecessary personal information.

The privacy policy and applicable agreement define processing roles and scope, entrusted processing, retention, return and deletion. These terms do not grant contractual consent for automatic transfer of the Customer’s internal data to Markr.

8. Security and operational responsibilities

Markr provides distributions, documentation, defect corrections and security-related support within the agreed scope. The Customer appoints operators and manages network boundaries, access, certificates and credentials, repository capacity, backup and recovery, and endpoint operations. Specific maintenance responsibilities and response times are set by the applicable agreement.

Inspection, isolation, approval and access controls reduce risk but do not guarantee the absence of vulnerabilities, malicious behavior or configuration errors. Each party must protect the area it controls, promptly share incidents that may affect the other party’s data or services, and cooperate on mitigation and recovery. This does not transfer responsibility for Markr’s defects or negligence to the Customer.

9. Acceptable use and third-party rights

• Do not access systems without authorization, use another person’s account, or bypass or falsify authentication, approval, signatures or audit records.
• Do not distribute malware or use the Services for unlawful activity, infringement or interference with normal operation.
• Comply with licenses and lawful usage scope for packages, models, plugins and other third-party components. Availability through supply does not replace the rights required from their owners.

10. Product rights, licensing and fees

Rights in original Chocolatecake software, trademarks and documentation belong to Markr or the relevant rights holders. Use, installation, copying, term, quantities, redistribution rights and fees are specified in the applicable license and agreement. Publication of this page does not grant an unrestricted product license or establish a price.

Included open-source software and third-party materials remain subject to their own licenses and notices. These terms do not restrict rights granted by those licenses or by applicable law.

11. Changes, maintenance and termination

Updates, maintenance and feature changes follow the agreed delivery and support terms. Markr will give advance notice of material changes affecting the Customer and discuss necessary transition arrangements. Urgent security or legal requirements may require action first, followed promptly by an explanation of the reason and impact.

Remedies for breach, restrictions, termination and settlement follow the applicable agreement and law. Arrangements at termination must address data return, export, retention and deletion, the end of software rights and any transition assistance. Termination or a change to website terms does not authorize Markr to arbitrarily delete Customer server data or retroactively change an existing agreement.

12. Warranties and liability

Markr will perform the delivery, acceptance, warranty and support obligations expressly agreed in the applicable contract. We do not promise unagreed fitness for a particular purpose, compatibility with arbitrary environments, uninterrupted operation or complete security. Descriptions of work in progress are not production acceptance or warranties.

Each party’s liability and its extent depend on fault, applicable law and any valid separate agreement. These terms do not exclude liability for intentional misconduct or gross negligence, or liability that cannot lawfully be limited. General descriptions of limitations do not displace statutory rights or express contractual warranties.

13. Governing law, updates and contact

Unless a valid separate agreement provides otherwise, the laws of the Republic of Korea apply, without limiting mandatory legal rights. The parties will first seek to resolve disputes in good faith, then use a court with jurisdiction under applicable law or another lawfully agreed dispute-resolution procedure.

Updates will identify the revision date, material changes and when they apply. Changes affecting an existing agreement follow that agreement’s notice and consent procedure. Continued visits to this website do not by themselves constitute acceptance of a new paid agreement or amendment of an existing one.

Services, terms and security contact: admin@markr.ai

For personal information, see our Privacy Policy.