1. Who is responsible
- Kit Remote is operated by Kit Business Solutions Limited ("Kit", "we", "us"), 131 Continental Dr, Suite 305, Newark, DE 19713, United States, telephone +256 326 901 600. Kit is the controller of the personal data described in this notice.
- For privacy questions and requests, write to privacy@kit.africa.
- This notice covers the Kit Remote website at remote.kit.africa, Kit Remote accounts, the Kit Remote desktop app and the Kit Remote software installed on computers that receive connections, including computers on which Kit POS Desktop installed Kit Remote. Kit's other products have their own privacy notices.
2. What Kit Remote processes
Your account
- Your full name, organisation name and email address, when you accepted the terms of use, and when your account was created and changed.
- Your password, stored only as a salted one-way hash (scrypt). We cannot read it.
- Email verification codes and links and password reset links, stored only as hashes. They stop working after 30 minutes.
- While you create an account or change your email address, what you entered is kept with the code until you finish: for a new account your name, organisation, email address and password hash, for a change the new email address.
- Internal identifiers for your account. They are random codes that contain neither your name nor your email address.
- When you sign in to the desktop app through your browser: a sign-in request with the name and operating system of the computer the app runs on, a hash of the network address it came from, random one-time values that tie it to that app and to your browser session (the secret ones stored only as hashes) and, once you approve it, your account's internal identifiers. It can be used for 15 minutes and is deleted when someone next starts an app sign-in at least 15 minutes after that.
Organisations
- The Kit Remote organisations you create or belong to, their names and your role in them.
- If Kit verifies an organisation: its legal name, a reference to the evidence we checked, who at Kit verified it and when the verification starts and ends. If a verification is withdrawn: when, who at Kit withdrew it and why. Earlier verifications stay in the organisation's history.
Your connection profile
- Your profile: the name and organisation name of your account, unless you change them for your profile, and a photo if you add one. They are shown to the person at a computer when you ask to connect to it. Without a photo, that person sees your initials.
- Our server re-encodes every photo as a new square image, which removes embedded information such as location. The original file is not kept, and a replaced photo is deleted. If you remove your photo, it is deleted.
Computers
- When a computer is added to an account or organisation, as desktop app 1.0 did: its nine-digit Kit Remote ID, its computer name, the organisation it belongs to, the account that added it, the operating system chosen for the download, the IP address it was added from, and identifiers of the Kit Remote software installed on it.
- While the Kit Remote software on a computer is connected to our server: the IP address it connects from and when it connects and disconnects; when it connects, the computer's name, the type of operating system and the version of the Kit Remote software; identifiers of the Kit Remote software and a fingerprint of the code it runs; which of its features are available (for example whether it has a desktop to show); and, about every 15 seconds, a short signal that it is still connected, so that a computer that is switched off is shown as offline within about a minute.
- The Kit Remote software does not send our server the computer's hardware, network, signed-in users, programs, processes, services, antivirus or other system details, and it refuses requests for them.
- When you sign in to the desktop app, the computer's name and operating system, so that you can recognise the sign-in request you approve.
Computers without an account
- Installing the Kit Remote desktop app gives a computer its nine-digit Kit Remote ID without any account. Kit POS Desktop releases that include Kit Remote also install it, so that Kit support can help on that computer. Kit Business Solutions Limited is the controller in both cases.
- For such a computer our server keeps: its Kit Remote ID; the name "Computer" in place of its real name; whether its ID is active, dormant or turned off, and when and why it was turned off; a fingerprint of the key of the Kit Remote software on it (the key is made on the computer and stays there) and identifiers of that installation; which Kit Remote installer it was set up with; when it was set up, renewed and last connected (recorded at most once an hour); the type of operating system and the version and features of the Kit Remote software; and, for 7 days, when it connected and disconnected.
- To limit abuse of free IDs, our server also keeps keyed hashes (HMAC-SHA256, with a key kept on our server) of the network the computer was set up from (its IPv4 address or IPv6 /64, and the /24 or /48 network around it) and of the /24 or /48 network it last connected from. Because the key is on the same server, these hashes are pseudonymous, not anonymous, and they are deleted after 60 days. Our service logs hold only the first characters of them.
- Our records about such a computer keep neither its computer name nor its IP address, although the Kit Remote software sends both when it connects, as described above. IP addresses appear only where they do for every computer: in the server event log for 7 days, for each session, and in web server logs for up to 60 days.
- A computer that has not connected for 180 days is marked dormant. It keeps its ID, and it is active again when it connects.
- If the person at such a computer reports a request, we keep the report, the account and organisation of the person who asked, and a keyed hash of the /24 or /48 network the computer last connected from. Reports can lead to that person's account being suspended, after Kit reviews them or when computers on several different networks report the same person.
Your computer list
- Our server keeps your own list of the computers you connect to or add, and, for each organisation, a list of the computers its owners and admins add for it. The desktop app shows these lists from version 1.2. For each computer in a list: its nine-digit Kit Remote ID, the name given to it in that list (if any), whether it is in your own list or in an organisation's, the account that added it, and when it was added, last changed and, in your own list, removed.
- When the person at a computer approves your request, our server adds that computer to your own list, or shows it there again if you had removed it, unless one of your organisations lists it. The app also shows when you last connected to each computer, taken from your connection and approval records.
- Only you see your own list and the names in it. Every member of an organisation sees its list and names, and its owners and admins can add, rename and remove computers in it. A name you give a computer in your own list is never copied to an organisation's list. The prompt at the computer never shows these names: it shows your profile, not the name given to that computer. The members of an organisation, who may include people working at a computer in its list, see the organisation's list with its names.
- Our server records which account added, renamed or removed a computer in a list, and when, but not the name.
- When the person at a computer approves you, the Kit Remote software there tells our server how long the approval lasts. For your account, that computer and each kind of access approved (desktop or files), our server keeps when you were approved and when the approval ends, or that it lasts until the person at the computer revokes it. If the approval is for that session only, or the software does not say how long it lasts, we keep only when you were approved. These approval records belong to your account, also when a session counts against an organisation's plan. Only you see them, as the time left in the app. They hold nothing about what happened in the session, and they are not the approval itself, which stays on that computer, as described under "On the computer that receives connections".
- From version 1.2, the desktop app may also keep a small picture of a computer's screen on your own computer; see section 9.
Connections
- For each session: the account that connected and the plan it counted against (your own or an organisation's), the computer's ID, whether the desktop or files were requested, when the session was requested, started and ended, how much data it carried, how it ended, the answer given at the computer (allowed, declined, blocked, no answer in time, or none) and whether the person at the computer reported the request. A report also tells us how long the block given with it lasts; we record only whether it is for a time, until a date or for good.
- Sessions are relayed through our servers. We do not record the screen, keystrokes or the contents of files of a session. These connection records contain no names, email addresses or IP addresses; the server event log below does hold IP addresses, for 7 days.
Server event log
- The remote access server that Kit Remote is built on (MeshCentral) keeps an event log. It records when sessions to a computer start and end, with the internal identifier of the account, the IP addresses of both ends, how long the session lasted and how much data it carried; when a computer's Kit Remote software connects and disconnects; and changes to a computer's details. The Kit Remote software on a computer does not send its own messages about sessions to this log, so the log holds no names or paths of the files handled in a session.
Security records
- Sign-ups, sign-ins and failed sign-ins, password resets, email and password changes, and sign-outs, with the time and result. These records hold your email address and IP address only as keyed hashes. The key is kept on the same server, so the hashes are pseudonymous, not anonymous.
- IP addresses, to limit repeated requests and to lock sign-in for a while after repeated failures.
- Web server logs with the IP address, time and request, for connections of the Kit Remote software and sessions, and for errors.
- We send the emails your account needs: verification links and codes, password reset links, a notice when your password or email address changes, and a notice when someone tries to create an account with an address that already has one. Kit Remote sends no marketing email.
Cookies
- The pages of this website set no cookies and use no advertising, analytics or third-party tracking.
- The sign-up, sign-in and account pages use one session cookie (
xid, with its signaturexid.sig). It keeps you signed in and protects the forms. It ends when you sign out, and after 12 hours at most. - The desktop app keeps your session in its own storage on your computer and deletes it when you sign out. From version 1.1 it stays signed in for 30 days after you last used it, and its session ends when you sign out anywhere or change or reset your password.
- The remote screen page keeps the picture quality you choose in your browser's storage for this site: one entry holding the chosen setting, the same for every computer, with nothing about any computer in it. It is written only when you choose a setting other than Auto, removed when you choose Auto again, never sent to us, and stays until you clear this site's data in your browser. In the desktop app it is kept in the app's own storage and deleted when you sign out.
On your local network
- The desktop app looks for other computers running Kit Remote on your local network. Each computer that runs the app and has a Kit Remote ID answers with that ID, its computer name and an identifier of its Kit Remote software. This exchange stays on your local network; our server is involved only when you choose a nearby computer to connect to.
On the computer that receives connections
- The Kit Remote software keeps, on that computer, the approvals and blocks given there (the requester's display name and internal account identifiers, the account at the computer that gave the approval, what was approved and until when) and a consent log of requests and decisions.
- This information stays on that computer, under the control of its owner and administrators. It is not sent to Kit. Our server learns the answer given for each session and any report, as described under "Connections", and how long an approval given to the person connecting lasts, as described under "Your computer list".
- The Kit Remote software also writes a status file with the computer's ID and whether it is connected to our server (Linux
/run/kit-remote/host-status.json, WindowsC:\ProgramData\Kit Remote\status\host-status.json). Programs on that computer can read it, so that the Kit Remote app, and Kit POS Desktop where it installed Kit Remote, can show the ID. - When Kit Remote is uninstalled, the computer keeps its Kit Remote identity in a folder only administrators can read: the key behind its ID and the Kit Remote software's database, which also holds the approvals and blocks given there. Installing Kit Remote again therefore gives the computer the same ID. On Linux,
sudo apt purge kit-remotedeletes the kept identity. On Windows, an administrator can delete the folderC:\ProgramData\Kit Remote\host-identityand the registry keyHKEY_LOCAL_MACHINE\; Windows also keeps the Kit Remote software's key in its own key store until another installation replaces it. Resetting the computer's ID in the Kit Remote app gives the computer a new ID and, if the computer is online, turns the old one off.SOFTWARE\ KitRemoteHostIdentity
3. Why we use it
| Purpose | Legal basis |
|---|---|
| Create and run your account, show your profile to the person at a computer you ask to connect to, add computers, and set up and relay sessions | Performance of our contract with you (the terms of use) |
| Send the emails your account needs | Performance of our contract with you |
| Protect accounts and computers, limit abuse, investigate reports and enforce the terms | Our legitimate interest in a secure service that is only used with consent |
| Give a computer its Kit Remote ID without an account, relay the sessions the person at it approves, and limit abuse of free IDs | Our legitimate interest in delivering the help the person at the computer asks for, and in preventing abuse |
| Meet legal obligations, answer lawful requests and establish or defend legal claims | Legal obligation and our legitimate interests |
We do not sell personal data, show advertising or build marketing profiles.
4. Who receives data
- The person at a computer you ask to connect to sees your profile name, organisation and photo if you added one (otherwise your initials), whether Kit has verified your organisation, and what you ask for. The Kit Remote software on that computer also receives your account's internal identifiers and, for a verified organisation, Kit's reference for it, and keeps them with the approvals, blocks and consent log there.
- Our service providers process data for us under contract, only for the service they provide:
| Provider | What they do | Where |
|---|---|---|
| DigitalOcean | Servers that run Kit Remote and hold its data | Bangalore, India (region blr1) |
| IONOS | Sends Kit Remote's account email | Outside Uganda |
| Stripe | Payments, only once paid plans open. Kit Remote takes no payments today and sends nothing to Stripe. | Outside Uganda |
- We disclose data to courts, regulators or law enforcement only when the law requires it.
5. Transfers outside Uganda
Kit Remote's servers are in India, and our providers may process data in other countries. Personal data is therefore processed outside Uganda. We protect these transfers with appropriate contractual, organisational and legal safeguards, and limit the data to what each service needs.
6. How long we keep it
| Data | How long |
|---|---|
| Account, profile, organisation and computer data | While your account exists. Deleted within 30 days after you ask us to delete your account at privacy@kit.africa. A Kit Remote ID is never given to another computer, so a record of each ID is kept: the ID, the organisation it was issued to, the internal identifier of the account that added the computer, the identifiers of the Kit Remote software that held the ID, and when the computer was added, confirmed and removed. |
| Your own computer list, with the names in it | While your account exists. A computer you remove from your list is hidden, not deleted: it is kept with its name so that you can undo the removal, and it shows again when the person at that computer next approves your request, unless one of your organisations lists it. A hidden computer is deleted when your list is full (500 computers) and another one is added. |
| An organisation's computer list, with the names in it | While the organisation exists. A computer is deleted from the list when an owner or admin removes it. |
| Records of who added, renamed or removed a computer in a list | Kept as the list's history. We have not set an end date yet. |
| Approval records (how long the approval a computer gave you lasts) | Until the approval ends; our server deletes ended ones once a day. When the computer did not say how long the approval lasts (as for an approval for that session only), until you are next asked there for that access. Deleted earlier when our server learns that the approval is gone: the person at the computer is asked again about your request for that access, blocks you, or ends a session by revoking the approval, or the computer is moved to another account or organisation. Deleted within a day after the computer's Kit Remote ID is turned off, and at the latest about 12 months after you were last approved there. If the approval is revoked at the computer while you are not connected, our server learns it only when you next ask to connect. |
| The record of each ID of a computer without an account: the ID, its state and history, the identifiers of the Kit Remote software and installation that held it, the installer it was set up with, and dates | Kept for good, so that the ID is never given to another computer. |
| Keyed hashes of the network a computer without an account was set up from or last connected from | 60 days after it was set up or renewed, or after it last connected. In a report: 30 days. |
| A computer without an account in the remote access server's database (ID, the name "Computer", software version and features, connection times) | While it has its ID. Deleted within 30 days after its ID is turned off, and within two days if its setup never finished. |
| Reports made on a computer without an account | 12 months |
| App sign-in requests | Usable for 15 minutes, then deleted when the next app sign-in starts at least 15 minutes later |
| What you entered to create an account or change your email address | Until you finish or start again, or until we delete it. The code or link stops working after 30 minutes. |
| Verified-organisation records, including withdrawn ones | Kept as the organisation's history. We have not set an end date yet. |
| Server event log | 7 days |
| Connection records and security records | 12 months |
| Web server logs (IP address, time and request) | Up to 60 days |
| Backups | Up to 35 days, so deleted data leaves our backups within 35 days |
| Approvals, blocks and the consent log on a computer that receives connections | On that computer, under its owner's control. Approvals and blocks end when they expire or are removed there. Kit holds no copy of them, only the approval records described above. |
7. How we protect it
- The website, accounts and sessions use encrypted connections (TLS 1.2 or later) to our servers.
- Passwords are stored as salted scrypt hashes; codes and reset links only as hashes.
- The service runs under its own restricted system account, and its data directory is readable only by that account.
- Forms are protected against cross-site requests, repeated failed sign-ins are rate limited and locked, and signing out ends your sessions in every browser and the desktop app.
- Connecting to a computer needs an approval from the person at it, as described on the security page. Our servers do not record the screen, keystrokes or the contents of files of a session.
- No internet service can be perfectly secure. Keep your password and codes secret, and tell us at support@kit.africa if you suspect misuse.
8. Your rights
- In your account you can see your details and change your connection profile. If you created your account with an email address and a password, you can change them there too.
- Subject to the law of Uganda, you can ask for a copy of your personal data, ask us to correct or delete it, and object to or ask us to restrict how we use it. Write to privacy@kit.africa from the email address of your account. We delete an account within 30 days of a deletion request.
- For a computer that has a Kit Remote ID without an account, write to privacy@kit.africa with its ID to ask us to turn the ID off and delete our server's entry for it; we may ask you to show that you can use that computer. The record of the ID stays, as described in section 6, so that the ID is never given to another computer. On the computer itself, you can uninstall Kit Remote, remove its kept identity or reset its ID, as described under "On the computer that receives connections".
- We check that a request comes from the account holder before we act on it. We will never ask you for your password or a verification code.
- You can complain to Uganda's Personal Data Protection Office.
9. Data you see during a session
The person connecting may see personal data on the other computer. They are responsible for handling it lawfully and only for the help that was agreed (terms of use, section 4). Kit does not record the screen, keystrokes, or the names or contents of files of a session; the server event log keeps when sessions started and ended for 7 days.
From version 1.2, the desktop app of the person connecting may keep a small picture of the other computer's screen on their own computer, so that they can recognise that computer in their list. The app does not send the picture anywhere: it is not sent to Kit, and Kit's servers never receive it. The app takes at most one picture in each desktop session, 5 seconds after it connects, and none in a files session; it reduces the picture to at most 80 by 50 pixels before saving it, and shows it blurred. It keeps the newest picture of each computer, at most 50 pictures, only for the account signed in to the app. It deletes every picture when the person connecting signs out, or the app finds that they were signed out, for example when their sign-in expires or they signed out everywhere in the browser; when another account signs in to that app; and when they turn off Screen previews in the app. When they remove a computer from their list in the app, the app deletes that computer's picture from the computer they removed it on. Copies in the app on their other computers, and on other members' computers when an organisation's computer is removed, are deleted by the 60-day rule below, unless a rule above deletes them first. When the app starts, it deletes pictures older than 60 days. Screen previews are on unless the person connecting turns them off.
10. Children
Kit Remote is for people aged 18 and over. If you believe a child has given us personal data, write to privacy@kit.africa and we will delete it.
11. Changes to this notice
We will publish every change on this page with a new "last updated" date and announce it in the changelog.
12. Contact
- Privacy and account deletion: privacy@kit.africa
- Support and security reports: support@kit.africa
- Everything else: info@kit.africa
- Post: Kit Business Solutions Limited, 131 Continental Dr, Suite 305, Newark, DE 19713, United States. Telephone +256 326 901 600.