Terms of Service

1. About these Terms

Repopack is operated by [operator legal name, legal form, registered address and registration number] ("Repopack", "we", "us"). These Terms of Service ("Terms") govern your access to and use of Repopack, including the website at repopack.com, the web application, the APIs, the rp command-line tool, Git and SSH access, jobs, applications, and any related features we provide (together, the "Service").

You accept these Terms when you create an account, when you accept them in the Service, or otherwise when you use the Service. When you sign up, we ask you to confirm that you agree, and we record which version of the Terms you accepted and when.

Our Privacy Policy explains how we handle personal information. Other policies that these Terms refer to, such as an acceptable use or naming policy we publish in the future, form part of these Terms.

In these Terms, a "business user" is someone using the Service for their trade, business, craft or profession, or on behalf of an organisation. A "consumer" is an individual using the Service for purposes outside their trade, business, craft or profession. Some sections apply differently to consumers, and where they do, we say so.

2. Your account

You must be at least 16 years old, and old enough to enter into a binding contract where you live, to create an account or use the Service.

If you use the Service on behalf of a company or other organisation, you confirm that you are authorised to accept these Terms for it. In that case, "you" includes that organisation.

You are responsible for:

• giving us an email address that you control and keeping it current. We use it to sign you in and to send you service communications;
• keeping your credentials secure, including access to your email account, your SSH keys, API and CLI tokens, and any machine where the rp CLI is signed in;
• all activity performed through your account, including activity through your tokens, keys and automation (see section 9); and
• telling us promptly if you believe your account or credentials have been compromised.

Accounts are personal. Do not share your account or credentials with other people. Each person should use their own account, and projects can be shared through project membership.

3. Early access

Repopack is currently in an alpha/beta stage, and access may be limited to people we invite. During early access:

• features may be incomplete or experimental, and may change, be removed, or be unavailable;
• interfaces, APIs, CLI behaviour, workflows and data formats may change, sometimes without advance notice;
• the Service may be interrupted, and data may be lost or corrupted; and
• you should not rely on the Service as guaranteed production infrastructure, for example for workloads or data you cannot afford to lose or have unavailable.

We may limit, pause or end early access, or particular early-access features, for example because of capacity, security, cost, or changes in our plans. Where practicable, we will give you notice first (see section 14).

Unless we expressly commit otherwise, you are responsible for keeping your own copies of important code and data. For Git repositories, keeping an up-to-date clone elsewhere is usually enough.

4. Free access and fair use

The Service is currently free. If we introduce paid plans, we will tell you in advance, and we will not charge you unless you agree to paid terms.

Free access does not mean unlimited access. You are not entitled to unlimited compute, storage, bandwidth, execution time, concurrency, jobs, applications, builds, logs, artifacts, API requests, agent activity or other platform resources. That no limit is published for a resource does not mean it has no limit.

We may set, adjust and enforce reasonable limits where needed to protect the availability and security of the Service, protect other users, prevent abuse, control disproportionate use of resources, keep operating costs reasonable, or keep free and early access viable. Measures we may use include:

• throttling, quotas, and limits on concurrency, execution time, runtime, storage or bandwidth;
• temporarily restricting features or workloads;
• asking you to reduce your usage; and
• stopping or suspending workloads that use an unusual amount of resources or place a material burden on the Service.

Where practical, we will tell you about a problem and give you a chance to fix it before we act. Where an immediate risk to the Service or to others makes that impractical, we may act first and tell you afterwards.

5. Acceptable use

You must not use the Service, or attempt to use it, to:

• access systems, accounts or data without authorisation;
• distribute malware or other malicious payloads, or operate botnets or command-and-control infrastructure against systems whose owners have not consented;
• carry out denial-of-service attacks or other attacks on third parties;
• exploit vulnerabilities in systems you are not authorised to test;
• steal credentials, phish, or send spam or other unsolicited bulk messages;
• generate abusive automated traffic toward the Service or third parties;
• mine cryptocurrency, or run similar resource extraction, unless we have expressly permitted it;
• run workloads designed mainly to consume excessive resources or to degrade the Service;
• evade limits, quotas, suspensions or other restrictions, for example by creating additional accounts;
• probe, attack or disrupt Repopack's infrastructure, interfere with other users' workloads or data, or circumvent isolation between workloads;
• store, publish or distribute content that is illegal, or that infringes other people's intellectual property, privacy or other rights;
• harass, threaten or defraud other people; or
• otherwise break the law, or create unreasonable security, operational, legal or reputational risk for Repopack, our users or third parties.

Security research. Legitimate security work is welcome. You may develop and store security tools and test systems that you own or have permission to test. To test Repopack itself, you must follow any vulnerability disclosure policy we publish, or get our permission first. Report vulnerabilities to [security contact]. You must not access other users' data, degrade the Service, or keep data beyond what is needed to demonstrate a vulnerability.

We may publish a more detailed acceptable use policy. If we do, it forms part of these Terms.

6. Your content

"Your content" means the code, repositories, files, tasks, comments, reviews, pastes, job and application configuration, environment variables and other secrets, logs, artifacts and other material that you, your collaborators acting on your behalf, or your automation submit to or create through the Service.

You keep your rights. We do not claim ownership of your content.

The licence you give us. You grant Repopack a worldwide, non-exclusive, royalty-free licence to host, store, copy, transmit, process, execute, build, display and back up your content, and to transform it where technically necessary (for example to render, index, highlight, compress or convert it). This licence covers only what is reasonably necessary to provide, secure, maintain, support and improve the Service, and to carry out actions requested by you, your collaborators or your automation. It includes showing your content to the people you give access to, and to the public where you choose to make something public.

The licence does not allow us to sell your content or use it for advertising. "Improving the Service" means things like diagnosing problems and understanding how features are used. It does not include using your private content to train machine learning models that we offer to others.

The licence ends when your content is deleted from the Service, except for copies that remain in backups or logs until those expire, content that has become part of shared project history as described in our Privacy Policy, and anything we must keep to comply with the law or to establish, exercise or defend legal claims.

Your responsibilities. You are responsible for your content. You confirm that you have the rights and permissions needed to upload, store, run, distribute and otherwise use it through the Service, and that doing so does not break the law, these Terms, or anyone else's rights.

Visibility. Project content is visible to the people your project's owners give access to. Things you deliberately make public, such as public pastes, public job artifacts and applications exposed to the internet, can be accessed by anyone.

Our access. We do not review content before it is published and do not routinely monitor it. We may access your content where reasonably necessary to operate or troubleshoot the Service, to support you when you ask us to, to investigate reports, abuse or security issues, or to comply with the law. We may remove or disable access to content that breaks these Terms or the law (see section 13).

7. Jobs, applications and code execution

The Service can build and run code you provide, including jobs, builds and applications, on infrastructure that we operate or control. You are responsible for:

• the code you run and its dependencies;
• how you configure your workloads, including the secrets and settings you provide;
• the data your workloads process and the actions they take, including requests they make to other systems;
• obtaining the licences and permissions your workloads need;
• complying with the law in what your workloads do; and
• what you choose to expose publicly. Public applications and public artifacts can be reached by anyone on the internet.

We do not review or approve workloads before they run. Running code on Repopack does not mean we endorse it.

We may stop, isolate, suspend, restart or remove workloads, or disable public access to them, where reasonably necessary for security, abuse prevention, resource management, legal compliance, or the integrity of the Service and other users' workloads. Where practical, we will tell you why. Workloads can also be interrupted by maintenance, failures or changes to the Service, so design them with that in mind.

Personal data in your workloads. We do not know what data your applications and jobs process, and you are responsible for complying with data protection law for that data. We do not currently offer a data processing agreement. If you need Repopack to act as your processor under data protection law (for example, to run an application that processes your customers' personal data), contact us before doing so.

8. Secrets and sensitive data

Use the mechanisms the Service provides for secrets, such as application environment variables, rather than putting credentials, API keys or tokens in repositories, task text, pastes, logs or public content. Remember that the workloads you run can read the secrets you give them, and your code could expose them. Revoke or rotate any secret you believe has been exposed.

We take reasonable measures to protect the Service, as described in our Privacy Policy, but no system is perfectly secure, and we cannot guarantee that data or secrets will never be exposed.

The Service is not designed or certified for regulated or high-risk data. Unless we have agreed otherwise in writing, do not use it to store or process:

• special categories of personal data, such as health, genetic or biometric data, or data about criminal convictions;
• payment card data or other data subject to industry security standards; or
• data subject to specific legal or regulatory security regimes, such as classified information.

9. Automation, agents and API access

Repopack is built for automated and agent-driven work. We treat actions taken through the APIs, the CLI, SSH keys, tokens, agents, jobs, applications or integrations, using your credentials or set up by you, as actions performed or authorised by you.

You are responsible for configuring, supervising and limiting the automation you authorise, including AI agents you connect to the Service. Review what your automation does, and give it no more access than it needs. AI tools you use with Repopack are provided by third parties under their own terms.

Do not misrepresent who or what performed an action. For example, do not present an agent's activity as a human review where your collaborators rely on that distinction.

10. Names and identifiers

Identifiers are the names that identify things on Repopack, such as project names, group names, usernames and application names. Project names are unique across all of Repopack.

No permanent right to a name. Registering or using an identifier does not give you ownership of it, or an unconditional or permanent right to it. Identifiers are made available for use with the Service, subject to these Terms, any naming policy we publish, and the continued operation of the Service. You may not sell, rent or otherwise trade identifiers, except by transferring a project or group through features the Service provides for that purpose.

Names do not define ownership. Ownership, membership, grouping and permissions are determined by Repopack's records, not by the text of an identifier. For example, alice-tools does not mean the project belongs to the user alice, and repopack-web does not mean the project belongs to Repopack or to a repopack group. Hyphens, dots and other characters in a name have no special meaning.

Choosing names. You must not choose or use an identifier, or present the project or group behind it, in a way that:

• infringes or violates someone else's rights, including trademarks and service marks, trade names and brands, personality or publicity rights, and other intellectual property or proprietary rights;
• impersonates a person, company, organisation, product, service or Repopack itself, or misleadingly suggests sponsorship, endorsement, ownership, affiliation or authorisation. For example, you must not register a well-known company's name and present the project as that company's official project;
• amounts to squatting or bad-faith registration. This includes registering names mainly to stop others from legitimately using them, to sell, rent or ransom them, or to gain leverage over an established name or brand; registering large numbers of desirable names without genuine use; and otherwise acquiring names mainly for obstruction, deception, speculation or abuse; or
• could reasonably be mistaken for an official Repopack function, system resource, administrative area, security or support channel, official Repopack project or group, or another Repopack service.

Words like admin, support, security, billing, settings or login, and names that match a trademark, are not banned. What matters is whether a particular use infringes rights, misleads people or is abusive. We technically reserve only the few names that conflict with how the Service works, such as new for projects.

What we may do. We may ask you to rename an identifier, rename it ourselves, suspend its use, reclaim or revoke it, or transfer it to someone else where appropriate (for example, to the holder of the rights it infringes). Where needed, we may also suspend or remove the associated project or group. We do these things where reasonably necessary to address:

• infringement, or a credible claim that an identifier violates a third party's rights;
• impersonation or misleading affiliation;
• squatting, fraud or other abuse;
• security concerns, or legal or regulatory requirements;
• operational conflicts, or conflicts with Repopack functionality;
• a breach of these Terms; or
• material harm to Repopack, our users or third parties.

A rename or reclamation can change URLs, Git remote addresses and application hostnames that contain the name. We will try to limit that disruption where practical.

Notice. Where practical, we will contact you first and give you a reasonable opportunity to respond or to choose a new name. We may act without advance notice where that is needed for an urgent security issue, fraud or abuse, a legal requirement, serious impersonation or infringement, or to stop ongoing harm or confusion. Either way, we will tell you what we did and why, as described in section 13.

Disputes about names. If you believe an identifier infringes your rights or impersonates you, or you want to challenge a decision we made about an identifier, contact [abuse and legal contact]. Tell us the identifier, the basis for your claim, and how to reach you. We will consider the information available to us and decide what to do on Repopack. We do not decide trademark ownership or other legal disputes the way a court does, and our decision does not stop anyone from going to court.

Serious or repeated abuse. Deliberate or repeated misuse of identifiers can have consequences beyond losing a name. Examples are wilful impersonation, deliberate trademark abuse, repeated squatting, coordinated bad-faith registrations, and attempts to evade earlier naming enforcement. Such misuse may lead us to suspend or terminate the accounts and resources involved (see section 14).

Groups. These rules apply to group names in the same way as to project names. A group is a way to organise projects. It does not gain stronger rights to its name because it contains several projects.

11. Open source and third-party services

Your code may include open source or other third-party components. You are responsible for complying with the licences that apply to your code and its dependencies. We are not responsible for making sure your repositories or dependency graphs comply with those licences.

The Service can work with third-party services, such as Git hosts you import from, container registries your builds pull from, and AI tools you use alongside Repopack. Their terms apply to your use of them. Their availability is outside our control, and we are not responsible for them.

Parts of the Service may include open source software. Where those components come with their own licence terms, those terms govern them, and nothing in these Terms limits your rights under them.

12. Repopack's rights and feedback

Repopack and its licensors own the Service, including its software and design. Subject to these Terms, we give you a limited, non-exclusive, non-transferable right to use the Service. We may provide software for download, such as the rp CLI. Where that software comes with its own licence, that licence applies to it.

The Repopack name and logo are our trademarks. These Terms do not give you any right to use them, except to refer to Repopack truthfully, for example to say that a project is hosted on Repopack.

If you send us feedback or suggestions, we may use them without any obligation to you. This does not give us any rights to your content beyond those in section 6.

13. Reporting content and enforcement

If you believe content on Repopack is illegal or breaks these Terms, report it to [abuse and legal contact]. To help us act, please include:

• where the content is, such as a link to it;
• why you believe it is illegal or breaks these Terms;
• your name and email address, unless the report concerns child sexual abuse material; and
• a statement that you believe in good faith that your report is accurate and complete.

People review reports and decide what to do with them. We do not currently use automated tools to moderate content. If you gave us your contact details, we will tell you what we decided.

If we remove or restrict your content, workloads, identifiers or account, we will tell you and explain why, unless the law prevents us or telling you would undermine the security of the Service or an investigation. If you disagree with a decision, contact us, and we will review it. This does not affect any other remedy available to you, including going to court.

Authorities and users can contact us about these matters at [single point of contact], in English [and other languages, if any].

14. Suspension and termination

You may stop using the Service at any time. To close your account, contact us (see section 26).

We may suspend or end your access to the Service, or to part of it, such as a project, a workload or a feature, where reasonably necessary because:

• you have broken these Terms or our policies;
• your use creates a security risk or involves abuse or unlawful activity;
• the law, or an order from a court or authority, requires it;
• you have tried to evade limits or earlier enforcement;
• your use harms, or risks materially harming, the Service, our users or third parties;
• payment is overdue, if we introduce paid plans;
• your account has been inactive for a long period, after we have warned you by email; or
• we are ending the Service or its early-access programme.

We will choose a response that is proportionate to the problem, for example restricting a single workload rather than your whole account where that is enough. Where practical, we will warn you first and give you a chance to fix the problem. We may act without advance notice where needed to address a security issue, abuse or a legal requirement, or to prevent harm. In that case, we will tell you as soon as we reasonably can, unless the law prevents us or telling you would undermine security or an investigation.

If we decide to end the Service, or your access to it, for reasons unrelated to your conduct, we will give you reasonable advance notice, at least 30 days where practicable, so you can export your content.

After termination, your right to use the Service ends, and we may delete your account and your content. Some information may remain for a period afterwards, for example in backups, where we must keep it for legal reasons, or as part of shared project history, as described in our Privacy Policy. Sections that by their nature should continue after termination, such as those on content licences, liability and disputes, continue to apply.

15. Availability, changes and backups

We work to keep the Service available and reliable, but we do not guarantee that it will be uninterrupted or error-free. Interruptions, software defects, failed jobs or builds, application downtime, deployment problems, and loss or corruption of data can happen, especially during early access.

We may add, change or remove features, change APIs and interfaces, change limits, change whether free access is available, and change how the Service is built. Where a change materially reduces what you can do with the Service, we will tell you in advance where practicable. Any commitments we make under future paid plans will take priority over this section.

Unless we expressly agree to back up specific data for you, keep your own backups of anything important.

16. Warranties

During early access, we provide the Service free of charge, "as is" and "as available". To the extent the law allows, we make no promises about the Service beyond those in these Terms, including promises that it will be fit for a particular purpose or meet your requirements.

If you are a consumer, you have legal rights that these Terms cannot exclude or limit, and nothing in these Terms affects them.

17. Liability

Nothing in these Terms limits or excludes our liability:

• for intent or gross negligence;
• for death or personal injury caused by our negligence;
• for fraud;
• under mandatory product liability law; or
• in any other case where the law does not allow liability to be limited or excluded.

Subject to that:

• Where we are slightly negligent, we are liable only if we breach an obligation that is essential to providing the Service, and that you can reasonably rely on us to fulfil. Even then, we are liable only for damage that is typical and foreseeable for a service of this kind.
• If data is lost and we are liable for it, our liability is limited to the effort that would have been needed to restore it if you had kept reasonable backups (see section 15).
• If you are a business user, we are not liable for lost profits, lost revenue, business interruption, or indirect or consequential damage. Our total liability to you for all claims relating to the Service is limited to the greater of €100 and the amounts you paid us for the Service in the 12 months before the claim arose.

18. Indemnity

This section applies only to business users. You will indemnify Repopack against third-party claims, and the resulting reasonable costs and damages, to the extent they arise from your content, your workloads, material you provide that infringes a third party's rights, illegal or abusive use of the Service through your account, or your breach of these Terms. We will tell you promptly about any such claim, let you control its defence where appropriate, and cooperate reasonably with you.

19. Privacy

Our Privacy Policy explains what personal information we process and why, how long we keep it, and your rights. Accepting these Terms is not consent to any particular processing. The Privacy Policy explains the legal basis we rely on for each purpose.

20. Communications

We send service communications to the email address on your account. These include sign-in codes, security and account notices, notices about changes to the Service or these Terms, and other legal and operational notices. You cannot turn these off while you have an account. We also send workflow notifications, such as email about task activity and mentions, which you can control in your notification settings.

Accepting these Terms does not mean you agree to receive marketing. We do not currently send marketing email. If we start, we will ask for your permission separately where the law requires it.

Where the law allows, notices we send by email or show in the Service meet any requirement for notice in writing.

21. Changes to these Terms

We may update these Terms as the Service, the law or our operations change. The date at the top of this page shows when the version you are reading takes effect. Earlier versions remain available.

Minor changes, such as clarifications, corrections, or terms for new features that do not reduce your rights, take effect when we publish them.

Material changes: we will publish the updated Terms on this page and notify you by email at least 30 days before they take effect, unless a shorter period is needed to comply with the law or to address security or abuse. Once they take effect, we will ask you to accept them in the Service. If you do not agree to them, you can close your account before they take effect. We may limit access to the Service for accounts that have not accepted the current Terms.

22. Export controls and sanctions

You must comply with the export control and sanctions laws that apply to you and to your use of the Service. You may not use the Service if you are subject to sanctions that prohibit us from providing it to you, or to export, transfer or process anything in breach of those laws. We may restrict access where we believe the law requires it.

23. Assignment and transfer

You may not transfer your account, or your rights or obligations under these Terms, without our consent.

We may transfer these Terms, or our rights and obligations under them, to a successor or affiliate as part of a merger, acquisition, restructuring, financing or sale of all or part of our business, or to a successor operator of the Service. We will tell you if this happens. If you are a consumer and do not want to continue with the new operator, you can close your account.

24. Governing law and disputes

These Terms are governed by the laws of [country of the operator's establishment], excluding its conflict-of-laws rules and the United Nations Convention on Contracts for the International Sale of Goods.

If you are a consumer, you also keep the protection of the mandatory laws of the country where you live, and you may bring proceedings in the courts of that country.

If you are a business user, the courts of [place of the operator's registered office] have exclusive jurisdiction over disputes relating to these Terms or the Service, to the extent the law allows.

If you have a concern, please contact us first. Most issues can be resolved quickly that way.

25. General

• These Terms, together with the policies they refer to, are the entire agreement between you and us about the Service. A separate written agreement with us about specific services takes priority where it says so.
• If a court finds any part of these Terms invalid or unenforceable, the rest remains in effect.
• If we do not enforce a provision straight away, we can still enforce it later.
• Headings are for convenience only.
• These Terms are written in English. If we provide a translation, the English version prevails to the extent the law allows.

26. Contact

[operator legal name and postal address]
Email: [contact email]