KEB OS is made by KEB Tech, Inc., called “KEB Tech,” “we,” or “us” here. This policy covers the KEB OS desktop app, the KEB OS mobile app, KEB OS cloud computers, and keb-os.com. We don’t sell your personal information, and we don’t use it for advertising.
What we collect
Your account
Your email address, your name, an optional handle and profile picture, and what we need to sign you in securely: a hashed password if you set one, passkeys, one-time sign-in codes, and session records.
What you create
Cards and folders, Spaces you create or join with their channels, messages, reactions, and the files and photos you choose to attach, bookmarks, saved prompts, KEB Agent memories, automations, KEB Apps, the items you add from the KEB Store (a record of which items you added, when, and whether you’ve changed them), and passwords you save in Vault. Vault passwords are encrypted before they are stored. It also includes videos you record with KEB OS, as explained under “Call recordings” and “Screen recordings.”
Devices and usage
Your device type, operating system, and app version; push notification tokens so we can deliver notifications; IP addresses and user agents for security and rate limiting; and events about which features you use, so we can understand what works and fix what doesn’t. The app also tells us how it’s running, like when it started, how it last closed, whether it keeps crashing, and how many chats are open or were recently closed, as basic facts and counts, never chat titles or content. If KEB OS crashes, the app reads the crash report your computer made and sends us a short technical summary so we can fix the problem: when it happened, which part of KEB OS crashed and its version, the type of error, and the names of the code modules and functions involved, but never your files, chats, file paths, or what was in memory. The mobile app also reports its crashes, freezes and startup failures to us, even before you sign in and without your account attached. From each report we keep only the type of problem, when it happened and when it reached us, the app version, the phone model and system version, a short description of the error, and the names of the code involved. We drop anything else a report contains, such as memory contents near the crash, as soon as it arrives. We keep phone crash reports for 90 days, except that our team gets an email about each new kind of crash with some of these details, and those emails may be kept longer. Our website also uses Vercel Analytics to count page visits. We don’t use third-party advertising trackers.
How people find KEB OS
When you arrive at keb-os.com from a link with campaign tags (such as utm_source) or from another website, keb-os.com saves two cookies in your browser for 180 days: one for your first such visit and one for your most recent. They hold only those tags, the other website’s domain and the date. If you download KEB OS or create an account on keb-os.com, we copy them onto the download and onto your account, so we can see which channels bring people who go on to use KEB OS.
The KEB OS app can’t read your browser’s cookies. So after you download, the download page offers an “Open KEB OS” link. It carries a one-time code that connects your new app to those tags, and to an affiliate link you clicked in that browser, if there was one. The code is random, we store it only in scrambled (hashed) form, it works once, and it expires after 30 days, when we delete it. Using the link is optional. If you don’t, your account just isn’t connected to how you found us.
The first time KEB OS opens on a computer, the app sends us a one-time notice with only the platform (Mac or Windows), the app version, and the one-time code if you used the link. It contains no device identifier, and we use it only to count how many new installs get opened.
These cookies are first-party, and no third-party scripts read them. We don’t use fingerprinting, and we don’t connect your browser to your app by IP address or timing: the one-time link is the only connection. If your browser sends a Global Privacy Control signal, keb-os.com doesn’t save these cookies or create a one-time code. We delete the copy on a download after 180 days. The copy on your account is deleted when you delete your account.
Microphone, speech, and photos
The mobile app asks before it uses your microphone. Dictation turns your speech into text with Apple’s speech recognition. During a voice call with KEB Agent, your audio streams to your own computer over an encrypted connection, sometimes through a relay; we don’t record or store call audio. Photos are only read when you pick them to attach.
KEB Calls
When you start or join a KEB Call, including as a guest without an account, we keep a record of the call: who hosted it, its title, when it ran, and the name each person joined with. To keep calls working and fix problems like dropped sound or a blurry or choppy shared screen, the app or browser on each device in the call also reports how the call is going: connection quality (like packet loss, jitter, and delay, and whether the call connects directly or through a relay), whether the device is on Wi-Fi, cellular, or a wired connection, the kind of app, browser, and operating system, the type of microphone (Bluetooth, built-in, or USB, never its name), and when a microphone is muted, unmuted, or changed. They also say whether the call is on screen or in the background, whether the device is online or sharing its screen, and whether the microphone is allowed and how many microphones the device has. While a device shares its screen, they also include technical readings about the share: its size and the size of the screen or window being shared, its frame rate and data rate, the bandwidth available, how the computer encodes it (in hardware or software, and in which video format), whether the computer or the connection held it back, and how much of the time someone else was controlling it. They also include readings about the camera and video, like frame rate and resolution, how many audio and video tracks the connection carries, how long joining the call took, and how long the device’s requests to keb-os.com take. When a phone pauses someone’s microphone, for example during a phone call or while the app is in the background, the reports also say how many times that happened in the call and when, what brought the microphone back each time (like the interruption ending or the app reopening), and how long the sound took to come back, but never who called. On Android, while a call is open in the KEB OS phone app, the reports also include what the phone says about its sound whenever that changes: its audio mode, such as whether a phone call is ringing or in progress (never who), which kind of device the call’s sound goes through and which kinds connect or disconnect (like Bluetooth or headphones, never their names), and up to four recordings active on the phone at that moment, including ones by other apps. For each recording, they say only its kind (like a voice call or voice recognition), which kind of device it records from, and whether Android has silenced it, never which app it belongs to or anything it hears. These reports don’t include IP addresses, device names, or anything said or shown in the call. We delete the detailed reports after 30 days and each call’s quality summary after 180 days. We keep the call record as long as the host’s account exists, but 180 days after a call ends, we replace the name each person joined with by their role (Host, Member or Guest). Names in call transcripts and in their agreement records are kept as explained under “Call transcripts.” A call’s host can have a call transcribed, or recorded on video and transcribed, as explained below. Otherwise we don’t keep call audio or video. Chat messages in a call aren’t saved, except that messages sent while a call is being transcribed or recorded go into its transcript. Otherwise our real-time provider holds them for a couple of minutes so someone who joins late can see them.
Call transcripts
A call’s host can have a call transcribed, or recorded on video and transcribed. Before anything is captured, everyone in the call is told and asked to agree, and anyone who doesn’t agree leaves the call while it’s transcribed or recorded. A “Transcribing” or “Recording” sign shows in the call the whole time, and a short announcement plays when transcription or recording starts or resumes.
We save a written transcript of what each person said and wrote in the call’s chat while it was on (labeled with the name they joined with), a short record of the call (when it ran and who took part), and a record of who agreed and when. We don’t keep the call’s audio or video unless the host records it, as explained under “Call recordings,” and we don’t identify people by their voice. For a personal call, these go to the Cards of the person who turned on transcription, and only they can open them. For a call in a Space, they go to that Space’s Cards, where only members with access to that channel can open them. Either way, they can share them with others.
Transcription runs on Cloudflare. While a call is being transcribed, each person’s audio goes to Cloudflare Workers AI, which turns speech into text for us under Cloudflare’s data processing terms, and Cloudflare doesn’t use it to train AI models. We keep the text, not the audio sent for transcription. We use transcripts only to provide this feature. We don’t use them to train AI models or for our own analytics, and we don’t read them except to give support that’s asked for, to keep KEB OS secure, or when the law requires it. When someone asks KEB Agent about a call, the transcript goes to the AI provider they use with KEB Agent, as described under “AI features and AI providers.”
A deleted transcript stays in Trash for 30 days. Then it’s permanently deleted, and copies in our encrypted backups are deleted automatically within 90 days after that. It can also be deleted right away. Anything deleted stays deleted, even if we ever have to restore from a backup. Deleting your account deletes the transcripts in your personal Cards too. Transcripts in a Space belong to that Space: they stay until the Space’s owner or admins delete them, or until the Space itself is deleted, in which case they’re permanently deleted 30 days later, unless the Space is restored first. Deleting a transcript doesn’t delete copies made from it elsewhere, like notes, other Cards, KEB Agent chats and memories, or Cards shared in a Space; whoever made those copies can delete them. We keep a short record of who agreed to each transcript (each person’s name, their choice, and the time, but not what was said or any IP address) for 3 years, even after the transcript is deleted, so we can show that everyone agreed.
If you were on a transcribed call and want your part removed, ask the person who turned on transcription (for a call in a Space, the Space’s owner), or email us with the call’s link or date and the name you joined with. We’ll remove your name and your words from the transcript and call record we saved, and we’ll tell the person who turned on transcription, so they can also delete any copies they made elsewhere. We delete the whole transcript if you never agreed to be transcribed, or if the law requires it. We answer within 30 days. If the call was recorded, we can’t edit one person out of the video, so we’ll tell the person who recorded it about your request. We delete the video too if you never agreed to be recorded, or if the law requires it.
Call recordings
In the KEB OS desktop app, a call’s host can also record the call on video. Everyone is asked to agree first, as described above, and the call is transcribed too.
The video is made on the host’s own computer, by KEB OS. It shows the call as the host sees it in KEB OS, like people’s video, names, chat, and drawings, and whenever someone shares their screen, it shows that screen. Its sound is everyone in the call as the host hears them, including shared-screen sound, and the host’s own microphone as the call sends it. It never captures anything else on the host’s screen. Until it’s uploaded, the video is kept in KEB OS’s private folder on that computer. KEB OS uploads it once the recording ends and deletes it from the computer once it’s saved. The video ends when the host leaves the call, and the transcript continues.
The video is saved to the same place as the transcript: the host’s Cards for a personal call, or the Space’s Cards for a call in a Space, where only members with access to that channel can open it. It’s stored with our file storage provider, Cloudflare, and counts toward that account’s storage. We don’t use recordings to train AI models or for our own analytics, and we don’t watch them except to give support that’s asked for, to keep KEB OS secure (like reviewing a reported video), or when the law requires it.
A deleted recording stays in Trash for 30 days and is then permanently deleted. It can also be deleted right away. When it’s permanently deleted, its video file is deleted from our storage, which keeps no backup copies of videos, and records about it in our encrypted backups are deleted within 90 days. Deleting your account deletes the recordings in your personal Cards too. Recordings in a Space follow the same rules as its transcripts.
Screen recordings
In the KEB OS desktop app, you can record your screen or one window with KEB OS’s screen recorder, with your microphone and, if you turn them on, a camera bubble and, on Windows, your computer’s sound. It records only after you start it, and a control bar shows on screen the whole time; the control bar and the camera preview aren’t in the video. On a Mac, it needs your permission to record your screen. Like a call recording, the video is made and kept on your computer until it’s uploaded, then saved to your personal Cards, where it counts toward your storage. Only you can open it unless you share it. It’s deleted like any other Card, and deleting your account deletes it.
Share links
You can share a call recording or a screen recording with a link, and KEB Agent makes a call recording’s link when you ask. A link can be public, so anyone who has it can watch without signing in, or need a passcode, so only people who enter it can watch. A recording in a Space can also be shared only with people signed in who can open it in that Space. The page shows the video, its title, the name of the person who recorded it, and the date. It doesn’t show the transcript. A passcode page shows nothing about the video until the right passcode is entered. People signed in who can already open the recording in KEB OS (its owner, or for a call in a Space, people who can see it there) go straight to the video.
Whoever can manage the recording (its owner, or for a call in a Space, the Space’s owners and admins) can change a link or its passcode, or stop it, at any time, and a stopped link stops working right away. We store passcodes only in scrambled (hashed) form, so we can’t show one again, and we limit wrong tries. When someone enters the right passcode, their browser keeps a short-lived pass for that one link, which ends when the passcode changes or the link stops. Moving the recording to Trash pauses its links, and deleting it deletes them. We count how many times each link is opened, but we don’t keep a list of who watched. As on the rest of keb-os.com, IP addresses are used for security and rate limiting. Shared videos aren’t shown to search engines.
The mobile browser
Pages you visit and your browsing history stay on your phone. Bookmarks and saved logins sync with your KEB OS account so they match your desktop.
Payments
If you buy a paid plan, our payment processor, Stripe, collects your payment details directly. We never see or store your full card number. Stripe shares with us what we need to manage your subscription: your plan and its status, your billing name and country, your card’s brand and last four digits, and your invoice and payment history. If you buy a plan in the KEB OS iPhone app, Apple processes your payment, and we never see your payment details. Apple tells us what we need to manage your plan: which plan you bought, its price and currency, your App Store country, when it renews or ends, and whether it was canceled or refunded.
Affiliate program
When you click a KEB OS affiliate’s link, keb-os.com saves a cookie in your browser for 60 days that names that link, and we count the click. The click record says only which link was clicked and when. If you create a KEB OS account while the cookie is there, either on keb-os.com or in the KEB OS app opened with the “Open KEB OS” link from the download page in that same browser, we note which affiliate referred you, for as long as both accounts exist, so we can pay them a commission when you pay for a plan on our website. The affiliate sees how many clicks, signups and paying customers their link brought, and the plan, amount and date of each commission. We don’t show them your name or email, but someone who knows they referred you may be able to tell from that.
If you’re an affiliate, Stripe collects your identity, bank and tax information directly to pay you, and processes it under Stripe’s Privacy Policy. We get what we need to pay you: whether your payout account is ready, and your payouts.
Businesses that use KEB OS
When a business uses KEB Business, we store and process its customers’ information for that business: their contact details, the texts, emails and calls they exchange with the business, their bookings, their accounts and files on the business’s website, and whether they have an active subscription or membership with the business, matched by the email they sign in with. The business decides how that information is used, and its own privacy policy applies to it. We process it only on the business’s behalf. If you’re one of its customers, ask the business about your information, and we’ll help it answer. Texts go through Twilio, either on a number KEB gets for the business, held in a Twilio account we keep for it, or on the business’s own Twilio account, and calls go through the business’s own Twilio account. Twilio handles them under its own terms. Email goes through Amazon Web Services. If someone unsubscribes from a business’s emails, by the link or by replying STOP, we keep a record of that so the business’s emails skip them. For a business’s marketing emails, we keep the postal address the business gives us, which each one shows, and a record of each one sent, including when and how it was approved. Payments go to the business’s own Stripe or Whop account under that service’s terms, and we never see full card numbers. If we register a domain for a business, we give the domain’s registrar and registry the business’s contact details, as domain rules require. Privacy protection is on where the domain allows it, but some details can still appear in public domain records.
An agency on KEB Agency can show its client portal at a web address it owns, such as portal.youragency.com. If you sign in there, you’re signing in to KEB OS, not to the agency: we run the sign-in and the portal under this policy, your sign-in codes come from noreply@keb-os.com, and a sign-in there works only for that portal. We don’t give the agency your sign-in codes or your sessions, and using the portal on the agency’s domain doesn’t let the agency see anything it couldn’t see on keb-os.com. If the agency’s domain stops pointing to us, we stop showing the portal there.
If a business asks us to get it a texting number, we send the details its owner confirms (the business’s legal name, EIN, type, industry, address and website, the name, title, email and mobile number of its contact person, and a description of its texting with sample messages) to Twilio, which shares them with The Campaign Registry and U.S. mobile carriers to check and register the business. We don’t keep the EIN or the contact person’s details ourselves. We keep the texting description and samples, the registration’s status and Twilio’s reference numbers, and a monthly count of texts sent for billing, until the business’s Space is deleted. Twilio keeps the registration and the texts in the account we hold for the business, and deletes that account’s records 30 days after we close it, which we do after the number is released.
Connected accounts
If you connect your business’s Stripe account, new or one you already have, Stripe shares with us your Stripe account ID, business name, account status and capabilities, what Stripe still needs from you, and your payout status. When KEB OS creates a payment link, invoice, deposit or checkout for you, we send Stripe or Whop what’s needed to create it, such as your customer’s name and email, the items and the amount. We keep a record of each payment action KEB Agent takes for your business: what it was, the amount, when, and who asked for it or allowed it. When you ask KEB Agent about your payments, it reads your recent payments from Stripe or Whop at that moment (the amount, currency, status, date and description) to answer you, without keeping a copy of what it reads. When a payment arrives, Stripe or Whop tells us, and we keep a record of it (the amount, the currency and the customer it matches) so your automations can run. For members-only access, we keep a record of which of your website’s users has an active subscription or membership. If you connect your business’s Whop account through KEB’s Whop app, we keep no key or token for it, only its Whop business ID and the app’s install ID, and we use that connection only to check your members’ memberships, create the payment links and checkouts you ask for, read your payments, and keep the connection working. If you connect with a key you give us instead, we keep the key encrypted and use it only to check your members’ memberships and keep the connection working. We use what these accounts share only to show it in KEB OS and run what you set up. We also share information about your business’s account and payments with Stripe, Whop, card networks, banks and authorities when they ask for it or their rules or the law require it, or when we need to report a problem. Stripe and Whop handle payments under their own terms and privacy policies. When you disconnect, we stop using that account, end our access to a Stripe account you already had, and delete the subscription and membership records we kept from it, and any Whop key you gave us.
AI features and AI providers
KEB Agent is powered by AI models from third-party providers. Before the mobile app sends anything to KEB Agent, it asks for your permission.
KEB Agent runs in the KEB OS desktop app. You can connect an AI provider there, such as Anthropic (Claude), OpenAI (ChatGPT and Codex), Google (Gemini), xAI (Grok), or Cursor, and KEB Agent then works under your own account with that provider. When you message or call KEB Agent from your phone, your messages, voice, and the images you attach go to your computer. From there they go to the AI the chat uses, together with the context KEB Agent needs for the task, like relevant Cards or pages. When that AI is a provider you connected, the provider’s own terms and privacy policy apply to what it receives.
KEB’s model
KEB’s model lets KEB Agent run on an AI model we provide, without a separate AI account. For now, it’s only for accounts we’ve invited to try it. Everyone else uses KEB Agent with their own AI account, as described above. When a chat uses KEB’s model, your requests, and the files, screenshots, pages, Cards and tool results needed for your task, are processed by AI model providers that do not retain that data or use it to train their models. Web search sends your search query to a search service to find relevant information. Search services process queries under their own privacy terms.
We check your account and usage allowance. We record request size, token counts, cost, and whether the request worked to apply your allowance, prevent abuse and fix problems. We do not keep copies of your AI prompts or answers in these usage records, and we delete these records with your account.
If you report a KEB Agent reply in the app, we receive only the reply you chose, with anything you write in the report, and only when you send it. We use it to review that reply and make KEB Agent safer.
Cloud computers
If your plan includes a cloud computer (KEB Max, or an original KEB Pro or KEB Max plan), we run one for you: a private server with KEB OS on it, hosted by Google Cloud in the United States. Each cloud computer is its own server with its own disk. Nothing on it is shared with other customers, and its disk is encrypted at rest.
- What’s on it. Whatever you and KEB Agent do there: your chats and agent history, automations, files you create or download, the browser profile for websites you sign in to in KEB OS tabs (like cookies and saved sessions), and the sign-ins for the AI providers you connect there. Your AI sign-ins are stored on your cloud computer itself, not in our central databases, and our team never sees or enters them.
- AI on your cloud computer. When KEB Agent on your cloud computer uses an AI provider you connect there, like OpenAI or Anthropic, it connects directly to that provider under your own account, and that provider’s terms and privacy policy apply. We don’t route those prompts through our servers or keep copies of them. If a chat there uses KEB’s model instead, its requests are processed by the model providers as described under “KEB’s model” above. Features that sync with your KEB OS account, like Cards, Spaces, and the mobile app, work the same way they do on your own computer.
- Getting in. You open your cloud computer only inside the KEB OS apps, while signed in to your KEB OS account. Its screen, and your clicks and typing, travel over an encrypted connection, either directly or through our relay provider, Cloudflare. The relay can see IP addresses, but not what’s on your screen or what you type. Your cloud computer doesn’t accept incoming connections from the internet.
- When our team accesses it. Our team can technically sign in to a cloud computer, and those sign-ins are logged. We only do it to give you support you’ve asked for, with your permission; to keep KEB OS secure, like investigating abuse or a security problem; or when the law requires it. We don’t look through your files, chats, or accounts for any other reason.
- Running it. We keep operational records, like when your cloud computer was created, went to sleep, woke up, or was canceled, and which plan you’re on, for as long as your account exists. Security and access logs, including records of any staff sign-in, are kept for up to 400 days.
- When you cancel. We stop your cloud computer and keep a snapshot of its disk for 30 days, so you can come back and pick up where you left off. After 30 days, we delete it. If you delete your KEB OS account, we delete your cloud computer and its disk right away, with no snapshot. Before we update or repair your cloud computer, we may take a snapshot of its disk, so we can put it back if something goes wrong. We delete it within 14 days, or right away if you delete your account.
How we use information
- To provide KEB OS: sync your data across your devices, deliver Space messages and notifications, and run the features you use.
- To keep accounts and the service secure, prevent abuse, and review content that people report.
- To understand usage, fix bugs, and improve KEB OS.
- To email you about your account and, if you’re on our lists, product news you can unsubscribe from.
Who we share it with
People in your Spaces see your name, profile picture, and the messages and files you share there. Service providers process data on our behalf to run KEB OS: Amazon Web Services (databases and email), Vercel (hosting), Google Cloud (cloud computers), Cloudflare (file storage, call transcription, and connecting and relaying calls and cloud computer screens), Ably (real-time message delivery), Stripe (payments, affiliate payouts, and the Stripe accounts businesses connect), Twilio (texting numbers we get for businesses), Expo, Apple, and Google (push notifications and app updates), and the AI providers described above. We also share information when the law requires it, to protect people’s safety, or as part of a merger or acquisition, in which case this policy continues to apply.
Keeping and deleting your data
We keep your data while your account is open. When you delete a Card or a folder, it goes to Trash, where you can restore it for 30 days. Then it’s permanently deleted, with its files and earlier versions. You can also ask KEB Agent to delete a Card in Trash forever right away. Cards in a Space that has been in Trash for 30 days are permanently deleted too. When a message in a Space or a direct conversation is deleted, we delete its text, its attachments (including voice-note transcripts) and its reactions right away, keeping only a marker that tells everyone’s devices to remove it. If someone reported the message, we keep a copy with the report for moderation. Copies of anything permanently deleted are deleted from our encrypted backups automatically within 90 days, and anything deleted stays deleted, even if we ever have to restore from a backup. We keep something longer only if the law requires it. Deleting a Card or a message doesn’t delete copies made from it elsewhere, like other Cards, KEB Agent chats and memories, or notifications people already got.
You can delete your account at any time on our website at keb-os.com/account/delete, or in the mobile app under Settings → Delete account. Deleting your account permanently removes your profile, sign-in methods, personal Cards, memories, bookmarks, saved prompts, Vault, automations, KEB Apps, your KEB Store records, AI request records, usage events, KEB Calls you hosted and your place in calls you joined, call transcripts and recordings and screen recordings in your personal Cards, and their share links, and the messages, reactions, and files you posted in Spaces. Spaces you own that have no other members are deleted too, with their automations and the records of their runs. If you own a Space that other people still use, you’ll be asked to delete it first. Shared Cards you added to someone else’s Space stay with that Space, no longer linked to you. Automations you made or published in a Space other people use stay with that Space, with the records of their runs, no longer linked to you. Reports are kept as moderation records, including reports about content that broke our rules and the text of any KEB Agent reply you reported. If you delete your account, we keep the reports you sent, and the copies emailed to our moderators, for safety and moderation; those copies show who sent them. Agreement records from transcribed or recorded calls are kept for 3 years, as explained under “Call transcripts.” Copies in our encrypted backups expire on their normal backup schedule. If you have a paid plan bought on our website, deleting your account cancels it. Deleting your account also deletes your cloud computer right away, with no snapshot. A plan bought on the App Store keeps renewing until you cancel it in your Apple Account’s Subscriptions settings. We keep payment, invoice and affiliate payout records for as long as tax and accounting laws require.
When a business uses KEB OS to collect form submissions, each submission is saved as a row in the table the business chose. The submitted details are removed from our own record of the submission 30 days after it’s received, or once no automation it started is still running, if that’s later, and the rest of that record is deleted after 90 days. The row in the business’s table, and anything the business saves from it, like a contact, stays until the business deletes it or erases that customer. The events that start a business’s automations are deleted after 90 days. A record of each automation run, saying which steps ran and what happened, is kept with no set end date, even after the business’s Space is moved to Trash, and is deleted only if the Space’s last remaining member deletes their account. It refers to the customer’s Contacts row and to the rows and messages its steps touched, which lead nowhere once that customer is erased. It doesn’t hold the customer’s details themselves, except anything someone types in when starting a run by hand, or an unexpected technical error that quotes the value that caused it. A business can also erase a contact’s data on request.
Security
Data travels over encrypted connections and is stored with encryption at rest. Each cloud computer runs on its own server and disk and can’t be reached directly from the internet. Vault passwords are encrypted with a key per account. No system is perfectly secure, so please use a strong password and tell us right away if you think your account was compromised.
Your choices
- See and edit your profile in the app, and delete your Cards and your Space and direct messages at any time, as explained under “Keeping and deleting your data.”
- Turn notifications, microphone, camera, screen recording, speech recognition, and photo access on or off in your device settings.
- Stop sharing a recording’s link at any time.
- Withdraw permission for KEB Agent in the mobile app under Settings.
- Choose the AI each chat uses: a provider you connect, or KEB’s model if your account has it.
- Ask us for a copy of your data, a correction, or deletion by emailing us. We answer within 30 days.
Where your data is processed
KEB OS is run from the United States, and our main databases are there. Some providers, like Cloudflare, store or process data in data centers around the world, often the one nearest you. The AI model providers used for KEB’s model do not retain your requests or use them for training.
Children
KEB OS isn’t meant for children under 13, and we don’t knowingly collect their information. If you believe a child has given us information, contact us and we’ll delete it.
Changes
When we change this policy, we’ll update the date above, and for significant changes we’ll let you know in the app or by email.
Contact
Questions or requests: feedback@keb-os.com. See also our Terms of Use and Support page.