Terms of Service
The general terms of service governing access to Git.eu during its open beta, from 8 September to 30 November 2026.
Terms of Service — Open Beta
Version 1.1 · In force from 8 September 2026
0. Purpose and acceptance
0.1 These general terms of service (the "Terms") govern access to the Git.eu hosted software forge (the "Service") during its open beta phase, from 8 September to 30 November 2026. They form a contract between you (the "Customer") and Atyk, a société par actions simplifiée currently being registered with the Trade and Companies Register of Strasbourg, trading as Git.eu France, whose registered office is in Strasbourg, France ("Git.eu"). [SIREN number to follow on registration.]
0.2 They are published at git.eu/terms and can be read in full before opening an account. You accept them by opening an account; no signature is required.
0.3 Two other documents form an integral part of them: the Data Processing Agreement (git.eu/dpa) and the Privacy Notice (git.eu/privacy). In the event of a conflict on a data protection matter, the Data Processing Agreement prevails.
0.4 If you open an account for an organisation, you represent that you have authority to bind it, and these Terms bind that organisation.
0.5 These Terms cover a free phase. The terms applicable to paid subscriptions, opening on 1 December 2026, are published separately and are presented to you before any payment — see Article 16.
0.6 Opening an account is reserved to persons aged sixteen or over. Between the ages of sixteen and eighteen, opening an account is possible during the open beta, which is free; taking out a paid subscription, from 1 December 2026, is subject to the commercial terms referred to in Article 16.
0.7 "Customer" means the party entering into these Terms: you, or the organisation on whose behalf you act under Article 0.4. "User" means the natural person who accesses the Service by means of the account. During the open beta, an account corresponds to a single natural person: the Customer and the User are then the same person, except where the Customer is an organisation. The Customer is responsible for what the User does from its account.
1. Description of the Service
1.1 The Service is a hosted software forge: public and private repositories, full Git history, issues, merge requests, code review, wikis, and import from any Git repository accessible by URL.
1.2 What the Service does not do as at 8 September 2026: there is no continuous integration runner, no public API, no webhooks, and an account cannot yet grant someone else access to a private repository.
1.3 The Service's interface is in English and French, and will remain so throughout the open beta.
1.4 Your account and repositories are attached to an instance. There is only one during the open beta.
1.5 The Service is provided as it exists on the day you use it. We evolve it during the beta; Article 17 explains how we notify you when a change affects you.
2. Opening and maintaining an account
2.1 An account corresponds to one natural person, the User within the meaning of Article 0.7. It is not shared, transferred or resold. You are responsible for what is done from your account.
2.2 The information you give us on sign-up must be accurate and must remain so — in particular your email address, which is the only means we have of notifying you, notably before any deletion of data under Article 15.
2.3 You are responsible for the confidentiality of your credentials, keys and tokens. Two-factor authentication is available from the opening of the beta; we recommend that you enable it.
2.4 Notify us without delay at redalert@git.eu if you have reason to believe your account has been compromised.
2.5 During the open beta, one person holds only one account. The storage volume in Article 3.3 is assessed per account: opening multiple accounts to add them together is a circumvention within the meaning of Article 5.1(e).
2.6 You may close your account at any time from the Service, without reason and free of charge.
2.7 An account opened with an email address at the domain of a higher-education institution accesses the open beta free of charge, like any other account. From 1 December 2026, this access remains free for the duration of your studies, limited to one free account per student, and solely on condition that you continue to use that address. We ask for no other proof: no card, no document. This tier is checked at the start of each academic year, by the sole fact that the address still works. This is the only free account on the Service beyond the open beta; its terms are governed by the commercial terms referred to in Article 16.
3. Free of charge during the open beta
3.1 The Service is free from 8 September to 30 November 2026. No payment method is requested from you.
3.2 No amount may be charged to you during this period, on any basis whatsoever.
3.3 The storage volume included is 50 GiB per account, covering all content — repositories, history, large files, attachments. A single counter, and nothing else is measured.
3.4 Once this volume is reached, you can no longer add content: uploads that would exceed the limit are refused. Everything else continues to work — reading, cloning, issues, merge requests and export. You are warned at 80% and 100% of the volume, before crossing the limit and not after. Nothing is charged, and no paid overage option is offered during the open beta.
3.5 The free nature of this phase does not amount to a commitment to remain free beyond 30 November 2026.
4. Your content
4.1 You retain all rights in what you upload to the Service. We acquire no rights in your code or associated material.
4.2 You grant us, for the sole duration of hosting and for the sole purpose of operating the Service for your benefit, a non-exclusive, royalty-free licence to store, copy, transmit, back up and display your content. This licence does not extend beyond what is technically necessary to provide you with the service and ends when the content is deleted.
4.3 We do not read your repositories. The content of a private repository, and that of a non-public issue or merge request, is treated as confidential information: we apply to it at least the care we apply to our own confidential information. Access is limited to the three cases in clause 3.4 of the Data Processing Agreement: technical necessity to provide the Service, a support request from you, or a legal obligation. Each access is limited to what the purpose requires, and we inform you of it — except where the law prohibits us from doing so or a security imperative requires us to act first. We do not scan private repositories looking for a breach of these Terms: on a private repository, we act only on a report, a legal requisition, or observable technical signals that do not require accessing the content — volume, traffic, resource consumption.
4.4 Your repositories are not used to train machine learning models, ours or third parties', and are not made available to anyone for that purpose. This is clause 9 of the Data Processing Agreement: a contractual undertaking that survives any change of control of the company and any assignment of this contract.
This undertaking concerns what we do with your content. It has no bearing on what a third party would do, independently of the Service, with the content of a repository you have chosen to make public.
4.5 A public repository is public. Your commit metadata — author name and email address — is recorded in the Git history and readable by anyone who accesses it, including after deletion, in copies others have made of it. We cannot remove it without rewriting your history, which belongs to you.
4.6 By making a repository public, you authorise other users to view, clone, download and duplicate it through the Service's functions, and to display and reproduce its content through the Service. This authorisation does not extend beyond the Service and does not replace the licence you attach to your repository: where that licence grants more, it applies.
4.7 When you contribute to a repository under a licence — commit, merge request, patch — your contribution is made under that same licence, unless otherwise agreed between you and the repository owner.
4.8 You are responsible for what you upload: for its lawfulness, for having the necessary rights, and for compliance with the licences of any third-party components you include in it.
4.9 You may not upload to the Service data falling within Article 9 GDPR (racial or ethnic origin, political opinions, religious beliefs, trade union membership, health data, genetic or biometric data, sex life). The Service is neither designed nor represented as suitable for processing such data.
4.10 You may export your data at any time, free of charge and without giving a reason. This is a function of the Service, not a request you need to make to us.
5. Prohibited uses
5.1 It is prohibited to use the Service to: (a) upload, distribute or make available unlawful content; (b) infringe the rights of third parties, in particular intellectual property rights, privacy or image rights; (c) conduct an attack against an information system, or distribute malware to people who have not requested it; (d) send unsolicited messages, phish, or impersonate someone; (e) access or attempt to access an account, repository or data not intended for you, or circumvent a technical limitation of the Service; (f) use the Service as a storage, backup or file distribution space unrelated to development work, or as a content delivery network; (g) mine cryptocurrency or run processing unrelated to code hosting; and more generally for any use liable to harm the integrity of the platform; (h) harm, or attempt to harm, the integrity, availability, security or proper functioning of the Service or the infrastructure hosting it.
5.2 Hosting security research code, including offensive code — proof-of-concept material, audit tools, documented exploits — may only be done in accordance with applicable law. It is, however, prohibited to use Git.eu to conduct an attack or deceive a victim. We judge the use, never the subject.
5.3 The help space in Article 7 is a workplace between professionals. Abusive, harassing or discriminatory remarks, and contributions manifestly unrelated to the topic at hand, are removed under the conditions of Article 6.4. Technical criticism, however, is not moderated.
5.4 Automated access to the Service is permitted as long as it remains measured and does not degrade the Service for others: bulk cloning, scraping the interface, and calls to a programming interface once one is opened. We may rate-limit an account, a key or an address, and we do so before suspending. Tokens and access keys are personal: sharing them, or spreading them across several accounts to exceed a limit, is a circumvention within the meaning of 5.1(e). Content on the Service may not be extracted in bulk for resale or to build a prospecting file.
5.5 You do not resell the Service or give third parties access to it for payment.
5.6 In the event of a breach, Article 13 sets out what we do and in what order.
6. Reporting unlawful content
6.1 Any content publicly accessible on the Service can be reported to us at redalert@git.eu. The report must state the exact address of the content, the reason it is considered unlawful, and how to contact you.
6.2 We acknowledge receipt within 2 business days and issue a reasoned decision within 10 business days. Manifestly unlawful content is dealt with as soon as it is identified, without waiting for this deadline.
6.3 The decision is explained to the person who made the report and to the holder of the account concerned. The latter may respond to us and request a review. We will carry one out.
6.4 Depending on severity, we may remove content, make a repository private, or suspend or close an account. We take the least far-reaching measure that resolves the problem.
6.5 A manifestly unfounded and repeated report may lead us to stop acting on it.
7. Help space
7.1 From the time it goes live, the Service includes a public help space between users. It does not include private messaging.
7.2 The questions, answers and comments you publish there are made available under the Creative Commons Attribution 4.0 licence (CC BY 4.0). Code excerpts they contain are further placed under CC0 1.0. These licences are recalled below the input field.
7.3 You remain the author of what you publish. By publishing it, you accept that others may reuse it under the terms of these licences — including us, in our documentation.
7.4 These licences apply to contributions published from the time the space goes live. They do not apply retroactively.
8. Availability and support
8.1 No service-level commitment is made during the open beta: no uptime rate, no restoration time, no penalty. Such a commitment will appear in the commercial terms, not here.
8.2 The Service is operated to the best of our ability. We do not provide a permanent on-call rota: detection and handling of incidents outside business hours are done on a best-effort basis.
8.3 We may interrupt the Service for maintenance. Planned interruptions are announced and repositories are locked beforehand, so that no write is lost.
8.4 A beta is a trial phase. Bugs, regressions and outages are possible, and Article 18 draws the consequences.
8.5 Support is provided at support@git.eu, free of charge, with no guaranteed response time.
8.6 We may freely implement, without consideration and without time limit, the suggestions, comments and feature requests you send us during the open beta. This gives us no rights over code you might show us to illustrate your point.
9. Backups
9.1 We back up all repositories and the database daily, off the production site, in France, on hardware we own. Copies are encrypted and overwritten on a 30-day rotation. No other company holds a copy of your data.
9.2 These backups cover a loss occurring on our side. They do not replace your own copies: a Git repository cloned on your machine remains the fastest way to recover what you have deleted yourself.
9.3 There is no self-service restore: a restore is requested at support@git.eu and we carry it out. Annex II of the Data Processing Agreement describes the exact state of this arrangement, including what has not yet been tested, and it is updated when it changes.
10. Personal data
10.1 For the data you place in the Service, you are the controller and we are the processor. The Data Processing Agreement published at git.eu/dpa governs this relationship.
10.2 For data that concerns you as a person — your account, technical logs, correspondence you send us — we are the controller. The Privacy Notice published at git.eu/privacy describes this processing.
10.3 The list of our sub-processors appears in Annex III of the Data Processing Agreement published at git.eu/dpa. It is exhaustive: six companies, and no others. Any addition or replacement is subject to 30 days' notice, under the conditions of clause 6.3 of that agreement.
10.4 We deploy no third-party analytics, no advertising tracker, and no open-tracking pixel in our emails.
11. Reporting vulnerabilities
11.1 If you discover a vulnerability in the Service, write to us at redalert@git.eu before disclosing it publicly. We acknowledge receipt and keep you informed of how it is handled.
11.2 We will not take action in respect of research carried out in good faith, provided it does not access a third party's data, does not degrade the Service, and is not disclosed before a fix is available or a reasonable period has elapsed.
12. Intellectual property
12.1 The Service, the software that runs it, its interface and the git.eu and Git.eu France trademarks belong to us. These Terms grant you no rights over them, other than the right to use the Service for the life of your account.
12.2 You do not decompile the Service and do not attempt to extract its source code, except where the law permits you to do so.
13. Suspension and closure on our initiative
13.1 We may suspend or close an account in the event of a breach of Articles 2, 4 or 5, or where a legal obligation requires it.
13.2 Except in an emergency, in the case of manifestly unlawful content, or where a legal obligation requires otherwise, we notify you, state the reasons for the measure, and give you a reasonable period to remedy it.
13.3 During a suspension, reading and exporting your data remain available, unless the unlawfulness of the content prevents it or the law prohibits it.
13.4 In the event of closure for breach, you have 30 days to export your data. Manifestly unlawful content is deleted without delay and is not exportable.
14. Closure on your initiative
14.1 You may close your account at any time, without reason, free of charge and without notice.
14.2 Export your data before closing: closure triggers the deletion provided for in clause 14.2 of the Data Processing Agreement, i.e. 30 days, subject to the recovery period published in Article 15.
14.3 Deletion covers your account and your repositories. It does not remove what you have contributed to other users' repositories, nor copies others have made of your public repositories: a fork is a repository that belongs to them. Your commit metadata remains there, under the conditions of Article 4.5.
15. End of the open beta
15.1 The open beta ends on 30 November 2026.
15.2 On 1 December 2026, an account without a subscription switches to read-only. You retain read access, cloning, downloading and export; you can no longer push commits or open merge requests. Your data remains intact and belongs to you.
15.3 On 31 January 2027, accounts that remain without a subscription, and all their data, are permanently deleted. These two dates go together: the recovery window opened on 1 December closes on 31 January 2027.
15.4 We write to you before any deletion: 30 days, 7 days and 24 hours in advance, at your account's email address. This is a commitment, not an intention.
15.5 No payment is taken at the end of the beta. We hold no payment method, and no account switches to a paid plan without a subscription on your part.
16. Transition to commercial terms
16.1 Subscriptions open on 1 December 2026. They are governed by separate terms, published before that date, which you accept at the time you subscribe and not before.
16.2 These Terms cease to apply to an account on the day it takes out a subscription. They continue to govern non-subscribed accounts until they are deleted.
17. Changes to the Terms and the Service
17.1 We may amend these Terms, in particular to reflect a change in the Service or the law. Each version carries a number and a date, and previous versions remain available at git.eu/terms.
17.2 Any material change is notified to you by email at least 30 days before it takes effect. If it does not suit you, you may export your data and close your account before that date.
17.3 We may evolve the Service at any time during the open beta: add features, change them, remove them. The notice period in Article 17.2 concerns these Terms and does not extend to the Service's features. Notice regarding features will appear in the commercial terms referred to in Article 16.
18. Warranties and liability
18.1 During the open beta, the Service is provided free of charge and as is, with no warranty of availability, error-free operation, or fitness for a particular purpose.
18.2 Our liability may only be engaged in the event of proven fault and only for direct damages. Indirect damages are excluded, in particular loss of business, loss of opportunity, commercial loss, and the cost of reconstructing data of which you held a copy.
18.3 Given that the Service is free of charge during the open beta, our liability, and that of our sub-processors, is capped, for all breaches combined and for the whole duration of the open beta, at €60, or at your direct loss if that amount is lower.
18.4 If a third party brings a claim against us on account of content you have uploaded, or a breach on your part of Articles 4 and 5, you bear the consequences: the amounts we may be ordered to pay, as well as the entirety of the defence costs. We inform you without delay of any such claim.
18.5 A dispute between users — over content, a contribution, a licence, or a remark made in the help space — is settled between them. You waive any claim against us in respect of such a dispute, except where you establish a fault of our own.
18.6 Nothing in this Article limits our liability in the event of wilful misconduct, gross negligence or personal injury, nor does it prevent the rights the law grants to consumers.
18.7 On pain of being time-barred, any action against us must be brought within two years of the day on which you became aware of the damage. This period does not reduce those granted to consumers by law.
18.8 Our liability is not engaged: (a) where the damage results from use of the Service not in accordance with these Terms; (b) where it results from a third party, from you, or from a third-party product you use with the Service; (c) in the event of loss, disclosure or fraudulent use of your credentials, keys or tokens attributable to you or to a third party — Article 2.3 makes you responsible for this; (d) where it results from a suspension or closure carried out under the conditions of Article 13, including at the request of a competent administrative or judicial authority, or following a third-party report under the conditions of Article 6; (e) in the event of loss, alteration or destruction of content of which you held a copy and whose reconstruction is your responsibility, under the conditions already set out in Article 18.2; (f) where the Service does not meet a need that was not agreed between us, in particular regarding the sensitivity of the data you place there; (g) in the event of a security incident related to your use of the internet — loss, alteration, destruction, disclosure or unauthorised access occurring on the network or from it, outside our infrastructure.
18.9 The cap in Article 18.3 continues to apply after the transition to the commercial terms in Article 16, unless those terms provide otherwise.
19. Force majeure
19.1 Neither party is liable for a breach caused by an event of force majeure within the meaning of Article 1218 of the French Civil Code. Performance is suspended during the event; if it continues beyond 30 days, either party may terminate the contract without compensation.
20. Assignment
20.1 You may not assign your account or this contract.
20.2 We may assign this contract to any entity that takes over operation of the Service. The non-training undertaking in Article 4.4 and the Data Processing Agreement follow the assignment and cannot be weakened by it.
21. Miscellaneous
21.1 These Terms, the Data Processing Agreement and the Privacy Notice form the entire agreement between us in respect of the open beta.
21.2 The invalidity of one clause does not affect the others, which remain in effect.
21.3 Failure to rely on a breach does not amount to a waiver of the right to rely on it later.
21.4 Notices under these Terms are given by email. Those we send you — deletion notice under Article 15, changes to the Terms or withdrawal of a feature under Article 17, change of sub-processor, volume warnings, account suspension or closure — are sent to the address linked to your account. Those you send us are sent to the address indicated in Article 23 for the relevant matter.
21.5 Article headings are for reading convenience. They are not binding and, in the event of a discrepancy, the text of the Article prevails.
21.6 The following Articles survive the end of these Terms, however it occurs: Article 4.4 (no use of your content to train models), Article 4.5 (persistence of commit metadata in existing copies), Article 8.6 (licence over your suggestions), Article 12 (intellectual property), Article 14.3 (what closure does not remove), Article 18 (warranties and liability) and Article 22 (language, governing law and disputes).
22. Language, governing law and disputes
22.1 These Terms are published in French and in English. In the event of a discrepancy between the two versions, the English version prevails — except with regard to a consumer resident in France, against whom the French version is enforceable.
22.2 The contract is governed by French law.
22.3 In the event of a difficulty, write to us first at support@git.eu.
22.4 Failing an amicable agreement, the courts of Strasbourg have exclusive jurisdiction. This clause does not apply to a consumer, who retains the right to bring proceedings before the court of their place of residence or that of Git.eu's registered office, and does not affect mandatory rules of jurisdiction.
22.5 A consumer may make free use of a consumer mediator. [Mediator's name and contact details to be inserted before subscriptions open on 1 December 2026.]