Terms of Service

1. About these Terms

These Terms of Service ("Terms") govern your use of Codebase.run, including its website, application and AI-assisted software-development services (together, the "Service").

The Service is provided by 1xTeam sp. z o.o., a Polish limited liability company, with its registered office at Jana Kazimierza St. 11B/29, 01-248 Warsaw, Poland. Polish Tax ID (NIP): 5223035587. National Court Register (KRS): 0000571058. REGON: 362256087 ("Codebase.run", "we", "us" or "our").

Contact for contracts, support, complaints, cancellations and legal notices: hello@codebase.run. You may also write to our registered address. Customer contact telephone: +48 794 044 144.

"You" or "Customer" means the individual or organization entering into the agreement with us. A "Consumer" is an individual acting outside their trade, business or profession, as defined by applicable law. Consumer protections also apply to sole traders and other customers to the extent applicable law grants them equivalent rights.

Nothing in these Terms excludes or limits rights that applicable law does not allow us to exclude or limit. Business-only provisions do not override those protections.

2. Agreement, eligibility and accounts

The account agreement begins when you expressly accept these Terms and the Acceptable Use Policy during registration and we provide your account. It continues until ended under these Terms. A paid order is formed when you accept the price and order details provided by us and we confirm the order. An invoice or quotation alone does not authorize a purchase.

You must be at least 18 and legally able to enter into the agreement. Someone accepting on behalf of an organization must have authority to bind it. You must provide accurate account and billing information and keep your contact details current.

Using the Service requires an internet connection, a current supported web browser with JavaScript and essential storage enabled, a GitHub account, and the repository permissions and GitHub App installation needed for the selected features. You are responsible for your connection and devices. Additional material technical requirements will be disclosed before the relevant purchase or activation.

You may authorize team members to act for your account or project ("Authorized Users"). You are responsible for managing their permissions and for work they authorize within those permissions. Repository ownership, installing the GitHub App and accepting a paid order are separate actions: none automatically authorizes spending another customer's credits.

Protect your accounts and credentials and promptly report suspected misuse. We do not hold you responsible for unauthorized charges caused by our failure to meet our obligations merely because activity appeared under your account.

3. The Service and available plans

The Service uses AI agents and computing environments to assist with software-development tasks. Depending on available features and your instructions, it can inspect repositories, prepare environments, modify code, run commands and checks, and create or update pull requests and related reports.

We provide development tooling and resource usage, not a promise that each task will produce a particular result or an accepted pull request. We remain responsible for supplying the agreed Service with reasonable care and skill and for any mandatory requirements of conformity.

The Free plan provides the allowance and features stated when access is granted. Free access does not become paid access automatically. Paid plans are available only when we accept an order and confirm its features, price and duration. Paid access may be activated manually following payment by bank transfer.

References to a Business plan or custom capabilities are invitations to discuss future requirements. They do not promise that those capabilities are currently available or will be delivered by a particular date. A custom scope becomes binding only when expressly agreed with you.

Features clearly identified as beta, preview or experimental may change or be withdrawn under Section 17. No uptime percentage, response-time commitment or service-level credit applies unless expressly included in an accepted order. Labels such as "beta" or "Free" do not remove applicable statutory rights.

4. Repository permissions and automated actions

By connecting a project and authorizing work, you permit us to access and process the relevant repository and project materials, create working copies and environments, install dependencies, run code and tools, communicate with configured services, and publish results within the permissions and instructions you provide.

Only you and Authorized Users may request work against your project's payer account or enable automated follow-up work. An outside contributor's participation in a repository does not by itself authorize access to that account's credits.

An enabled workflow can authorize further executions without a separate approval for each execution, including responses to supported review or CI events. Those executions consume credits under Section 6. You are responsible for the scope of the automation you enable and for withdrawing permissions you no longer intend to grant.

Disabling follow-up, removing an integration or requesting cancellation may not immediately stop an execution already in progress. Usage continues until the relevant processing stops and the worker is released. Use any available stop control and contact us when assistance is needed; do not rely on changing a repository label as an immediate spending stop.

Repository changes can trigger your own CI, deployments or other third-party actions and charges. These are separate from Codebase.run credits. Configure approvals, secrets and permissions accordingly. Publishing into a public repository can make the published material publicly accessible.

5. AI limitations and your review

AI-generated code, explanations, tests and other results ("Output") may be incomplete, incorrect, insecure or unsuitable for a particular purpose. Different users may receive similar results. We do not guarantee that Output is unique, eligible for intellectual-property protection or free of third-party rights.

A "verified pull request" refers to the checks actually performed and their reported results in the relevant environment. It is not a certification, a comprehensive security audit or a guarantee that every test passed or that the code is production-ready. Review reported failures, skipped checks and limitations.

You are responsible for reviewing and appropriately testing Output before merging, deploying, distributing or relying on it. Maintain your own backups and use human approval for consequential actions. Repository content, dependencies and external services can contain malicious code or misleading instructions; isolation and automated checks do not eliminate every risk.

Do not rely on the Service as the sole safeguard in a safety-critical or regulated use case. These responsibilities do not release us from our own contractual or statutory obligations.

6. Credits and metered usage

6.1. What credits represent

Credits are units used to account for Service consumption. They are not a fixed number of tasks and do not guarantee a particular outcome. They are not transferable, tradable or redeemable for cash, except for refunds expressly provided by these Terms or required by law.

The applicable rates, credit conversion and any material usage limits must be available to you in the application, pricing information or written order before you authorize chargeable work. Our rates are Service prices set by us; they are not necessarily our suppliers' prices or a reimbursement of our exact supplier costs.

6.2. Starting an execution

The designated payer must have a positive credit balance before an execution or retry starts. We do not reserve an estimated total task cost. A positive balance is permission to start, not a guarantee that the task will finish within that balance.

6.3. What is measured

AI usage is calculated from separately metered uncached input tokens, cached input tokens and output tokens, using the applicable model and service-tier rates.

Compute usage covers the time a worker is allocated to the execution, including preparation, commands, testing and waiting that occur during that allocation. Time before allocation and after release is our platform cost, not your task's compute charge. Environment preparation and follow-up work consume credits when they form part of a metered execution.

6.4. Conversion and deductions

The prices and conversion rate applicable to an execution are fixed when that execution starts. A later price change does not reprice that execution.

For each usage record, its cumulative US-dollar-denominated cost is multiplied by its fixed microcredits-per-dollar conversion rate and rounded upward to a whole microcredit, the smallest accounting unit used by the Service. We deduct only the increase over the amount already charged for that record. Repeated reporting of the same usage does not create a second charge.

Deductions occur as AI usage is reported and compute usage is observed or finalized. Each deduction updates the balance and creates a corresponding ledger entry together. Reported balances can lag actual consumption. Corrections and refunds are recorded through separate credit adjustments rather than silently removing usage history.

6.5. Negative balances

An execution already running is not automatically stopped when credits run out. Your balance can become negative. The balance is not a spending cap for running work. A zero or negative balance blocks subsequent starts and retries, including additional automated executions that require a new start.

A negative balance does not, by itself, create a cash debt. We do not automatically charge a payment method or issue an overage invoice solely because the balance is negative. You may stop using the Service without purchasing further credits to clear it.

Later credit grants or purchases may first offset that balance. Before accepting a paid renewal or top-up, we will disclose any such offset and the credits that would remain available. You may decline the purchase. This paragraph does not excuse fraud, intentional circumvention or deliberate abuse.

6.6. Failed or cancelled work

Resources already consumed remain chargeable when a task fails, is cancelled, produces no changes or does not achieve your preferred result. Automated follow-ups and retries are separate executions and can consume further resources.

This is not a waiver of remedies for billing errors or our failure to supply the agreed Service. We will investigate disputed usage and correct charges that should not have been made. We will provide any legally required refund or other remedy.

7. Purchases, plan periods and credit validity

Before you commit to payment, we will provide the plan or credit quantity, total price, currency, applicable taxes, payment method, activation arrangements, duration and expiry rules. Consumer order totals include applicable taxes and unavoidable charges payable to us. A bank or payment provider may apply its own disclosed conversion or transfer charges.

Paid plans under these Terms are prepaid and do not renew automatically. You purchase each further period separately. We do not perform automatic top-ups. Introducing automatic renewal would require separate, express enrollment after disclosure of its price, frequency and cancellation conditions.

A paid period begins on the activation date confirmed in the order, not merely when an invoice is issued. Pay only using payment instructions we have confirmed. If we receive payment but cannot provide the accepted order, we will refund it.

Unless your accepted order expressly provides otherwise, credits included in a periodic plan expire at the end of that purchased period and do not roll over. Any separate top-up offer must specify its validity before purchase; if no expiry is specified, no time-based expiry applies while the account remains open. Mandatory rules governing credit validity always prevail.

Promotional credits have the eligibility conditions and expiry disclosed when granted; without a disclosed expiry, they remain available while the account remains open, subject to these Terms. Promotional credits have no cash refund value and do not replenish automatically unless the offer says so.

You can ask to cancel a paid plan at any time. Normally, paid access remains available until the purchased period ends. Not purchasing another period creates no renewal charge. Cancelling paid access does not, by itself, delete your account or published repository content.

8. Refunds and billing corrections

As a voluntary policy, we will refund your most recent plan or top-up purchase if you contact us within 14 days of purchase and none of the access or credits supplied under that purchase has been used. This voluntary policy is additional to, and does not replace, statutory rights.

Otherwise, a change of mind, an unused part of a purchased period or an unsuccessful task does not automatically qualify for a refund. Sections 9 and 10, billing corrections, our termination obligations and mandatory law remain applicable.

Contact hello@codebase.run with the account, order or execution reference and the issue. We will correct duplicate and otherwise incorrect deductions through the credit ledger. Where a cash refund is due, we will not replace it with credits without your agreement. Cash refunds use the original payment method unless you expressly agree to another method without extra cost, and are issued within the applicable legal deadline or, for a voluntary refund, within 14 days of approval.

9. Consumer withdrawal from a distance contract

Consumers in the European Economic Area and the United Kingdom may withdraw from an online service purchase without giving a reason within 14 days after the contract is concluded. Equivalent or more protective rights under other applicable laws remain available. A separately concluded renewal or top-up contract has its own applicable withdrawal period.

To withdraw, send an unambiguous statement to hello@codebase.run or our postal address in Section 1. You may use the form at the end of these Terms, but it is not compulsory. Any withdrawal function provided in our online interface is an additional method, not a restriction on other lawful methods. Sending your statement before the deadline is sufficient.

We will reimburse payments covered by withdrawal without undue delay and no later than 14 days after receiving your notice, using the original payment method unless you expressly agree otherwise and without a refund fee.

If you expressly ask us to begin the paid Service during the withdrawal period, and we provide the legally required information, you may be required to pay a proportionate amount for the services actually supplied before your withdrawal. We calculate that amount using the agreed price and extent of performance, without double counting access and resource usage. It will not exceed the amount permitted by law.

Without the required express request or information, we will not charge for early performance where the law prohibits it. Merely accepting these Terms is not that express request. Starting a task or consuming some credits does not automatically remove your right to withdraw from the whole ongoing Service.

10. Consumer conformity and remedies

Where consumer digital-service law applies, the Service must conform to the contract, including applicable requirements for functionality, compatibility, accessibility, continuity and security. We will provide required updates for the legally applicable period.

If the Service is not supplied or does not conform, you may have rights to require supply or correction, receive a price reduction, or terminate and obtain a refund, depending on the circumstances. Correction must be free of charge, within a reasonable time and without significant inconvenience where the law so requires. You need not accept Service credits instead of a cash refund legally due.

These rights also apply to eligible free services where the relevant law covers them. Descriptions of AI limitations and business-only liability restrictions do not displace these rights.

11. Customer Content and intellectual property

"Customer Content" means the code, instructions, files, repository information and other materials you provide or authorize us to access, together with Output produced for your project. You retain all rights you hold in your existing materials.

You grant us a non-exclusive permission to host, copy, process, adapt, execute and transmit Customer Content only as needed to provide, maintain and secure your Service, handle support, comply with law and give effect to your instructions. This includes necessary processing by our service providers and publishing to destinations you authorize. The permission ends when those purposes and applicable retention obligations end.

You must have the rights and lawful authority needed to provide the materials and instructions, including where a repository belongs to an employer, client or another organization.

We do not assert ownership of AI-generated Output against you. To the extent we hold licensable intellectual-property rights in Output, we grant you a worldwide, non-exclusive, royalty-free, transferable and sublicensable license for personal and commercial use for the full duration of those rights, to the fullest extent permitted by law. It covers copying, storage, execution, modification, adaptation, translation, incorporation into other works, distribution, sale, licensing, publication, display and making Output available to others. Those rights survive termination of your account.

This does not transfer our platform, models, internal tools or other pre-existing technology. Third-party and open-source components remain subject to their own licenses, notices and restrictions. Review these before distribution or use.

We and our licensors retain rights in the Service itself. You receive a limited, non-exclusive right to use it during your agreement in accordance with these Terms. Feedback you voluntarily provide about the Service may be used to improve it without compensation, but this does not give us a general development license to your private code or other Customer Content.

12. Confidentiality, privacy and service providers

We protect non-public Customer Content as confidential. Access is limited to personnel and service providers who need it for permitted processing and who are subject to appropriate confidentiality and data-protection obligations. Our administrators may access relevant material when necessary for operations, support or security.

Confidentiality does not restrict information already lawfully public, independently developed without using your confidential information, lawfully obtained without restriction, or disclosed as legally required. Where legally permitted, we will notify you of a compulsory disclosure affecting your confidential information and limit it to what is required.

Codebase.run does not use customer project content to train models, develop the platform or conduct benchmarks. Customer-specific analysis is used to provide the relevant customer's Service. This does not prevent processing content-free operational statistics for legitimate service administration as described in our Privacy Policy.

We use external providers, including AI and infrastructure providers. Relevant project material is transmitted to them when needed for the Service. Provider-specific processing, locations, training arrangements and retention must be assessed under the disclosures in our Privacy Policy and any applicable data processing addendum; these Terms do not promise zero retention or processing exclusively within the EU.

Our Privacy Policy explains personal-data processing. Accepting these Terms is not consent to optional analytics or an unrestricted use of personal data.

Where we process personal data on your behalf, we must put an appropriate data processing addendum ("DPA") in place with you before that processing. An agreed DPA forms part of our contract and prevails on its subject matter. These Terms alone do not replace a required DPA. You remain responsible for your lawful instructions, notices and permissions; we remain responsible for our own data-protection obligations and our appointed processors.

13. Acceptable use and connected services

You and your Authorized Users must comply with our Acceptable Use Policy, which forms part of this agreement and supplements the acceptable-use rules in this Section 13. The AUP does not create separate payment rules, an additional liability cap or a new right to use Customer Content or personal data.

You must not use the Service to break the law or infringe another person's rights; gain unauthorized access to systems; create or deploy malware for unlawful or harmful purposes; facilitate fraud, spam or denial-of-service activity; evade credit accounting or access controls; or abuse free allowances, computing resources or other users' access.

Authorized security research and testing are not prohibited merely because they involve security tools, but you must have permission for the systems tested. Testing our infrastructure requires our prior written authorization unless covered by an applicable published testing policy.

Do not submit unnecessary sensitive personal data, live production datasets, payment-card data or material requiring special regulated handling that we have not expressly agreed to support. Use appropriately restricted test credentials and do not expose production secrets in repository content, prompts or logs.

Do not resell access to our platform or reverse engineer protected Service components except where we authorize it or the restriction is prohibited by law. This does not limit the Output license in Section 11 or lawful interoperability rights. Comply with applicable export controls and sanctions.

GitHub and other services you connect remain subject to your agreements with their operators. You are responsible for permissions and charges for integrations you choose. We remain responsible for providers we engage to perform our own contractual obligations to the extent required by law.

Reports of unlawful content, rights infringements or abuse may be sent to hello@codebase.run. Include its location, the reason for the report and relevant supporting information. We will assess reports and take appropriate action; we do not claim that every task or item of content is reviewed by a person before processing.

14. Support and complaints

Send support requests and complaints to hello@codebase.run or our postal address. Describe the issue, relevant dates and available account, order or task references. Do not send passwords or unnecessary sensitive information.

We will respond to complaints within 14 calendar days after receipt, or sooner where mandatory law requires. We may ask for information needed to investigate, without extending a statutory deadline where that is not permitted. A response deadline is not a promise that every technical problem can be resolved within that period.

Unless an accepted order says otherwise, support is not provided on a 24/7 basis and no guaranteed technical response time applies to ordinary support requests.

15. Suspension and ending the agreement

You may end your account agreement at any time by contacting us and asking to close the account, or by using an available account-closing function. You can separately disable integrations and stop authorizing new work. Charges for resources already consumed and applicable refund rights are addressed above.

We may restrict or suspend affected functionality where reasonably necessary to address a material breach, suspected fraud, a security threat, unlawful use, an applicable legal requirement or an unpaid amount you actually agreed to pay. A negative credit balance alone does not create such a cash payment obligation.

Where reasonably possible, we will explain the reason and give you an opportunity to resolve the issue before suspension. We may act immediately where delay would create harm or violate law. Measures should be proportionate, and you may request a review by contacting us. We will restore access when the reason for restriction has been resolved, unless lawful termination is justified.

We may terminate for a material breach that remains uncorrected seven days after notice, or immediately for serious or repeated abuse or where required by law. For other termination or discontinuation, we will provide at least 30 days' notice and refund amounts attributable to paid services we will not supply and unused separately purchased credits. We will not impose a termination penalty.

A customer-initiated closure does not create a voluntary refund beyond Section 8, but all statutory and expressly promised refunds remain available. Closure does not automatically remove commits, pull requests, comments or other material already published on GitHub. Rights in Output, confidentiality, payment and refund obligations, and provisions necessary to resolve existing disputes survive termination.

16. Export, switching and deletion

16.1. Retained data and export

The Service is not your repository backup or a permanent archive. Keep copies of materials you need. Normal retention is described in the Privacy Policy; short-lived worker data may no longer exist when an export is requested. We will not delete retained exportable data to frustrate a valid export or switching request.

You may request an export at hello@codebase.run. Subject to verification of your authority, the export covers retained customer-provided files and repository copies; project settings and instructions; task histories, agent messages, tool results, patches, screenshots and reports; customer-related usage and credit records; and customer-specific environment configurations and assets, including retained images, snapshots and caches to the extent they are exportable data or digital assets.

We provide data in a commonly used, machine-readable form appropriate to the material, such as structured data, text, source files, patches or archives. The export excludes other customers' data, our platform-managed secrets, proprietary platform components and internal materials protected by our intellectual-property or trade-secret rights, but only to the extent their exclusion is legally permitted. We do not withhold your exportable data merely because it is stored together with excluded material.

16.2. Switching

Where Chapter VI of the EU Data Act applies, you may switch to another provider or your own infrastructure, or request deletion without switching. No additional contractual notice period is required to initiate the process. We will provide reasonable assistance, information about known technical limitations and continuity risks, and appropriate security and service continuity during transition.

We will complete the transition without undue delay and within 30 calendar days of your request. If that is technically unfeasible, we will explain why within 14 working days and give an alternative transition period no longer than seven months, subject to the statutory conditions. You may exercise any statutory right to extend the transition once for a period reasonably appropriate to your needs.

We charge no switching, standard export or data-egress fee. Ordinary agreed Service charges remain payable only as applicable to services supplied during transition. We do not promise that another provider can reproduce proprietary Service functionality. The affected service agreement ends when switching is completed, or when the applicable notice period ends for deletion without switching, as required by law; we will confirm this to you.

16.3. Retrieval and erasure

After account termination or the end of a switching transition, we make retained exportable project data available for retrieval for at least 30 calendar days, unless you request earlier deletion. A longer period may be agreed or required by law. A negative credit balance does not prevent a lawful retrieval request.

After the retrieval period, we erase the relevant project data from our systems, including retained environment images, snapshots, caches and backup copies, and instruct our processors to erase their copies in accordance with the applicable DPA and law. When you request earlier deletion, we act without undue delay and within 30 days, subject to any shorter mandatory deadline.

We retain separately only information necessary for a legal obligation, an unresolved security incident or legal claims, for no longer than that purpose requires. Such retained information remains protected and is not used to continue project processing. Disconnecting a repository or uninstalling the GitHub App alone is not a deletion request.

17. Changes to the Service, prices and Terms

We may make changes for specific, justified reasons: complying with law; addressing security or abuse; maintaining compatibility with GitHub, AI providers or infrastructure; fixing defects; improving functionality; or responding to material changes in the cost or availability of providing the Service. Changes must be proportionate to the reason.

We will notify existing customers by email at least 30 days before a material adverse change to these Terms or applicable prices takes effect, except where an earlier change is necessary to address an urgent legal or security requirement. The notice will explain the change, effective date and available choices. We will obtain express acceptance where required; silence alone is not consent to a new charge.

New prices apply prospectively. They do not reprice past or running executions or increase the agreed price for a period already purchased. Optional new paid features require separate authorization. A change that materially reduces prepaid functionality gives you any applicable right to end the affected service and receive a refund for services not supplied.

Where consumer digital-service law applies, non-essential changes are made only for the justified reasons above and without an additional charge. For a change that adversely affects access or use beyond a minor degree, we will provide advance notice on a durable medium. You may terminate without charge within 30 days after the change or receipt of the notice, whichever is later, unless we let you retain the conforming unchanged service without additional cost. More protective statutory rights prevail.

Changes to the Acceptable Use Policy follow this Section 17. Merely publishing a revised AUP does not establish acceptance of new contractual obligations. We retain the accepted version and obtain express acceptance where required.

18. Business-only warranties and liability limits

This Section applies only to business customers and only to the extent it does not conflict with mandatory protections applicable to them. It does not limit Consumer remedies or liability.

Except for express commitments in our agreement, we provide the Service and Output on an "as available" basis. To the extent permitted by law, we exclude implied warranties of merchantability, fitness for a particular purpose and non-infringement. We do not promise uninterrupted access or error-free Output.

Subject to the exceptions below, we are not liable for lost profits, lost business opportunities or indirect or consequential losses. Our total aggregate liability arising out of the Service and these Terms is limited to the greater of USD 100 or the fees you paid to us for the Service in the 12 months preceding the event giving rise to the claim.

These exclusions and limits do not apply to fraud, intentional misconduct, gross negligence, death or personal injury caused by negligence, or any liability that cannot lawfully be excluded or limited. They do not limit statutory data-protection compensation or non-waivable rights under the EU Data Act. Refunds and credit corrections expressly due under these Terms are not reduced by the liability cap.

19. Business-only third-party claims

To the extent permitted by law, a business customer is responsible for reasonable, documented amounts finally awarded against us, or included in a settlement the customer approves, arising from a third-party claim caused by your supplying materials you did not have the right to provide, or your intentional or negligent material breach of Section 13. It does not apply merely because unmodified Output generated by the Service infringes a third party's rights.

This obligation does not cover a claim caused by our breach, negligence or unauthorized modification. We must notify you promptly, permit you to participate in the defense and provide reasonable cooperation. Neither party may settle in a way that admits fault or imposes a non-monetary obligation on the other without that party's consent. This Section does not apply to Consumers or override equivalent mandatory protections.

20. Governing law and general provisions

These Terms are governed by Polish law. For Consumers, that choice does not remove mandatory protections of the law of the country where they habitually reside when those protections apply.

For business customers, the courts having jurisdiction over our registered office in Warsaw, Poland have exclusive jurisdiction, unless mandatory law provides otherwise. Consumers may bring claims in any court available to them under applicable law, including their home courts where permitted. These Terms do not require arbitration or waive non-waivable rights to participate in collective proceedings.

You may contact us to seek an informal resolution, but this is not a mandatory prerequisite to exercising legal rights. Consumers may seek assistance from a competent consumer authority, consumer ombudsman, Trade Inspection or European Consumer Centre. We are not committed to a specific alternative dispute-resolution scheme unless required by law or separately agreed; when a dispute arises, we will provide any required information about available procedures and our participation.

These Terms, the Acceptable Use Policy, an accepted order and any agreed DPA form the agreement. An order controls only the scope, price, duration and other matters it expressly addresses. A DPA controls personal-data processing on your behalf. Mandatory law prevails over every document.

If a provision cannot lawfully be enforced, the remainder continues to apply where legally possible, without substituting a term that unlawfully disadvantages a Consumer. A failure to enforce a right once does not waive it. We may transfer the agreement in a genuine business reorganization or sale only without reducing your contractual or mandatory rights and with notice where required.

We provide this version in English. A legally required local-language version, interpretation rule or disclosure obligation takes precedence over any preference for English. We will make the accepted Terms and Acceptable Use Policy, together with any paid-order confirmation, available in a form you can save, including by email.