← Back to Karnex

Karnex Privacy Policy

Karnytine Labs LLC · Effective November 17, 2026

Karnex is a remote support and device management service operated by Karnytine Labs LLC ("Karnytine Labs", "we", "us"). This policy explains what information Karnex collects, why, who it is shared with, and the choices you have. It covers karnex.org, the Karnex console, the Karnex Agent installed on managed computers, the Karnex Viewer (the desktop app for Windows and Linux, and any later macOS build, and the Karnex Viewer app for Android), KarnexDesk (support ticketing, including karnexdesk.com, organizations' support portals such as yourcompany.karnexdesk.com, and the "Get help" window on managed computers), and Kara, our AI assistant. The Android app stores your sign-in token and display preferences on your device; if you turn on fingerprint sign-in, it also stores your account email, an on/off setting and its own sign-in credential for that phone, encrypted with a key held by Android Keystore that only a strong biometric check (such as your fingerprint) can unlock. It never stores your password. It does not collect location, contacts, photos, advertising identifiers or analytics.

1. Who this applies to

Karnex is used by organizations (our customers) to support and manage computers. There are two groups of people whose information we handle:

2. Information we collect

CategoryWhatWhy
AccountName, email address, job title, password (stored only as a salted hash), two-factor authentication secret and backup codes (stored protected), and for any security key you add, the name you give it and the key's public credential (never a secret; used only to check your sign-ins), for each phone on which you turn on fingerprint sign-in in the Karnex Viewer app for Android, a one-way hash of that phone's sign-in credential (never the credential itself), a label made from the phone's manufacturer and model, when it was set up and last used, the IP address it last signed in from, and when and why it was turned off (these records are deleted 90 days after it is turned off), and for any Microsoft or Google account you connect for sign-in, that provider's identifier for you and the account's email address, the date you accepted our policies, whether your email is verified, and the language you chose (used for the console, our emails to you and Kara's answers).To create and secure your account and to contact you about the service.
OrganizationOrganization name, team members and their roles and permissions, plan and subscription status, optional logo and subdomain.To provide the console, access control and billing.
Managed computersFrom the Karnex Agent: computer name, operating system and version, manufacturer, model, serial number, processor, memory, boot time, the signed-in username, network address, MAC address, the public IP address it reaches Karnex from, agent version and last-seen time; free disk space and processor load; and, on Linux, the desktop type (Wayland, Xorg or text console). The name you give the machine, its site and notes your team writes about it.To show your fleet, let you connect to the right computer, keep the agent up to date, and raise the monitoring alerts you set up (low disk, high processor load, offline).
Karnex Quick Assist for AndroidWhen someone uses the Karnex Quick Assist app on an Android phone or tablet with a code a technician gave them: the device’s name, manufacturer and model, its Android version, the app version and the public IP address it reaches Karnex from, which the organization sees like any other Quick Assist computer. The screen they share, the technician’s taps and typing, and chat messages are end-to-end encrypted (section 5); we can’t read them and don’t keep them. If the person turns on the app’s accessibility service, it is used only to perform the technician’s taps, swipes and typing while the screen is being shared. To add the technician’s typing, it reads the text already in the field being typed into and keeps it on the device for a few seconds; it never sends, saves or logs that text, and it doesn’t read or collect anything else. The app keeps one key that identifies it on the device, in storage only it can read.To let the person get help from the technician they invited, and to show the organization which device it is helping.
MonitoringThe alert rules your Org Admin sets, the alerts raised, and the email address alerts are sent to. For service and event-log monitors (RMM Automation add-on), a check runs on the computer every 5 minutes and returns whether each watched service is running and how many matching events appeared, with the newest matching event's ID, source and the first 160 characters of its message (which can include names the computer logged, such as a username); these checks are kept for a day, and alert details as long as the alert. Script monitors run a script your team saved on each covered computer on the schedule it sets; we keep each run's exit code and output for a day, and the last line of a failing run's output as the alert's detail. Disk-health and battery-wear monitors use the daily hardware inventory (below). If a rule is set to open a KarnexDesk ticket, the ticket holds the alert's details and the computer it is about. Scheduled reports your admins set up (which report, when, and the email addresses it goes to); each one is emailed through our email provider to those addresses with the report's data (machine details, patch status or alerts) attached.To tell you when a computer needs attention.
Remote sessionsWho connected to which computer, when, and for how long. We do not record or store the live content of a remote session: it is end-to-end encrypted between the computer and the operator's viewer (see section 5). The one exception is a recording an operator chooses to make (next row).To operate sessions, enforce plan limits and keep an audit trail.
Session recordings (optional, Karnex Elevate)If an operator uses "Record video" in the Karnex Viewer, a silent video of the remote screen as the operator saw it is uploaded from their viewer over TLS, converted to a compressed video, and stored for the organization, together with the computer, operator, date, length, resolution and size. If your organization has set a recording passphrase, the recording is encrypted on the operator's device before upload and we store it without being able to read it; only people who know the passphrase can watch it. Otherwise, unlike a live session, a recording is not end-to-end encrypted to our servers, because they must process and play it back. Who viewed, downloaded or deleted a recording is logged. The operator's own viewer also keeps a copy on their device.To give the organization a reviewable record of support sessions for compliance and quality. Nothing is recorded unless an operator starts it.
Privileged Access (optional, Karnex Elevate)When someone on a managed Windows computer asks to run a program with admin rights: the Windows user, the program’s path and file name, its SHA-256 hash, its publisher and whether its signature is valid, any arguments, the reason they give, and who approved or denied it (or which rule did) and any note they added. For temporary admin accounts issued by the organization’s team: the account name, who issued it, the reason and how long it lasts, and its password, which is stored encrypted. Kept as part of the audit trail (see section 7).To let people get admin rights only when an approver agrees, and to keep a record of it.
Local admin passwords (optional, Endpoint Security add-on)If an Org Admin turns on local admin password rotation, the name of the managed local admin account on each computer and its current and previous password. Each computer creates its own password and sends it encrypted; we store it encrypted and show it only to the organization's Org Admins and Admins, recording each time it is revealed. It is deleted with the computer or the organization.
BitLocker recovery keys (optional, Endpoint Security add-on)If an Org Admin turns on BitLocker key backup, each Windows computer's BitLocker recovery passwords, their key IDs, which drive they belong to and whether each drive is protected. Each computer sends its keys encrypted; we store them encrypted and show them only to the organization's Org Admins and Admins, recording each time one is revealed. They are deleted with the computer or the organization.
Compliance checks (optional, Endpoint Security add-on)If an Org Admin turns on compliance checks (or runs one), each computer's operating system and version, antivirus products and whether they are on and up to date, firewall and User Account Control state, disk-encryption state, whether a restart is pending, and the names of its local administrator accounts. Shown only to the organization's Org Admins and Admins; the newest result per computer is kept and deleted with the computer or the organization.
Software and hardware inventory (RMM Automation add-on)Once a day, the name, version and publisher of the programs installed on each covered computer, and its hardware facts: disks (model, size, health), battery capacity, make, model and firmware date. Shown to your organization in reports and monitors; the newest collection per computer is kept and deleted with the computer or the organization.
Backup status (optional, Backup Monitoring add-on)For the backup checks an Org Admin or Admin sets up, each covered computer reports every 6 hours when its last backup succeeded and failed, and the backup tool’s own message for a failure (from Windows Server Backup or Veeam Agent event logs, a Task Scheduler task, a systemd service, or the newest file time in a folder). Karnex only reads this; it never reads the files in your backups.
Network discovery (optional)When your team scans a network: the addresses that answered, their MAC addresses and names, which common ports were open and, if a community was given, their SNMP names. Kept for 30 days in the console list, deleted with the organization.
Network devices (optional)For devices and sites your team monitors: their name, address (or website link) and type; for SNMP devices the community (stored encrypted) and what they report (name, description, uptime, printer toner); for ping, TCP-port and website checks the latest response time; and the up/down history of each. The checks are run by a computer with Karnex on the same network. Deleted when your team removes the device or with the organization.
IT documentation and password vault (optional)Notes your team writes about clients and machines, and the credentials it stores in the password vault (name, username, link, notes and the secret). Vault secrets are stored encrypted and shown only to the people the entry is shared with, recording each time one is revealed. Documents and vault notes are stored as written (not encrypted beyond our normal storage). Deleted when your team deletes them or with the organization.
Commands and scriptsCommands and scripts your team sends to a computer, who sent them, when, and the output returned — including the installed-software list, Windows Update status and security status (antivirus, firewall, BitLocker; on Linux, the installed packages, pending package updates, firewall, disk encryption, AppArmor/SELinux, automatic updates, ClamAV and SSH sign-in settings) a technician looks up from a machine's Software, Updates and Security tabs. Uploaded script files. Automation tasks, patch policies, software deployments and app-update policies your admins set up (including installer links and the installed-app lists and versions they report) (what runs or which updates are approved, on which machines, and when or on which monitor alert), their run history, and patch-compliance results (updates still missing, last install result, restart pending). For a software deployment from a download link, if a computer can’t download the installer itself, our server fetches it from that link and passes it to the computer; we keep the installer only if it matches the deployment’s SHA-256 hash, and delete it after two weeks unused.To deliver and run them, show results, and keep an audit trail.
Support tickets (KarnexDesk)For organizations that use KarnexDesk: the requester's email address and name (when Kara opens a request on the portal for someone who isn't signed in, the name and email address they type, which they confirm with a code emailed to it), the email addresses of other people copied on a request (from the email's To and Cc lines, or added by the organization's team), who then receive copies of its public replies, the messages, notes and replies on each request, answers to the organization's request forms, the computer and client a request is about, who worked on it and what changed, and the requester's satisfaction rating and comment, the time team members log on it (how long, billable or not, and a note), the values of the organization's own custom fields on it, and which of its requests are linked to each other. If the organization has resolved requests signed off, who resolved each one and the person or team asked to sign it off. With the KarnexDesk ITSM add-on, also the problems, changes and releases its team records (descriptions, plans, root causes, reviews and who is assigned), each change’s approvers and their decisions and comments, service catalog requests and their approvals, its assets (name, type, manufacturer, model, serial number, location, notes, and the person or client they belong to) and how they relate to computers, tickets and each other, and its client contracts (hours, rates, dates and service levels). If an organization shows its logo in its ticket emails, the logo is loaded from karnex.org when the email is displayed, so our servers receive that request like any other web request; we don't use it to track whether emails were read. Email sent to an organization's KarnexDesk address arrives at our own mail server and becomes a ticket; the files and pictures attached to it are stored with the ticket, and our mail server notes the address of the server that sent it. An organization can block senders; email from a blocked address or domain is discarded. For 30 days we keep a mail log line for each email sent to an organization's KarnexDesk address, blocked ones included: the sender's address, the address it was sent to, its subject and size, when it arrived and what became of it (for example, which ticket it went to), so the organization can see what arrived. People an organization invites to its support portal sign in with emailed links; we keep their email, name and which client they belong to. We also keep the language a requester last used on the support portal, so the organization's emails to them are written in it. Live chat with an organization's team and the Karnex Chat app were retired on November 12, 2026; the data they kept (chats, and which team members' apps were signed in) was removed then, except a copy of each chat's record kept with the organization's tickets.To let the organization receive, answer and track requests, and to email the people involved.
"Get help" requestsWhen someone uses "Get help" on a managed computer: what they typed, the email and name they choose to give, the signed-in Windows user, and computer details (operating system, memory, uptime, free disk space, network addresses and agent version). A screenshot of their screen is included only if they tick the box; it is stored with the ticket (encrypted at rest) and only the organization's technicians can open it.So the organization knows which computer needs help and what state it is in.
Help articles (KarnexDesk)Articles an organization writes. Articles it marks public are shown on its support portal to anyone who visits; we count views and "Was this helpful?" answers.To let organizations publish self-help for their users.
Kara (AI assistant)What you type to Kara in the chat on karnex.org. When the Karnex team has to act, or you ask about a ticket, Kara opens a ticket for the Karnex team with her summary and that conversation, for the email address of your Karnex account, or, if you aren't signed in, the email address and name you give, which you confirm with a code emailed to it (we keep the code only as a one-way hash, for 10 minutes). When a technician chooses "Draft with Kara" or "Improve with Kara" on a ticket, the ticket's content is used to write a suggested reply (see section 4). When an organization has Kara Self Help turned on, Kara answers questions in the "Ask Kara" box on its support portal from the organization's public help articles and says she is an AI; the conversation is kept for 7 days, and when the organization's team has to act she opens a ticket for that organization with her summary and the conversation, for the signed-in contact or for an email address the visitor confirms with an emailed code.To answer questions about Karnex and to help technicians write replies. Kara's replies to technicians are suggestions: a person reviews a draft before it is sent. On an organization’s support portal (Kara Self Help add-on), Kara answers visitors directly, without a person reviewing each answer, and opens a ticket for the organization’s team when one is needed.
Translation suggestionsWhen you use "Suggest a better translation", the language, the console section you were on, the text you quote and your suggested wording, with your account.To improve Karnex's translations. Suggestions are reviewed by the Karnex team; they are not shared with anyone else.
BillingHandled by Stripe. We keep the Stripe customer and subscription identifiers, plan, and payment status. We do not receive or store full card numbers.To charge for the service and handle non-payment.
Technical dataIP address and request details in server logs, and security events such as failed sign-ins. To carry a remote session over whichever of our two US server locations (East or West) is nearer, we use the approximate location Cloudflare works out from the IP address of the managed computer and of the technician starting the session; we keep only which location is nearer (“east” or “west”), never the location itself.To operate, secure and troubleshoot the service and prevent abuse.
Sign-up recordsA one-way record of the email address used for a free trial (with any "+tag" removed) that remains after an account is deleted.To prevent repeated free trials.

Karnex does not use advertising or tracking cookies, and doesn't follow you across other sites. Our web pages (karnex.org and karnexdesk.com) use Cloudflare Web Analytics to count page views and measure how fast pages load: it sets no cookies, stores nothing in your browser and doesn't build a profile of you; it reports the page visited, the referring page, the browser and device type, an approximate country and loading times, and we only see totals. The console keeps your sign-in token in your browser's local storage so you stay signed in. If you tick “Don’t ask again on this device” when you complete two-factor authentication, we set an http-only cookie holding a random secret (we store only a keyed hash of it) so that browser can skip two-factor until the period your organization chose runs out.

3. How we use information

We do not sell personal information, and we do not share it for advertising.

4. Who we share information with

We use a small number of service providers who process information on our behalf, only to provide their part of the service:

Within an organization, information about its computers, sessions, commands, tickets and team is visible to the people the organization has given access. A person who contacts an organization through KarnexDesk sees only their own requests and the organization's public replies, never its internal notes. We may also disclose information when required by law or to protect the rights, safety and security of our users or the service. If Karnytine Labs is involved in a merger or sale, information may transfer as part of it, and we would tell you. If an Org Admin turns on Audit Streaming, the organization’s audit log (who signed in, changed a setting, revealed a password or key, ran a command or started a remote session, with names, email addresses and computer names) is also sent, as it happens, to the syslog server, Splunk instance or HTTPS address the organization chooses; that destination is the organization’s own choice and is handled under its own terms. If an organization sets up webhooks (including Slack or Microsoft Teams messages), details of the events it picks are sent (sessions, tickets, finished commands, monitoring alerts and Privileged Access requests: for example computer names, the technician’s name, a requester’s name and email, and the Windows user and program asking to run as administrator) to the address it chooses, under that service’s terms. Delivery records are kept for 30 days. If an organization connects its own identity provider (Enterprise Identity), signing in with it sends you to that provider, and it tells us your identifier there, your email address and your name, which we use to match you to your account (or create it, if the organization allows that); if it uses SCIM provisioning, its directory sends us the names, email addresses and directory identifiers of its people to keep their accounts up to date.

5. End-to-end encryption

The screen, keystrokes, clipboard, chat, files (including file names) and audio of a Karnex remote session are encrypted on the managed computer and decrypted only in the operator's viewer. Our servers relay this data but do not hold the keys and cannot read it, and we do not record it ourselves. The exception is a recording that an operator in your organization deliberately starts in the Karnex Viewer: it is captured on the operator's device from what they see, uploaded over TLS and stored so your team can review it (see "Session recordings" in section 2). Commands, scripts and their output, and account and machine details, are protected by TLS in transit but are processed by our servers as described above. The console's remote shell and file browser are protected by TLS and pass through our servers, like commands. More detail is on the Security page inside the Karnex console.

The Karnex Viewer keeps a few things on the operator’s own computer, not on our servers: for each machine it has connected to, the machine’s ID and its identity public key (so it can warn if that machine’s identity ever changes), and its own settings. The Linux and macOS Viewer stores these in the user’s configuration folder; its sign-in is kept only in memory while the app is open.

6. Security

Connections to Karnex use TLS. Passwords are hashed; two-factor authentication is available; roles and permissions restrict access within each organization. No system is perfectly secure, but we work to protect your information and will notify affected customers of a confirmed breach as required by law.

7. Retention and deletion

We keep information for as long as the account is active, with these exceptions. An Org Admin can set how long the audit log is kept; past that period, audit entries, finished commands, remote session records and Privileged Access history are deleted. Whatever that setting, the output of a command is shortened to its first 2,000 characters after 30 days, the history of runs made by automation is deleted after 400 days, and resolved alerts are deleted after 400 days. When a member is removed, their account is kept so an Org Admin can reactivate it, until an Org Admin deletes it or the person joins another organization. When an organization is disbanded, its people, computers, sessions, session recordings, scripts, notes, keys, webhooks, support tickets, ticket files, help articles and portal contacts are permanently deleted and installed agents are told to uninstall. Support tickets are otherwise kept for as long as the organization uses Karnex. We do not keep Kara chat conversations on karnex.org on our servers unless Kara opens a ticket, which keeps the conversation with that support request. Conversations with Kara on an organization's support portal are deleted after 7 days, unless she opened a ticket, which keeps the conversation with it. Session recordings are otherwise kept until an Org Admin deletes them or the retention period they set passes; deleting one removes the stored file. If an organization's service ends (a free trial that ended, a canceled subscription, or a payment still unpaid after its grace period) and no plan is chosen within 60 days, the organization is deleted in the same way; its Org Admins are emailed before that happens. Backups are retained on a rolling basis and age out: the continuous database backup within about three days, the daily copies within 14 days. We may keep limited records where the law requires it, for billing and tax, or to prevent abuse (for example the trial record in section 2).

8. Your choices and rights

You can view and update your account details in the console. You can turn on two-factor authentication and change your password at any time. Depending on where you live, you may have the right to access, correct, delete or export your personal information, or to object to certain processing. To make a request, email support@karnex.org. If your information is held on behalf of an organization that uses Karnex, we may refer your request to that organization.

9. International use

Karnex is operated from the United States and information is processed there and in other countries where our providers operate. By using Karnex you understand that your information may be transferred to and processed in the United States.

10. Children

Karnex is a business service and is not directed to children under 16. We do not knowingly collect personal information from children.

11. Changes

We may update this policy. If the changes are material we will notify account holders, for example by email or a notice in the console, and update the effective date above.

12. Contact

Karnytine Labs LLC
support@karnex.org