Legal
Imprint, privacy and terms.
Imprint
Information according to § 5 DDG.
- Company
- KINAV GmbH
Jurastraße 27/1
72072 Tübingen
Germany - Register
- Amtsgericht Stuttgart, HRB 807824
- Managing director
- Oleksii Kvasnikov
- VAT identification number according to § 27a UStG
- [to be filled]
- support@kinav.com
Privacy
This notice says what this site and its downloads record, what Crabway sends, what its licence service keeps and why, and what rights you have. Last updated .
Who is responsible
The controller is KINAV GmbH, Jurastraße 27/1, 72072 Tübingen, Germany. Write to support@kinav.com with any question about your data.
What the server of this site records
Hostinger hosts this site for us. Its server records each request in a log: your IP address, the date and time, the page you asked for, the page you came from (the referrer) and your browser. We use this log to run the site and to keep it secure. The legal basis is our legitimate interest in a site that works and is safe, Art. 6(1)(f) GDPR.
Downloads
Downloads come from downloads.crabway.dev, which Cloudflare serves for us. Cloudflare records the same kind of log for each download, for the same purpose and on the same legal basis.
What this site does not do
crabway.dev sets no cookies and runs no statistics script. It loads nothing from other sites, except the checkout when you buy.
What Crabway sends
| What | To | When |
|---|---|---|
| git fetch and git push, with your code | Your Git servers | When Git fetches, pulls or pushes |
| Pull requests and issues | Services you connect | When you open them |
| The update check, with no ID | downloads.crabway.dev | Unless a setting turns it off |
| The licence check | Our licence service | Once a month, and as below |
| Get a key | Our licence service | When you press it |
| A bug or feature report: the title, the description, the steps for a bug, your email address for the answer, the version of Crabway, the system and its version, the desktop session and the Git version | Our GitLab Service Desk | When you press Send |
| Usage statistics | Nobody | Never |
| Code, paths, file names | Us | Never |
The licence check
Crabway asks our licence service for a pass once a month, in the background. When a check fails, it tries again after waits that double from 1 hour up to 24 hours, each with up to a fifth more at random. It also asks at once when you make a key from the portal your licence, press Check now or Try again, or answer the monthly question, and at most once a day when it finds an update that its pass does not cover. Each time it sends the key, a random computer ID, the computer's name, a public key made on it, a signature by its private key with the moment it was made, the version of the licence terms agreed on the computer and when, and for Non-profit, after the monthly question, the answer and when it was given.
When you press Get a key, it sends a random computer ID, the computer's name, a public key made on it, a signature by its private key with the moment it was made, and a random value made for that press: not the key, the version of the licence terms or an answer. No request sends a version of Crabway or anything of your work.
A licence belongs to an email address, which signs in to the licence portal with a link mailed to it. The service uses what it keeps to give each key its passes, to count the computers of each key, to sign you in, and to keep the record of each licence and of the terms agreed to it.
What the licence service keeps
| What | Kept |
|---|---|
| The email address, name and business of whoever manages a licence, for a paid one as the seller gives them | While the licence runs, then 1 year |
| The email address of whoever holds a seat | While the seat is held |
| A Non-profit application: the person's name, what the work is, and a link | While the licence runs, then 1 year |
| Each agreement to the licence terms: who, the licence and seat, the version and a hash of its text, the moment, and where, a page of the licence portal or Crabway with the computer's ID | Until three years after the end of the year in which the licence ended, also after an erasure |
| The last answer to the monthly question, and its day | As long as its licence |
| Each computer: its random ID, its public key, its name, the day it was first seen, its last check, and whether it was freed | Until 90 days after its last check |
| Payments: the seller's transaction ID, the day and the period | While the licence runs, then 1 year |
| Ended keys: a key's ID, a day and why, which hold no personal data | As long as the service runs |
| What the seller tells the service, as it was sent | 30 days |
| The mails the service sends | The text until it is sent, the record of it 30 days |
| Sign-in links, sessions and the tickets of Get a key, each only as a hash | Until each one ends |
| The audit log | 2 years |
| Backups | 35 days for a daily one, 400 days for the one of each month |
It never keeps your network address, as the service's request logs are off; your browser's description; a password, as there are none; card data, which only the seller holds; the text of a key, which is signed again each time it is sent; a computer's private key, which never leaves the computer; the plain value of any token or link; or anything of your work.
Who receives your data
The licence service and the licence portal run with a cloud provider, not with the web host of this site. The provider keeps their data and the backups in the EU, and sends their mail. Each request to them passes through its network, which sees your network address. What its network and its mail service log, it keeps as its own terms say.
When you buy, our payment provider takes the payment. It is the seller and a controller of its own: it holds your card data, keeps the invoices and tells the licence service of each payment.
Bug and feature reports reach our GitLab Service Desk through a mail relay, and stay there until they are resolved.
Backups
Every day, the store of the licence service is encrypted with a key that only we hold, and written to storage in the EU under a lock that lets no access token change or delete a copy before its time. Only a member of our account with the licence service's cloud provider can change the lock. Someone erased from the store stays in the backups until each one ends: 35 days for a daily one, 400 days for the one of each month.
The audit log
The licence service logs every change to a licence, by a person, by the seller, by the service itself or by us, and every record we read. A row holds the moment, the kind of actor and an ID, the action and the IDs it touched: never an email address or a key. Each row holds a hash of the one before, so that a row changed later shows. Only we read the log, and it is kept 2 years.
Your rights
You have the right to see the data we hold about you (Art. 15 GDPR), to have it corrected (Art. 16) or erased (Art. 17), to restrict its use (Art. 18), to receive it in a portable form (Art. 20), and to object to its use on the ground of our legitimate interest (Art. 21). Write to support@kinav.com for any of these, a copy of your licence data or its erasure included.
An erasure removes your email addresses and names, except from your agreements to the licence terms. Those keep who agreed for as long as the table says, as proof of what was agreed if a legal claim needs it. The IDs and the ended keys stay too: they hold no email address or name, and they keep an ended key ended.
You can also complain to a supervisory authority (Art. 77 GDPR), such as the LfDI Baden-Württemberg, the authority for data protection of the state where we are based.
Terms
The licence terms that come with Crabway. The app shows the same text.