Short version: Khayt keeps your book on your own machine. We do not collect, transmit or hold your business data. Sync and offsite backups are sealed with your key before they leave, so we hold ciphertext, not records. Library files you keep in Google Drive or your own storage bucket are stored there as they are. The customer-facing services are different: a storefront, an order-tracking link or an order form has to be readable by the customer it is for, so what you publish through one is stored by Khayt Cloud in a form it can read. So are an iPhone's Live Activities, which iOS draws without a key, and — only if you turn it on — a copy of your customers and their orders for your own web store. Section 5 lists exactly what that is.
1. Who we are
Khayt is a desktop application for 3D print shops: quoting, a production queue, invoicing, inventory and the numbers behind them. It is developed and maintained by Khayt. Contact: support@khaytapp.com.
2. Data we do not collect
Khayt is local-first. We never collect:
- Your customer data, order information or business records
- Your inventory, pricing or financial data
- Personal information of any kind
- Your files — models, photos, PDFs — or anything you typed
- Your API keys, PINs, tokens or other secrets
Crash reports and anonymous usage counts are off by default and are only ever sent if you explicitly turn them on. The one thing sent without asking is a once-a-day anonymous count that an install exists, which carries no identifier and which you can switch off. Section 11 says exactly what each of these contains.
What you choose to send us. If you report a problem with Help ▸ Send Feedback on the Mac, the app prepares an email to support@khaytapp.com in your own mail app, and nothing goes until you press Send. It attaches a diagnostics file (app and macOS versions, language, region, window size, and how many jobs, customers, machines, spools and library files your book holds — counts, not contents), a picture of the window you were in, which can show customer names and prices, and — only if you tick the box — a copy of your book with every password, key and token masked. The rest of the book, including your customers, is in that copy. We use what you send only to investigate the problem you reported.
The beta list (closed). Until 7 November 2026 you could ask on khaytapp.com to be told when a beta was ready. That list is closed: the form is gone and nothing new is collected. The email addresses on it, with the app asked about, the language and the sign-up and confirmation times, were deleted from Khayt Cloud on 7 November 2026; copies in Khayt Cloud’s backups age out on their usual schedule (below), so the last are gone by 8 December 2026. Nothing more will be sent to it.
3. Where your data lives
Everything you enter is stored on your own device, in the application's data directory. Khayt does not sync your book to any cloud service operated by us unless you switch that on. Backup files you create are saved where you choose. If you enable iCloud Backup on macOS, your data is in your own iCloud account and Khayt has no access to it.
The Save to Khayt browser extension. The extension, for Safari, Chrome, Edge, Brave, Vivaldi and Firefox, saves a model’s web page into the Khayt library on your Mac. It reads a page only when you press its button, and only the tab you are on. It makes no network connections of its own: what it read (the page’s title and link, creator, licence, tags, a short excerpt of its description, its picture’s address and the links to files on the page) goes only to the Khayt app on that Mac, never to Khayt’s servers. A link the page gives for itself is kept only if it is on the same site as the tab; otherwise the tab’s address is kept. The Mac app then downloads the page’s picture from the address the page gives, over a secure connection only, sending no cookies or passwords and never from a machine on your own network, and keeps a small copy (at most 480 pixels a side) if it is a JPEG, PNG, WebP or GIF picture of at most 8 MB. The saved model becomes a library record in your book with the page’s link, site, creator, licence wording, description excerpt, file links, tags and when it was saved; the picture’s address is not kept. Like any library record, it travels with your book if you sync it or back it up to Khayt Cloud, and the iPhone app can show it (section 6). None of it appears on customer pages, vault share or product pages, or makerrun.com. Saving is on unless you turn off “Accept pages saved from the browser” (Settings ▸ Preferences ▸ Browser extension) on that Mac.
What the extension may see in your browser. In Safari it asks for three permissions: to read the tab you are on when you press its button, to run its reader in that tab, and to talk to the Khayt app. In Chrome, Edge, Brave, Vivaldi and Firefox it asks for two more, to see your downloads and to keep a short note while the browser is open, and it talks to a small helper inside the Khayt app that the browser starts only when the extension needs it. The helper makes no network connections, never opens your book and never starts Khayt; it hands each save to Khayt through Khayt’s own folder on your Mac. Khayt adds the small file each browser needs to find the helper only when you press Install in Khayt’s settings, and removes only that file when you press Remove; to show which browsers are set up, it reads those files and asks macOS which browsers are installed. The downloads permission lets the browser show the extension every download’s file location, address, referring page, time and state, and the extension uses it for one thing: for 10 minutes after a save, if a model file finishes downloading from the same tab, from that page or another page on its site, or from one of the file links on it, the extension tells Khayt the page’s link and the file’s name and location. Every other download is ignored and nothing about it is sent. The saves of the last 10 minutes (page link, file links, tab and time) are kept in the browser’s memory for this and cleared when the browser quits. Safari offers no way to see downloads, so for 10 minutes after a Safari save the Khayt app looks at the names and sizes of new files in your Downloads folder, which macOS asks you to allow. Either way, Khayt asks before adding the file: it reads the file only after you choose Add to Library, then copies it into your library and leaves the download where it is.
4. Google Drive
Khayt can connect to your Google Drive, and only if you ask it to. It is off until you connect an account.
The only scope Khayt requests is drive.file. That scope covers only files Khayt itself creates. It gives Khayt no access to anything else in your Drive — not documents, not photos, not files put there by any other application.
What Khayt puts there. Two things, both into your own Drive:
- Your print library — the model files themselves — in a folder Khayt creates called Khayt print library.
- Offsite backups of your book. These are sealed on your Mac with your own Khayt Cloud key (AES-256-GCM) before they are uploaded. Khayt refuses to upload a backup at all if there is no key to seal it with.
What Khayt reads. The email address of the connected account, so the app can show you which account it is using, and how much space is used in that Drive, so it can warn you before an upload fails. Both come from Google's own Drive about endpoint under the same drive.file scope. Khayt does not request a profile or contacts scope and cannot read your name, photo or contacts.
Where it goes. Between your machine and Google. The data moves directly from the app to Google's servers; Khayt's servers never receive it and we never see it. It is not sold, shared, used for advertising, or used to train AI or machine-learning models — by us or by anyone on our behalf.
How to revoke access. Either way works, at any time:
- In Khayt: Disconnect this Google account.
- In your Google account: myaccount.google.com → Security → Third-party access.
Revoking stops all further access immediately. Files Khayt already placed in your Drive stay in your Drive — they are yours — and you can delete them like any other file.
Khayt's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Khayt Cloud
Khayt has an optional, opt-in cloud. It ships switched off, and a shop that never turns it on gets the whole app with no account to create and nothing leaving the building.
When you do switch on sync, your book is encrypted on your own machine with a sync passphrase that never leaves it, and the server stores the result. The server holds ciphertext it cannot read. The consequence follows from the design and is worth knowing before you switch it on: a lost passphrase cannot be reset for you, because a recovery path that did not involve you would mean the server could read the data.
Your Khayt Cloud account. If you create one, Khayt Cloud keeps your email address, your password as a one-way hash (bcrypt) and never the password itself, which shop you belong to and your role in it, whether you have confirmed your address, when the account was made, and your shop’s plan and its status. It does not ask for your name or phone number. For each device you sign in on with your email and password, it keeps your email address, when that device signed in and the day it was last used; a device that goes unused for 90 days is signed out and its record deleted. For your shop it keeps only a hash of the sync token, not the token. A team invitation keeps the invited address, the role and a hashed code until it is used or expires. Khayt Cloud emails you, through our email provider, only about your account: a code to confirm your address, a password reset code, a team invitation, and, if your shop moved up for free during the beta, a notice when its 30 days after the beta begin and another 7 days before they end; and, if your shop moves to a smaller plan while its vault holds more than that plan allows, a notice giving the date files will be deleted and reminders 30, 7 and 1 day before it, as the terms (“Moving to a smaller plan”) describe. It records when each of these notices was sent; the times of the smaller-plan notices are erased once the vault fits again, or when your shop is deleted.
The weekly summary. Once Khayt switches it on, Khayt Cloud emails each shop’s owner on Sunday mornings, through our email provider, in English and Arabic, with last week’s counts: order requests, quotes approved and declined, customer messages, payments, reviews, storefront views and vault downloads. A week with nothing in it sends nothing. For this Khayt Cloud keeps only those weekly totals for each shop, never who did what, and deletes them after 8 weeks, and with your shop. Every summary has a link that stops it; it needs no sign-in, and asks you to press a button, so a mail scanner opening the link changes nothing. The owner can also turn it off in the app. Khayt Cloud records on the owner’s account whether the summary is off and the last week it was sent for.
Other online services — the storefront, order tracking, messaging, the AI assistant — each have their own switch, and each is described service by service, including exactly what it transmits and to whom, on the online services page.
What the cloud can read. The services your customers use cannot be end-to-end encrypted, because the customer opening the page holds no key. So when you switch one on, what you publish through it is stored by Khayt Cloud in readable form:
- Storefront — the products, prices, photos and promo codes you publish, and the ratings and comments customers leave.
- Order tracking and the customer portal — for each order you share: its details and stage, the customer's email address, the payment link, the messages exchanged on it, and any photos of the order you add (see section 6). Once an order has shipped, the app also sends what its shipping card shows: the carrier’s name, the delivery status, the tracking number and an https tracking link. A republish without them, or unsharing the order, removes them. Your shop can also set one payment link of its own for all its orders: Khayt Cloud keeps only its address and label, and shows it as a Pay button on the customer’s order page. The button opens your payment provider’s page directly, without passing through Khayt or being counted, and the deposit or balance due may be written into the address, so your provider sees it. The customer pays you, not Khayt.
- The customer portal — a customer can sign in at cloud.khaytapp.com/portal with their email address and a one-time code emailed to it. A code is sent only if an order has been shared with that address; it is stored only as a hash, works once and expires after 15 minutes. Once signed in, the customer sees every order and quote that any Khayt shop has shared with that email address — the shop’s name, the reference, the status, the amount and whether it is paid — and can order one again, which sends that shop a new order request with their email address and what was ordered. They can also rate an order: the rating is stored with their email address, and the shop’s public reviews show only its first letter. The sign-in lasts at most 7 days, and the browser forgets it when its tab is closed. A shop can choose to keep its orders out of that list across shops; its orders then show only when the customer opens the portal from that shop’s own pages, and Khayt Cloud stores nothing more about the customer for it.
- Live Activities — a printer's name, its job, the print's phase and progress, and its start and estimated end times, relayed to Apple for a phone showing that print on its Lock Screen (see section 6).
- Order requests — what a customer submits through your online order form or storefront checkout, held until you import or delete it.
- Instant quotes — the pricing inputs you publish so the storefront can quote (your rates and margin). Callers are shown a price, never those inputs. Outside the quote form below, a model file a customer uploads for a quote is priced in memory and not kept.
- The quote form for your store (off unless you turn it on, and shown only on the store addresses you list) — a visitor to your store can upload a model file (STL, OBJ, 3MF, STEP or G-code, up to 32 MB) and send it with a quantity, their name, an email address or phone number, notes and a link to their model. Khayt Cloud prices the file on its server against the quote sheet your Mac published. The price shown is an estimate, which you confirm. A STEP file cannot be priced on the spot, so no estimate is shown and it arrives as a request for you to price. The request and the file are held for you in readable form: the file is not end-to-end encrypted, because you have to open it, and every member of your shop can download it. The file is deleted when you import or delete the request, 14 days after the request arrived at the latest, within about a day if the visitor never sends the request, and with your shop. If your shop has no file storage set up, the file is not kept and the request arrives without it. The form, its frame and its loader script set no cookies, store nothing in the visitor’s browser and load no third-party scripts, and the loader reads nothing on your store’s page. A script error in the form may be reported to our error-monitoring service, as on our other pages. If the visitor gives an email address, Khayt Cloud also keeps it, with their language (from the form, or from their browser), apart from the request, so that when you publish an order from it, it can send them one email, through our email provider, with your shop’s name, the order reference and the link to their order page, where they can approve a quote, pay and message you. Once that email has been sent, the address is erased and only a note that it was sent is kept; either way, this is deleted 60 days after the request arrived, and with your shop. If, after seeing the price, the visitor asks for it by email (“Email me this quote”), Khayt Cloud uses the address they type only to send them that one email, through our email provider, with your shop’s name, the file name, the quantity, the estimate and a link back to your form. The address is erased once that email is sent and is not given to you unless they go on to send the request. Nothing else about the email is kept, except two counters, both deleted within about an hour: one, keyed to the estimate and without the address, stops the same estimate being emailed more than once an hour; the other, keyed to a one-way hash of the address (never the address itself), limits how many emails one address can be sent. The visitor’s IP address is used only to limit abuse, as described below. For this data Khayt acts as your processor (section 10).
- Customer records for your web store (Mac; off unless you turn it on) — so that your own web store can show a signed-in customer their past orders and let them order again. This is a readable copy, outside your encrypted book. While it is on, the Mac uploads, for each customer who has an email address: the email, name and phone number, and up to their 100 most recent orders (order number, the web store's reference, date, title, stage, the total they paid and its currency, and what was ordered, with quantities). It never includes your costs, margins, notes or files. The cloud can also hold up to ten delivery addresses per customer, though the Mac sends none today. The copy cannot be listed: your web store, using your shop's own access key, looks up one customer at a time by email address, and it must show a record only to someone who has proved they own that address. Each upload replaces the whole copy, so a customer you delete is gone from it at the next one. Turning the switch off deletes the copy at once; a copy the Mac has not refreshed for 30 days is deleted automatically, and deleting the shop deletes it too.
- WhatsApp delivery reports (Mac; off unless you set it up) — when you send customers WhatsApp messages through your own WhatsApp Business account, the Mac sends them straight to Meta; Khayt Cloud sends nothing and never sees what a message says. Meta reports what happened to a message only to a public internet address, which your Mac is not, so the cloud receives those reports for your account and keeps, for each message: Meta's message ID, its status (sent, delivered, read or failed), the time, the customer's phone number, your business number's ID, and any error code and description. Customer replies that reach the same address are counted and dropped, never stored. To check that a report really came from Meta, the cloud keeps your Meta app's secret and a verification token (see section 9). Reports are kept for 30 days after a message's last change. Removing the connection deletes it and every report, and deleting the shop deletes everything.
Your book itself is not among them: published records are copies you chose to share, and unpublishing one deletes it from the cloud. Server errors may be reported to an error-monitoring service (Sentry) so that we can fix them. None of this data is sold, used for advertising or used to train AI models.
Khayt Vault
Your library in the cloud, end to end. If you keep library files in the Khayt Vault, each file is encrypted on your own devices before it is uploaded, under a key that Khayt Cloud never holds. The cloud stores only the encrypted result. It cannot read a file's name, folder, thumbnail or contents, and so it cannot scan them. What it does see is each file's size and number of pieces, when it was uploaded and which of your devices uploaded it, and a tag that tells it when the same file is uploaded twice in your shop. That tag cannot link a file to another shop or to a known file. A file you delete stays in the vault's Trash for 30 days and is then deleted; older versions of a file are kept until you delete them, and no plan limits how long they are kept today; if a plan ever does, they will be deleted after that period. The one exception: if your shop moves to a smaller plan and its vault still holds more than that plan allows on the date Khayt emailed you, older versions are among what is deleted, as the terms (“Moving to a smaller plan”) describe.
Share links. A share link looks like https://cloud.khaytapp.com/s/…#…. The part after the # is the key, and browsers never send it to the server, so Khayt Cloud cannot open what a link shares. If you add a password, it is mixed into that key on your device and is never sent either. The link’s key is kept in the Keychain of the Mac that made the link, not in your synced data, so only that Mac can copy the link again; your shop’s other devices can see the link, extend it, change who it is locked to and revoke it. For each link the cloud records when it was opened, when a file was downloaded and when a download was refused, with the file, the visitor’s country and whether they used a phone, tablet or computer. It keeps the last 500 of these per link, and every member of your shop can see them. The share page makes a random number for the browser tab and sends it when a file is downloaded; the cloud keeps it with the link so that a limit on devices can be counted. It is not linked to who the visitor is.
Links locked to email addresses. If you lock a link to certain email addresses, Khayt Cloud stores those addresses in readable form, because it sends each one a code through our email provider. A code is stored only in scrambled (hashed) form, works once, and expires after 10 minutes or five wrong tries. Once someone proves their address, that address is recorded on the link’s download records, and their browser gets a cookie for 24 hours that only that link’s pages receive; the cloud stores only a scrambled copy of it. Every member of your shop can see the addresses a link is locked to.
Reports about a link. Anyone who has a link can report it to Khayt. A report holds the reason, any details and contact email address the person chooses to give, and their country, but not their IP address. Khayt reviews reports, which may also reach it by email, and they are deleted with your shop. Khayt cannot open a reported file; what it can do is turn the link off, or all of a shop’s links (see the terms).
Files for sale. Files you choose to sell are stored so that Khayt Cloud can read them, because a buyer who pays at night must get the file while your Mac is asleep. Before you release a file for sale, the Mac lists exactly which files and versions Khayt Cloud will be able to read, and ask you to confirm. A version you have released stays readable by Khayt Cloud while it is stored and is either still on sale or reachable through a buyer’s link. Deleting the file ends both. Stopping a sale protects only later versions, and buyers who have already paid keep their access unless you revoke it. Your other vault files stay end to end.
Sales and buyers. The buyer pays at your own checkout (Stripe, Lemon Squeezy or Gumroad), and that provider’s server tells Khayt Cloud about the sale. For each sale Khayt Cloud keeps the provider, its order number and payment reference, the product, the buyer’s email address (stored readably), whether the sale is paid, refunded or revoked, when each of those happened, and any note you add. The rest of the provider’s message is neither stored nor logged, and a notice for a product your shop doesn’t have is ignored and only counted. Your shop’s members can see its buyers and their email addresses. These records are kept until your shop is deleted, and for them we act as your processor, as section 10 describes.
Each buyer gets a vault share link locked to their email address, sent to them by email through our email provider. So that a buyer can find their files again on the “My files” page, Khayt Cloud keeps each buyer link’s secret sealed under a key only the server holds, and deletes it when the link is revoked, or within an hour of the link expiring. Because it holds that key, Khayt Cloud can open buyer links itself; they reach only the released versions it can already read. A buyer link records opens and downloads like any email-locked link, so your shop’s members can see which buyer downloaded what, when, and from which country and kind of device. A full refund reported by the provider ends that buyer’s link automatically, and so does a Stripe dispute you lose; a partial refund or an open dispute leaves the link working. To sign in to “My files”, a buyer types an 8-character code sent to their address. The code is stored only as a hash, works once, and expires after 10 minutes or 5 tries, and no more than 5 codes are sent to one address in an hour. Signing in sets a cookie that lasts 30 days, can be read only by Khayt Cloud’s own pages over a secure connection, and is stored only as a hash; signing out deletes it. If a file a buyer’s link names is due to be deleted because your shop moved to a smaller plan, Khayt emails that buyer once, 30 days before, through our email provider, with your shop’s name, the date and a link to “My files”, as the terms (“Moving to a smaller plan”) describe. It records when that email was sent, and erases the record once the vault fits again, or when your shop is deleted.
Listing on makerrun.com. If you make a product to list on makerrun.com, what a listing shows is public by design: its title and description, the price as you write it, its licence, your checkout link and payment provider, and its preview pictures, from which camera and location data are removed. Which vault files belong to the product is not public. A product you remove leaves only a marker, so the listing can say it has gone. To connect your makerrun account, Khayt Cloud emails a code to your Khayt account’s own address (owners and managers only); the code is stored only in scrambled form and expires after 10 minutes or five wrong tries. The cloud keeps which makerrun account is connected and the shop name you typed for it, and makerrun receives only your shop’s ID and that name. All of this is deleted with your shop.
Backups of Khayt Cloud. So that the service can be restored after a failure, its database is copied regularly. Copies kept on the server that runs the database are kept for 14 days. Copies sent off that server, to Cloudflare’s R2 storage, are first encrypted with a key that is not kept on the server, and are kept for 31 days. Shops’ synced books and vault files are copied there as they are stored, already end-to-end encrypted by your apps; a book’s copy is removed once it is over 31 days old and no kept database copy refers to it. Model files sent through the quote form are copied as they were uploaded, readable like the originals, and each copy is removed 30 days after the original is deleted. So data deleted from Khayt Cloud leaves these backups within about a month, with two exceptions: our hosting provider also backs up the whole server every day and keeps those backups for as long as its own service sets; and a one-time copy of the database from 24 September 2026, made when the service moved servers, is kept for recovery until 1 December 2026, and then deleted.
Emails that fail. If an email Khayt Cloud sends cannot be delivered, it keeps the recipient’s address, the email provider and the reason for 30 days, so that we can find and fix the problem.
Paying for a plan, and billing records. Once paid plans start, after the beta, the owner pays on Tap Payments’ own page, so Khayt never sees or stores card details. Khayt Cloud sends Tap the owner’s email address, the word “Khayt” in place of a name, a reference for the checkout, the total in Saudi riyals, and the shop’s ID with the plan and period paid for; Tap handles the payment under its own privacy policy. For each payment Khayt Cloud keeps the account’s email address, the shop, the plan and period, the billing country the owner chose at checkout and the country their connection came from (a two-letter code from our network provider, never the address itself), the amount before VAT, any VAT and its rate, the total, Tap’s reference for the charge and its status, when the paid period ends, and when the reminders 7 days and 1 day before that end were sent; these are deleted with your shop. Each charge, and each refund (the terms explain when one is given), also goes into its billing ledger — the amount and currency, the payment provider and its reference, a receipt number, the amount before VAT, any VAT and its rate, and the billing country the owner chose at checkout, with no name — which is kept for at least six years, even after a shop is deleted.
Internet addresses. To stop abuse, such as repeated sign-in attempts or spam sent through a form, Khayt Cloud notes the internet (IP) address of each request to its public and sign-in routes: signing up, signing in, password resets and joining a team, the customer portal and order tracking, order requests, the storefront, instant quotes and the quote form, reviews, notifications, crash and usage reports, vault share links, buyers signing in to “My files”, sale notices from payment providers, paying for a plan and Tap’s payment notices, stopping the weekly summary, makerrun product listings, connecting a makerrun account, and wrong attempts at Khayt’s own operator routes. It keeps the address, which kind of request it was, and when; an IPv6 address is cut to its network part. These notes are deleted after an hour, and they are never stored with your book, your files or your customers’ records. Where a request carries an email address (signing in, asking for or completing a password reset, a customer portal sign-in code, connecting to a vault with an email address, and asking the quote form to email a quote), Khayt Cloud also counts attempts against a one-way hash of that address (never the address itself), at most 10 in 15 minutes, so no one can guess a password or flood an inbox from many places at once. Each of these notes holds only the hash, which kind of request it was, and when, and is deleted within about an hour. They are counted the same way whether or not the address has an account. The once-a-day install count (section 11) does not store your address either: it is mixed with a value that changes every day and is held only in memory.
Our network provider. khaytapp.com is hosted on GitHub Pages and, like Khayt Cloud, reaches you through Cloudflare, which carries every request. As part of that service, Cloudflare keeps a record of each request, including the IP address, country and browser details, for a limited period (up to about 30 days) under its own privacy policy. We can look at those records in Cloudflare’s dashboard, and we use them only to keep the service running and to stop abuse. GitHub, which hosts the site, also records each visitor’s IP address for security, under its own privacy statement; it does not say for how long, and we cannot see those records (GitHub’s note on Pages). The one-hour limit above is for Khayt Cloud’s own records. If the list of downloads cannot be loaded from khaytapp.com itself, your browser asks GitHub’s API (api.github.com) for it directly, and GitHub handles that request under its own privacy statement.
Who runs Khayt Cloud for us, and where. Khayt Cloud runs on a server we rent from Hostinger, in Germany, behind Cloudflare. The emails it sends go out through Resend, in the United States. Mail to support@khaytapp.com is handled by Titan. So the data Khayt Cloud holds is stored and processed outside Saudi Arabia. Each of these providers handles it for us under its own terms.
6. The iPhone app
Khayt for iPhone is an optional app that pairs with your own Mac or PC. Everything below applies only if you install it.
What it keeps on the phone. A working copy of your shop — open orders, the newest finished ones, clients, inventory, machines, the waiting list, and the product catalogue (each product's names and descriptions, its prices with their costs and margins, the parts it is made from, and small pictures) — and a copy of your print library's list of models, so the phone can price one away from the shop, with pictures from the library, fetched from your Mac or PC over the shop's Wi-Fi (at most 80 MB, oldest dropped first). All of it is stored in the app's own container. iOS encrypts it at rest, and it cannot be read until you have unlocked the phone at least once since it was last started. Your pairing credentials — the owner LAN PIN, the Khayt Cloud sign-in token and the shop's encryption key — are held in the iOS Keychain, marked this device only, so they are never copied into iCloud Keychain and never restored onto a different phone.
Removing it. Unpair this device in Settings deletes all of it at once: the PIN, the cached shop data, the book and the rollback copy that holds the same records one write behind, the library copy and its pictures, and the cloud sign-in together with the shop's key. If your Mac or PC signs the phone out instead, the phone deletes its pairing key and PIN at once but keeps the shop data until you unpair it, so that a forged sign-out on the network cannot delete edits it has not sent yet.
Where it goes. Your shop's data goes to two places, and nowhere else on its own:
- Your own Mac or PC, over your local Wi-Fi. The app finds it with Bonjour and talks to it directly; nothing in that path leaves your building.
- Khayt Cloud, only if you switched sync on. The data is sealed with your shop's key (AES-256-GCM) on the phone before it is sent, so the cloud stores ciphertext it cannot read.
Two things you can switch on go to Khayt Cloud readable instead, because the person or device receiving them holds no key: photos you add to an order's tracking page, and Live Activities. Both are described below.
The app contains no analytics and no advertising SDKs. The one thing it sends on its own that is not your shop's data is the anonymous install count described in section 11, which you can turn off.
Notifications are optional — you can decline them when asked, or turn them off later in iOS Settings. If you allow them, the phone registers an Apple push token with Khayt Cloud; what is sent is that token, the app's bundle identifier and whether it is a test or release build. Nothing about your shop's contents goes with it.
What Apple delivers says only "A print finished". The details — which job, which printer, which client — travel sealed under your shop's key, and the phone opens them itself, so neither Apple nor Khayt Cloud can read them. Where the sealed details are too large to fit in a push, the alert carries only a timestamp and the phone fetches the sealed copy from the cloud, which is the same ciphertext by another route. What is not concealed is that an alert happened: the push carries your shop's identifier and the time, so Apple and the cloud can see that a print ended at your shop without seeing anything about it.
New order request alerts carry no customer details at all. The cloud raises those itself and holds no key to seal anything with.
Live Activities (optional) are the deliberate exception to the sealing above. To keep a print current on your Lock Screen and in the Dynamic Island while the app is closed, your Mac sends the printer's name, the job's name, the print's phase (printing, paused, finished, failed or cancelled), its progress, and its start and estimated end times through Khayt Cloud to Apple. These are not encrypted: iOS draws them itself, with no Khayt code running to open a sealed copy, so Khayt Cloud and Apple can read them. They are sent only for a phone that has registered for that printer's Live Activity — one showing it, or one that lets Live Activities start remotely. The cloud keeps a Live Activity's push token for at most 12 hours (a token for starting one, until the phone replaces it), does not store the print details it relays, and remembers only each printer's last phase and when it last sent, in memory, so it can space out updates. You can turn Live Activities off for Khayt in iOS Settings.
Camera (optional). Used to read printed spool labels and product barcodes. The text recognition runs on the phone, using Apple's own framework, and the pictures are not uploaded. There are three exceptions: a receipt photo you choose to attach to an expense, which travels to your own shop with that expense; a photo of a finished print you add to a job, which the phone sends only to your paired Mac or PC over your local network (the computer keeps it with that job, and a small preview of it is kept in the job's record, so it goes wherever the rest of that job goes if you turn on sync or backup); and photos you add to an order's tracking page, below. The app has no access to your photo library. When you choose a picture to send a customer, iOS's own photo picker hands the app that one picture and nothing else.
Photos for a customer (optional). When you send a customer a WhatsApp update with a picture of the finished part — taken with the camera or chosen from your photos — the picture goes only into the iOS share sheet, and from there to whichever app you send it with. Khayt does not upload it or keep it.
Photos on an order's tracking page (optional). You can also add photos of an order — the finished part, say — to that order's tracking page. These are uploaded to Khayt Cloud unencrypted, because your customer has to see them, and anyone with the order's tracking link can view them. Location and other metadata are removed on upload: EXIF (including GPS), XMP, IPTC and comments; the colour profile is kept. An order can have at most six photos, each at most 2 MB. They are deleted when you delete them, when you unpublish the order, or when the shop is deleted.
Printer camera (optional). While a printer's camera page is open, the phone fetches a still frame directly from that printer over the shop's Wi-Fi, every three seconds. The frames are not stored and are not sent anywhere.
Barcode lookup — one third party. When you scan a product barcode that is not already on your shelf, the app asks UPCitemdb, a public product database, what the product is, and reads the retail title it sends back. It sends the digits of the barcode and nothing else: no shop, no device, no account, no key. As with any request to any website, their server can see that it came from your internet connection. A barcode you have bought before is answered from your own inventory and nothing is sent anywhere.
NFC (optional). Reads and writes filament spool tags. Nothing leaves the phone.
Contacting a customer. The call, WhatsApp and email buttons hand that customer's number or address to the app you chose to open, exactly as tapping a number anywhere else on the phone would. Khayt does not transmit it anywhere itself.
The sample shop is invented data for trying the app before you pair it. It exists only on the phone and is never sent anywhere.
7. Optional third-party integrations
Khayt supports integrations you configure and control. When enabled, these may transmit data to the service concerned:
- Email notifications — using the SMTP or API credentials you provide
- Telegram notifications — using the bot token and chat ID you provide
- Printer messages to your phone through Telegram or ntfy (Mac app) — when a printer faults, stops answering or runs out of filament, and, only if you switch it on for that channel, when a print finishes, fails or pauses. A message names the printer and what happened; it includes the job and file names only if you tick “Include job and file names” for that channel, because a job or file is often named after a customer. ntfy messages go to the ntfy server you name, or ntfy.sh if you leave it blank. Anyone who knows an ntfy.sh topic’s name can read it, so use a hard-to-guess one; the “Make one” button picks one. An access token, if you add one, is stored encrypted and sent only over https. The topic and the token stay on that Mac and are never sent to Khayt Cloud
- E-invoicing — submitting invoices to your country's authority where the law requires it
- BNPL payment links — using the Tabby, Tamara or Stripe credentials you provide
- WhatsApp and SMS messages — using the WhatsApp Business (Meta), Twilio or Unifonic account you provide, or a webhook address you set, which receives the customer’s phone number, the message and the channel. A WhatsApp message goes from your app to Meta, which processes it for you under its WhatsApp Business data processing terms and privacy policy; delivery reports come back through Khayt Cloud, as section 5 describes
- Salla / Zid webhooks — receiving inbound orders from platforms you configure
- Accounting sync — when an order is paid, sending its invoice to an https webhook address you set, for example a bridge to your accounting software: the invoice number and date, the customer’s name, the currency, the amount before VAT, the VAT and its rate, and the total
- LAN server — a local web server on your own network for the customer portal, the intake form and an API (below)
- AI features — using the API key you provide for Anthropic, OpenAI, Google or a compatible service you name
- Your own storage bucket — an S3-compatible bucket you set up with Backblaze B2, Wasabi, Cloudflare R2, Google Cloud Storage, Storj or another provider, using the keys you provide. Library files you keep there are uploaded as they are, not encrypted by Khayt, and are held under that provider’s terms. Offsite backups of your book go there sealed with your Khayt Cloud key, as they do to Google Drive (section 4). The files go from your app straight to the provider, not through Khayt’s servers
- MakerRun (Mac) — opening the MakerRun tab in Maker Tools browses makerrun.com’s public catalogue, which needs no account and sends only what you search for. Downloading a design into your library, and, when you press Publish on a model, uploading that model, an optional picture and the listing details you enter (title, description, category, material and licence), happen only once you link a MakerRun account, and under that account. MakerRun reviews a listing before it is shown
- Filament profiles (Mac) — opening that tab in Maker Tools downloads the public list of filament profiles from bedready.io, and each profile you choose; nothing about your shop is sent
None are enabled by default. Khayt does not share your credentials with any party other than the service you explicitly configured.
Live exchange rates — one third party. Only when you press “Fetch live rates” under Exchange rates in Settings (on the Mac, Settings ▸ Invoice & Tax), the app asks ExchangeRate-API’s free open service (open.er-api.com) for today’s rates. It sends only your shop’s three-letter base currency (for example SAR): no key, no account, and nothing about your shop, orders or customers. As with any request to any website, their server can see that it came from your internet connection. Nothing is fetched in the background or on a timer. The rates that come back are kept in your book and used to convert amounts in other currencies into your base currency.
The LAN server and API tokens (off unless you turn it on). The Mac and desktop apps can run a small web server so that phones and tools on your own network can reach your shop: the customer portal, the intake form and, with a token, an API. It listens on port 3219 unless you change it, and answers only this computer until you also turn on “Listen on all network interfaces”. It is plain HTTP on your own network, not a cloud service, and it sends nothing anywhere itself: it only answers requests made to it. An API token opens only the parts you choose when you make it — orders, customers and inventory (read, or read and write) and machines (read only) — so a token that can read orders or customers can read your customers’ names and contact details. A token is shown once, when it is made; the app keeps only a one-way hash (SHA-256) of it, with its name, what it may open, and when it was made and last used, in your book, which syncs end-to-end encrypted like the rest of the book, and exports leave the hash out. Only the shop’s owner can make or revoke a token, and a revoked token is refused on its next request. No answer from the server includes printer keys, access codes or tokens. On Windows and Linux you can also switch on a remote tunnel, which makes the server reachable from the internet through localtunnel (loca.lt), a public relay service: while it is on, every request to the server and every answer passes through that service, so set a strong PIN. There is no tunnel on the Mac.
AI features with your own key (optional). The Mac and desktop apps can use an AI provider you choose — Anthropic, OpenAI, Google, or a compatible service at an address you give — with an API key from your own account with that provider. The request goes from the app straight to that provider; Khayt's servers are not involved and never see it, and the provider's own terms and privacy policy apply to it. Nothing is sent until you add a key, turn AI on, and turn on the feature itself — each has its own switch, and the app lists beside it exactly what it sends:
- Quote from a description — the description you type, your material names, and a reference photo if you attach one.
- Price suggestion — project names, prices and margins from up to 6 past jobs, plus the new job's material, weight, hours and cost.
- Customer message drafting — the customer's name, the order reference, project, status and due date, the amount and outstanding balance, and any note you type for it. This is the one feature that sends a customer's personal data, so it stays off until you turn it on yourself, even if you had AI on before it existed.
- Shop assistant — your question, with the conversation so far, your shop's name, and a summary of the shop: order and client counts (not names), revenue, outstanding and overdue totals, overdue project names, top materials and low stock.
- Sort linked folders (Mac only, off unless you turn it on) — the names of the folders inside folders you linked to your library, how many models each holds, its sub-folder names and up to 5 file names from it. It also sends the names of the files (models and pictures) lying loose at the top of a linked folder, in the order they were added to it — each name at most 120 characters, up to 300 a request and 3,000 a scan. Not their dates. Never a file's contents or anything about a customer, nothing from above the folder you linked, and never a picture unless you turn on Check pictures. Answers are kept in your book, so folders and names that were answered are not sent again; a request that failed is tried again at most once a day, and after 3 failures not again until those folders change; pressing Sort linked folders… always tries again.
- Check pictures (Mac only, off unless you turn it on, and separate from Sort linked folders: it works whether or not that is on) — to check that a picture found in a linked folder shows the right print: that picture (never one over 8 MB), redrawn as a new picture of at most 512 pixels on its long side, which keeps none of the original file's hidden details such as location and camera; the print's own preview when there is one (the picture inside a 3MF file already on your Mac, or the one the app drew of a model on your Mac — a model kept only in the cloud is never downloaded for this); and the print's name. At most 2 pictures a request and 40 checks a scan, never a model file. If your AI service cannot take pictures, nothing is sent. Nothing about a customer, and nothing from outside the folder you linked. Results are kept in your book, so a picture and print that were judged are not sent again; a check that failed is tried again on the same terms.
Folders you link from Google Drive, Dropbox, OneDrive or iCloud Drive are read on your Mac through that service's own app, not through Khayt's Google Drive connection. To show a picture for a print, the Mac asks that app to download a few small pictures from the folder (up to 8 MB each, 40 a scan); they stay in your drive, and models are never downloaded this way. A picture kept only online is downloaded only when you press Show on it, under the same 8 MB cap, and is not sent anywhere. Matching loose files into prints by their names happens on your Mac, whether or not AI is on, and sends nothing.
AI assistants on your Mac (khayt-mcp) (optional). The Mac app includes a small local server that an AI assistant you set up yourself — Claude Desktop, Cursor and others — can ask questions. It runs on your own Mac, reads your book there and never writes to it, and Khayt itself sends nothing anywhere for it. It can answer questions about your model library, and read-only questions about your books: open orders with their status, due date and amount; who owes what, and how late; stock running low; profit and loss for a month or a quarter; and the price of a quote. Whatever it answers goes to the assistant you connected — if that assistant is a cloud service, the answers leave your Mac and that service's own privacy terms apply.
Customers are not named unless you choose: the assistant sees "Customer 1", "Customer 2" and so on — the same label for the same customer in every answer — and a customer's full name is also replaced wherever it appears in project, stock and model titles, folders and tags. Titles are text you typed, though, so a first name on its own in one (say, "Nouf's lamp") can still reach the assistant. The switch Share customer names with AI assistants, at the bottom of Settings ▸ AI assist, is off unless you turn it on; it is kept with your shop's data, so it applies on every Mac that opens the same book, from the next question on. Phone numbers, email addresses and postal addresses are never shared, whatever that switch says, and neither are PIN hashes, passwords, sealed keys or cloud sign-in tokens.
8. Automatic updates
Khayt checks for updates via GitHub Releases. That is a standard HTTPS request to GitHub's servers, to which GitHub's privacy statement applies. The native Mac app checks a feed on this site instead, khaytapp.com/mac/appcast.xml, using the Sparkle updater, and downloads the update itself from GitHub. No personal data is transmitted in an update check, and updates install only when you choose.
9. API keys and secrets
Keys, tokens and secrets you enter are encrypted at rest using your operating system's secure storage — macOS Keychain, Windows Credential Store, Linux Secret Service. They are never transmitted to Khayt's servers, with two exceptions you choose. First, if you set up WhatsApp delivery reports, the Mac sends your Meta app's secret to Khayt Cloud, which uses it only to check that each report is signed by Meta. The cloud stores that secret as you entered it, not encrypted, and never shows it back. Your WhatsApp access token, which sends the messages, stays on your Mac.
Second, for each payment provider you connect to Khayt Vault, Khayt Cloud stores that provider’s webhook secret as you entered it, not encrypted, and uses it only to check that each sale notice really came from that provider. These secrets are never shown again after setup. Gumroad does not sign its notices, so for Gumroad the secret is part of the web address Gumroad calls instead. That address therefore also appears in our network provider’s request records (section 5), which only Khayt can see; Khayt Cloud shows you that address once, when you set it up.
10. Your customers' data
Khayt stores the customer details you enter, or that customers submit through your intake form or quote form: names, phone, email, addresses, order history and communication notes.
Under Saudi Arabia's Personal Data Protection Law (PDPL), and equivalents such as the GDPR, you are the data controller for that information. Khayt is a tool you run on your own machine. With cloud sync on, your book is end-to-end encrypted before it leaves your device, so we hold ciphertext, not customer records. The exception is what you publish through a customer-facing service — an order's details, a customer's email address, their messages, a request and model file sent through your quote form, and, if you turn on customer records, a copy of your customers and their orders — which the cloud stores readably on your behalf, as section 5 describes. For that data we act as your processor: we store it only to run the service you switched on, and unpublishing it deletes it. The customer portal is different in one respect: a customer signed in there sees the orders every Khayt shop has shared with their email address, side by side. That view across shops is Khayt’s own service to the customer, not one that a single shop runs, and a shop’s owner or manager can take the shop’s orders out of it.
To help you meet your obligations, Khayt provides:
- Consent at collection — your public intake form requires customers to agree to a plain-language notice before submitting, and records that consent with a timestamp and the exact wording shown.
- Access and portability — "Export this customer's data" produces a machine-readable file of everything Khayt holds about one customer.
- Rectification — every customer field is editable.
- Erasure — deleting a customer offers a choice: unlink, keeping order records you may be required to retain, or full erase, which also removes the name from those orders and purges intake submissions and communication logs. Orders that carry an invoice or a payment keep the customer's name even then, because tax invoices must be kept as issued. So does a gift card with a balance left, because that balance is money the shop still owes them; a used-up gift card loses the name, and their loyalty points are unlinked from them. A full erase also takes the customer's order tracking pages down from Khayt Cloud, those of invoiced and paid orders included; if Khayt Cloud cannot be reached at that moment, the app keeps trying until it can.
- Storage limitation — an optional retention setting anonymises contact details on old intake submissions while keeping the operational record.
These are engineering tools, not legal advice. How long you keep records, and on what lawful basis, is your decision as controller — please take qualified advice.
11. Crash reports and usage data
Apart from the anonymous install count below, Khayt sends nothing by default. You may turn on two separate, independently revocable options in Settings:
- Crash reports — the error type, a scrubbed message and stack trace, your app version, your operating system and its major version, the app's interface language, its release channel (stable, beta or alpha) and the day. File paths are reduced to a filename, and emails, phone numbers, IBANs and long digit sequences are removed before anything is stored. On Windows and Linux, a crash report is also sent to Sentry (Functional Software, Inc.), our error-monitoring service, and stored in the EU. It holds the error, its stack trace and basic device and system details, and Sentry keeps it for as long as its own retention sets. From desktop version 4.8.0, the same removal of emails, phone numbers, IBANs, long digit sequences, secrets and file paths also runs on the report before it is sent to Sentry, including the steps logged before the crash and any request details; reports from earlier versions were sent to Sentry without it.
- Anonymous usage counts — which features were used, as counts, with your app version, interface language, release channel and the day, and how the shop is set up in fixed categories: its mode, its business type, and whether VAT, ZATCA invoicing, the online services and the LAN server are switched on. Never what was in them.
On the Mac, and in the desktop app from version 3.11.22, the app asks once, with a card across the top of its window that never blocks it: share crash reports, optionally with usage counts too, or "Not now". Whichever you choose, it does not ask again on that computer, and the two switches in Settings stay the permanent control. "Not now" turns nothing on. Your answer is saved with your shop's data, so once you turn reports on in one app, the other app on the same data follows it and does not ask. The Mac's crash reports are errors the app caught in its shared rules engine, the note it leaves when it quits unexpectedly, and the report macOS gives the app about its own crash — the exception and signal, the build that crashed, and the crashing thread's frames as code offsets in the libraries the app was running (a library name and a number, never a path) — all scrubbed by the same rule as the desktop app's; its usage counts are the app being opened and how often each of a fixed list of features is used (for example a quote created, an invoice exported, a model imported), as counts only.
The anonymous install count — on unless you turn it off. So that we know roughly how many copies of Khayt are in use, each app sends Khayt Cloud one small message at most once a day, without asking first. It holds exactly six things: the platform (Mac, Windows, Linux or iPhone), the release channel (stable, beta or alpha), the app version, and three yes-or-no answers — whether this is the install's first count this week, this month, and ever. It carries no install identifier, shop, account or device name, so one install cannot be told from another, and Khayt Cloud does not store the address it came from. Like any web request, it passes through our network providers (Cloudflare and our hosting provider), which handle it under their own terms. The cloud does not keep the message itself: it adds one to a few daily totals per platform, channel and version, keeps those totals for 400 days, and only Khayt reads them. The count is not linked to you and is never used for tracking or advertising. To stop it, turn off Count this install (anonymous) in Settings; nothing is sent while it is off.
We never collect your orders, customers, prices, margins, inventory, files, or any secret. There is no account and no user id — only a random install identifier created when you opt in. Opting out removes it from your shop's data straight away; backups made before then still hold it until they are replaced, and reports already sent keep it until Khayt Cloud deletes them. Khayt Cloud deletes every crash report and usage count about 180 days after the day it was sent. Turning an option off deletes anything queued locally straight away. You can inspect exactly what would be sent at any time via "View what's collected".
12. Children's privacy
Khayt is a business tool intended for adults. It is not directed at children under 13 and we do not knowingly collect information from children.
13. Changes to this policy
We may update this policy from time to time. Updates are published at this URL, with the date at the top of the page. We encourage you to review it periodically.
14. Contact
Questions about this policy: support@khaytapp.com.
Khayt is source-available software licensed under the Functional Source License (FSL-1.1-Apache-2.0). The source is at github.com/KhaytApp/Khayt, which means every claim on this page can be checked against the code rather than taken on trust.