BukDesk does not report on how you use it. What passes between your computers is encrypted and only they can read it. Information reaches us only when you buy, open an account, connect over the internet, visit the site or write to us.
1. Who is responsible
Bukchair Ltd, company no. 516675188, 95 Etrog St., Giv'at Ze'ev, Israel, is the controller of the database. The privacy officer is Asher. Privacy requests go to him at main@bukdesk.com.
BukDesk is sold to buyers in the European Union too. For now Bukchair has no representative in the European Union under Article 27 of the GDPR. Requests from the European Union go to the same address, main@bukdesk.com.
2. In short: what we know and what we do not
| Reaches us | Never reaches us |
|---|---|
| Your email address, and your sign-in details in a form a password cannot be recovered from | Keystrokes, mouse movements, what you copied, files and screens |
| Licenses, orders and invoices | Messages between AI sessions, and conversations with AI tools |
| The Premium subscription, and how many relay tokens were issued | Pairing keys and private keys |
| "My computers": a random id, the name you typed, the version, when it signed in and the country of the last sign-in | A computer's serial, its public key, and the list of which computers are paired with which |
| Language and theme | Security settings, the relay's address and pairing codes |
3. Between your computers
The mouse and keyboard, the clipboard, files, messages between AI sessions, and screen pictures once someone said yes go straight to the paired computer, encrypted. Only the two computers can read them.
4. On the local network
Each computer announces its serial every few seconds, and its name while "Pair now" is open. Anyone on that network can see these.
5. Over the internet: the relay
Only after someone opens it. The mouse, keyboard, copied text and messages then go encrypted through Bukchair's relay, relay.bukdesk.com, on Google Cloud in Israel. Older versions of the software reach the same relay as relay.bscale.co.il. Files and screen pictures never go through it.
What the relay sees: both computers' network addresses, when they connect, how much passes, and a token that changes every hour.
What it does not see: the content, keys, serials or the names of computers.
What it keeps: who is connected is held in memory only, until the connection ends. A network address is held in memory, hashed, for about ten minutes after its last use, to limit load. Once a minute it writes one line of counts, with no addresses, no tokens and no content. Those lines are deleted after 30 days. The relay keeps no record of who connected to whom.
What you should know: a computer that waits for a connection without a break shows a new token every hour, and for a moment the old one and the new one together. So whoever runs the relay can tell that it is the same computer from one hour to the next, and which network addresses it comes from, for as long as its connection stays open. We do not record this. Someone who took over the relay could see it from then on, but not the content.
6. Premium and the relay
Premium is not on sale yet. This section applies from the day it is.
Premium gives hours of connection through the relay. To count them, the relay has to know that whoever connects has paid, without knowing who they are.
The site checks that there is a subscription, and signs tokens for the software without seeing them. The software hands the relay one token for each stretch of time the connection is open, and the relay checks the signature against a public key.
What the site knows: how many tokens were issued to each subscription in each billing period. It does not see the tokens themselves, and does not know when they were spent, from where, or whether they were spent at all.
What the relay keeps: only the tokens already spent, so that none is spent twice, until the end of the month they are valid for. No subscription, customer or network address is kept beside a token.
Nobody, us included, can link a spent token to the customer who got it. The account shows how many tokens were issued, and the software shows how many are left. There is no log of connections.
7. Update check
Where updates are on, about every 12 hours, BukDesk asks one fixed address on Google Cloud Storage, with no serial, name, version or identifier. The provider sees the network address the request came from, and when.
8. The account, which is optional
Everything works with no account. If you open one, it keeps:
- Your email address.
- How you sign in: a password is kept only as a hash that the password cannot be recovered from. A passkey is kept as a public key only. The two-factor secret is kept encrypted, and recovery codes are kept as hashes.
- Active sign-ins: when you signed in and from which browser, so that you can see them and end them.
- "My computers": for each app that signed in to the account, a random id, the name you typed, the app's version, and when it first and last signed in. The country of the last sign-in is kept too, and shown to you in the list. It is the country only: the network address itself is not kept. The name defaults to the computer's Windows name, and is shown to you first so that you can change it. The id is not the computer's serial and not one of its keys.
- Settings: language and theme.
If you sign in with Google, we receive your email address and an account id from Google. When you choose a password, we check whether it has appeared in known leaks, against the Have I Been Pwned service. Only the first five characters of the password's hash are sent to it, never the password.
We send security emails to your address: a sign-in from a new device, a change to your factors, and a recovery request.
9. Buying and billing
Buying, or fetching a license from a link, gives us your email address, the name you type for the license, the name for the invoice, a company name and VAT number if you gave them, the country, the transaction and the invoice. We also keep the license's id, its signed text, and a hash of the link code. Payment goes through PayPal, which handles it under its own privacy policy. Card details never reach us.
With Premium we also keep the subscription's status, the billing period, and how many relay tokens were issued in each period.
10. On the site
- Cookies: essential cookies only. See the cookie policy.
- Measurement: the site loads no analytics or measurement script. It builds no profile and does not follow you between sites.
- Server logs: the network address is recorded shortened, and an email address is recorded as a hash.
- Protection against abuse: we limit the rate of requests by network address. The address is kept for that for a short time.
11. When you write to us
We receive your email, and any recorder files you choose to send. These may hold program names and pointer positions. An abuse report is kept with whatever you attached to it.
12. Marketing email
We send marketing email only to people who expressly asked for it. Every message has a way to unsubscribe. Messages about a license, an invoice, billing and security are not marketing and are sent in any case.
13. Message history
BukDesk keeps the messages that passed between AI tool sessions on your computer only, encrypted, for 30 days by default. You can change the period, turn it off and delete. The history does not reach us, is not kept in the account and does not go through the relay.
14. What we do not do
There is no telemetry. We do not sell personal data or use it for advertising. We cannot see what you type, what you copy, or your screen. We do not know which computers are paired with which, and we have no log of connections.
15. Why, and on what basis
| Why | Which information | Basis under the GDPR |
|---|---|---|
| To sell a license and Premium, send the license and provide the service | Buying and billing, the account, the relay | Performance of a contract, Article 6(1)(b) |
| To issue invoices and keep them | Buying and billing | Legal obligation, Article 6(1)(c) |
| To keep the service secure and prevent abuse | Logs, rate limits, the audit log, reports | Legitimate interests, Article 6(1)(f) |
| To send marketing email | Email address | Consent, Article 6(1)(a) |
No law requires you to give us information. Without an email address and invoice details you cannot buy, and without an email address you cannot open an account. The software can be downloaded and tried without giving us anything.
16. Providers
| Provider | What it does for us | Where |
|---|---|---|
| Google Cloud | The site, the database, the relay and the update files | Israel. A backup in a second region, in the European Union |
| Google Workspace | Our mailbox, main@bukdesk.com | In Google's data centres |
| PayPal | Payments | Under PayPal's policy |
| Resend | Sending email: licenses, invoices and account messages | United States |
The providers process information for us under an agreement. We pass information to authorities only when the law requires it.
17. Moving information out of Israel
Most of the information is kept in Israel. Some of it is kept or processed in the European Union and the United States, by the providers in the table.
18. How long we keep it
| What | How long |
|---|---|
| Invoices and transaction records | 7 years |
| An account | Until you delete it. It leaves the backups within 35 days of that. Daily backups are kept for 30 days |
| An active sign-in | Up to 30 days, or 7 days with no use |
| "My computers" | Until the computer is removed, signs out, or the account is deleted |
| The relay: network addresses | In memory only, about ten minutes after last use |
| The relay: lines of counts | 30 days |
| Premium: spent tokens, at the relay | Until the end of the month they are valid for |
| Recorder files you sent | 90 days |
| Support emails | 24 months |
| Server logs | 90 days |
| The log of admin actions | 7 years |
| The record of marketing consent | While the consent stands, and 3 years after it is withdrawn |
| Message history | On your computer only. 30 days by default |
19. Your rights
You may see the information we hold about you, ask us to correct or delete it, get a copy of it, object to its processing or ask us to restrict it, and withdraw a consent you gave. An account holder can export their information and delete the account from the account itself. For anything else, write to main@bukdesk.com and we will answer within 30 days. Before answering we make sure the request comes from you.
We give these rights to everyone, wherever they live. You may also complain to Israel's Privacy Protection Authority. If you live in the European Union you have the rights in Articles 15 to 21 of the GDPR, and may complain to the authority in your country.
Invoices are kept after an account is deleted, as the law requires.
20. Security
Between computers: end-to-end encryption, a private key for each computer in Windows Credential Manager, and signed updates. On the site: two-factor authentication, encryption in transit and at rest, staff access that is limited and recorded, and encrypted backups. No system is fully secure. If we learn of a security incident affecting your information, we will tell you as the law requires.
21. Requests from authorities
We pass information to an authority only when the law requires it. What we have is account and billing information. We have no logs of connections, no list of paired computers, and no content.
22. Children
BukDesk is not meant for anyone under 18, and we do not knowingly collect information about anyone under 18.
23. Changes
We publish changes here with a new date. A material change is shown in the software and emailed to account holders.
This notice is published in Hebrew and in English. If the two texts differ, the English text prevails.