Privacy policy
Last updated November 7, 2026
Who is responsible
Alexandre Le Borgne, entrepreneur individuel (sole proprietor under French law, micro-entrepreneur), publisher of Git Lucky, is the data controller. Contact: contact@gitlucky.dev.
Release announcement list
If you sign up on our home page, we keep your email address, the date you signed up and gave your consent, and which of the page's two forms you used. We use your address for one thing only: sending you one email when the first version of Git Lucky is released. The legal basis is your consent.
We send that email from our own server, hosted by OVH SAS in France: no mailing service receives your address. Once the email is sent, we delete the list. If no version is released within twelve months of your sign-up, your address is deleted then.
You can withdraw your consent at any time by writing to contact@gitlucky.dev. Your address is then deleted.
What we collect, and why
- What your sign-in provider sends us when you sign in with Google or GitHub: your account identifier at that provider, your verified email address, your name and your profile picture. We never receive your password. Used to create your account, recognise you at your next sign-in, and link a Google and a GitHub account that share the same verified email address.
- Your subscription (Stripe customer and subscription identifiers, status, currency, trial and period end dates): to know whether you can use Git Lucky, and whether you already had your free month.
- The email addresses your account has used, with the dates, and the address that started your free month: to grant one free month per person, including after you change your address or delete your account.
- Gifted access: the license keys you used and the access they gave, with their dates.
- Your computers: the name you gave them, operating system, processor architecture, Git Lucky version, last check date, and a fingerprint computed on your computer from its system identifier, the serial numbers of its motherboard and system disk, and the hardware addresses of its built-in network cards (these values never leave your computer, only the fingerprint does). Used to apply the two-computer rule; if any of these values changes, you sign in again. A public key created by Git Lucky on the computer, whose private part stays on it (in its security chip when it has one): each check is signed with it, so that your sign-in can't be reused from another computer. With each check, a fingerprint of the Git Lucky program files installed on the computer (SHA-256 hashes of three files, which say nothing about you or your repositories), compared with those of the published version to detect a modified copy of Git Lucky.
- Security and audit records: technical logs of our server (IP address, requested page, date), requests refused by our protections (IP address or computer fingerprint, date), and a record of the changes made to accounts, subscriptions, access and computers, whether by us or automatically. Used to keep the service secure, prevent abuse and fraud, and trace what happened to an account.
We process these data to perform the contract you entered into (account, subscription, gifted access), to meet our legal obligations (invoices) and, for security and audit records and the fingerprint of the program files, on the basis of our legitimate interest in keeping the service secure and preventing abuse.
Git Lucky itself does not send us your repositories, your code or your Git history. It only contacts our server to sign in to your account and check your subscription, sending the computer details listed above, to send us the errors of the program, and to send an error report when you ask it to.
Errors and error reports
Git Lucky keeps a log of its errors on your computer. Before writing it, Git Lucky masks access tokens, keys, email addresses and the path of your home folder. The log leaves your computer only with a report you send.
When Git Lucky meets an error in its own program (an unexpected error, a crash, an error it did not handle), it sends it to us on its own, without the log, a screenshot or a crash dump. It does not send errors that come from your repositories, your network or your remotes. An error contains its code and message, the program's call stack, the errors Git Lucky met earlier in the session, and the context of your computer: the versions of Git Lucky and of your operating system, the fingerprint of the Git Lucky program files, your processor architecture and language, the name of your computer and its fingerprint (the identifier Git Lucky uses for your subscription), your screens' sizes, the email address of your Git Lucky account or the code of a sign-in in progress, and the GitHub username Git Lucky is signed in with. The same error is sent at most once a day, with the number of times it happened. When our server cannot be reached, Git Lucky keeps it on your computer and tries again later, for thirty days at most.
A report is sent only when you click Send, from Git Lucky or by uploading on our report page a report file saved by an earlier version of Git Lucky. It completes the error it follows, and contains what you write, the same context, and the log entries of the last seven days, which may include the names of your repositories and of their remotes. When our server cannot be reached, Git Lucky keeps it on your computer and tries again later, for seven days at most.
Unless you untick it, the report includes a screenshot of the Git Lucky window, which shows what was on screen: file names, code, commit messages. After a crash, it also includes the crash dump that your computer wrote for Git Lucky: a copy of part of the program's memory at the time of the crash, which may contain any data Git Lucky was handling. You see the screenshot and the size of the dump before sending.
With an error or a report, our server records the IP address and the app or browser identification (user agent and, for a report, language) of the request. When your computer is signed in, or when you upload the file while signed in on our site, they are linked to your account so that we can answer you. Used to diagnose and fix problems in Git Lucky, on the basis of our legitimate interest in improving it.
Payments
Payments are handled by Stripe, which collects your payment details directly under its own privacy policy. We never see your card number.
Who receives your data
- OVH SAS (2 rue Kellermann, 59100 Roubaix, France), which hosts our server in France.
- Google or GitHub, only for the sign-in you choose; they process it under their own privacy policies.
- Stripe, for payments and invoices. Stripe may transfer data outside the European Union under the safeguards provided by the GDPR.
- Google, only if you write to contact@gitlucky.dev: our server forwards your message to our Gmail mailbox, under Google's own privacy policy.
We never sell your data and use no advertising or analytics trackers.
How long we keep it
- Release announcement list: until the announcement is sent, and at most twelve months after you signed up.
- Account, gifted access and computers: as long as your account exists, then three years after your last sign-in or the end of your subscription, whichever is later.
- Invoices and accounting records: ten years, as required by French law.
- Address history and free-month record: kept after your account is deleted, without any link to it, as long as free months exist, on the basis of our legitimate interest in preventing abuse.
- Security and audit records: at least one year, at most fourteen months. Those about changes made to an account are kept as long as that account's data.
- Errors sent by Git Lucky, and error reports with their screenshot and crash dump, IP address and user agent: six months.
- Sessions: thirty days. Requests to sign in a computer: fifteen minutes. Expired ones are deleted within a day.
- Backups of our database, kept on our server: data deleted from the database remains in them for up to five months, then disappears with them.
Cookies
We use a single cookie, set only when you sign in, to keep you signed in. It is strictly necessary for the service, so it does not require your consent.
Your rights
You can access, correct, delete or export your data, object to its processing or restrict it, by writing to contact@gitlucky.dev. You can also lodge a complaint with the French data protection authority, the CNIL (cnil.fr).