Privacy Policy

Privacy policy (June 23, 2025)

Our goal is to only store data which is required for providing the service to you.

Our servers need to store names of user accounts you create and authentication credentials which belong to a user, i.e. hashed passwords and/or public SSH keys. Beyond this, there is no information stored on our servers which identifies a particular user. This provides fairly good privacy. However, the flip side is that you may well end up losing access to your data without your SSH credentials, since we may ask you to perform some action over SSH in order to authenticate requests you make of us.

For incident analysis, our servers keep rotating logs of IP addresses which access the servers via SSH or HTTP and HTTPS. Our web server logs also contain the submitted HTTP requests. Logs will be rotated out within 30 days.

Our web server may require a session cookie to be stored in your web browser when accessing Git repositories which require authentication. The cookie is only transmitted over SSH or SSL/TLS and encodes a numeric user ID of a user account in a virtual machine, and a validity timestamp. The cookie can be deleted by you at any time and recreated on demand by logging in again.

When you make payments, our fiscal host Chirpy Software SRL is required to pay VAT or sales tax in your country of residence. For this reason, our payment form may ask about your address. This information will be stored on the Open Collective and/or Stripe platforms. It is not stored on our own servers. Beyond Chirpy Software, a limited subset of our admin team is trusted with access to payment records on Open Collective and Stripe.

Data you upload to Git repositories will be stored in the virtual machine which corresponds to your Git repository space. If you request deletion of this data yourself, it will be removed immediately. Otherwise, the data may be kept for up to 4 weeks after you stop using the service, as explained in our Terms of Service.

Removing historical data from Git repositories is possible but is a destructive operation. If you require Git history to be changed, the easiest approach is to send email to admins@ and ask for the specific repository to be cleared of all content. You can then upload a new version of the history which you have rewritten/filtered yourself.

If your service tier includes backups, data you upload to Git repositories will be stored in our backup storage unless you choose to opt-out via email to admins@. When the repository space owner stops using the service, backed up data is kept for up to 4 weeks before being deleted.

If you lose your SSH authentication credentials we have no way of knowing whether a request made in your name is genuine. In which case, if you have previously contributed funds via Open Collective using an account which is known to correspond to your Git repository space, we might ask for a transfer of some random small amount of money from that same Open Collective account in order to be somewhat sure that we are still talking to the same person. You may be asked to join a video call with one of our admins while making this transfer. If that is not possible then the only solution will be to let your current Git repository space expire and book a new one. To avoid such problems, please keep your SSH credentials safe.

Please contact us on admins@ if you have any further questions.

Third party terms

Because we use Open Collective and Stripe, use of our service may require accepting the Open Collective Privacy Policy and the Stripe Privacy Policy.