Privacy Policy
Effective: October 11, 2026
This policy explains how iyulab, inc. (the "Company") handles information on this website and in the Bohm desktop application ("Bohm"). It follows the personal information protection laws of the Republic of Korea.
1. The Bohm application
Bohm runs on your PC. The apps you add, their data, your settings and your visit history are stored in a folder on your PC. The Company does not operate a server that receives them.
While Bohm is being stabilized, it sends diagnostics to the Company: crash and error reports (the kind of error and where in Bohm's own code it happened), the exit code and restart outcome when its local runtime stops unexpectedly, and once a day a “started” note with Bohm's version, the number of apps you have added, the screen language and a random install ID. An error report is made only of set fields and carries no text: error messages, app names, what you type and file contents are never included (versions before 0.3.0 sent the error message with paths, addresses and email addresses removed; from 0.3.0 no message is sent). Offline, reports wait on your PC, the oldest are discarded first, and nothing stops working. You can see exactly what was sent under About Bohm › Diagnostics in its settings; your IT team can turn diagnostics off.
Bohm also sends the usage record — which days each app was opened and used, with no app names, paths or data — once a week, but only if you turn on Also send the usage record in its settings.
Otherwise Bohm sends something to the Company only when you use Tell us in its settings — to report a problem or to ask for news — and press Send. It shows you exactly what will be sent before you do. Your IT team can turn this off.
To keep itself up to date, Bohm asks GitHub's public release page (github.com) for the number of the newest version once a day (and, from version 0.10.14, each time it starts) and — from version 0.10.8 — when there is a newer one, downloads that version's installer from GitHub. These requests carry nothing about you or your apps — only Bohm's version as its name — and, like any web request, reach GitHub from your network address. The installer is kept in Bohm's data folder until it is installed, then deleted. Your IT team can turn this off.
If you connect a key for an AI service, requests your apps make to that service are sent to it with your key, under that service's own terms. An app's request to a service with no key connected is answered by your local AI server, if you set one, or otherwise by the model on your PC — with the model on your PC, it stays on your PC. A request from an app to turn a recording into text (from 0.10.11) goes the same way, and the recording goes with it; from 0.10.12, when neither a key nor your local AI server answers it, the speech-to-text model on your PC does if you have got it, and then the recording stays on your PC.
When you ask Bohm about the web pages you have open, ask it to make or change an app, or save an answer as an app, Bohm hands what that needs — the text of the pages, your description of the app to make, the app's code (with Ask to fix the problem, also the changed or newly made version and the error messages it gave when opened or tried — a changed version is opened with a copy of your data, so its messages can quote a little of that data; a newly made one is opened with none, though its messages can quote what you typed while trying it; and a picture of a newly made app's first screen, opened with no data, so the AI that made it looks it over once), or your question, the answer and the tables read from the pages — to the AI you chose for it: a model on your PC, a local AI server (for example, one your organization runs), or an AI service you connected with your key. None of it goes through the Company. Pages at addresses inside your network, and sites you or your IT team list, are not handed to AI services. If you send such a page to one of your apps while an AI service is connected, Bohm tells you first, since the app's AI requests could carry it there; when your IT team has turned page reading off, Bohm does not send it. An app saved from an answer reads those tables again only when you choose Read again, from the page open in Bohm, without any AI.
When you choose Use an AI chat site to make or change an app, Bohm sends nothing anywhere. It puts your request — with the app's code, when you change one — on your clipboard, for you to paste into an AI service yourself — after showing you all of it, with a note on anything that looks like a key, a private-network address or an email address. The data you entered in the app is not in it, while values written into the code itself are. What you paste is handled under that service's own terms. Your IT team can turn this off.
Bohm opens sites, searches, fills in or clicks on a web page only when you ask it to in the chat. By default it asks you first before submitting a form that sends or changes something (a search goes ahead) or pressing a button that pays, posts, sends or deletes; you can set it to only read. From 0.11.0, before it opens a site it chose itself, Bohm reads that site's public robots.txt — the request carries nothing about you — and, to protect you legally, does not open what the site asks agents to stay out of. Pages you open yourself, or whose address you write in your request, are not checked.
From 0.12.6 you can give the AI that makes and changes your apps skills and MCP servers. A skill is a text file kept in Bohm's data folder on your PC; when a request fits it, the AI reads it, so it goes with that request to the AI you chose. An MCP server is a program on your PC that Bohm starts, or an address it connects to, that you list in Settings or approve when the chat proposes it — Bohm shows the whole entry before adding it. When the AI wants to use one of a server's tools while making or changing an app, Bohm asks you first — from 0.12.7 you can also allow that server for the rest of that one task, and each use is then listed while it works; if you allow it, what the AI passes goes to that program or address, and what it answers goes to the AI you chose. None of it goes through the Company. Your IT team can turn MCP servers off.
When you choose Send as a package for an app, Bohm writes one .bohm file to the place you pick. By default it holds the app's code only; the app's data goes in only if you choose to include it. Where the files you added originally came from is kept as file names only, and AI keys you connected are never included. When you choose Put in a registry, Bohm writes the app's code — no data — to a folder set in its settings (a shared folder, for example). Neither sends anything to the Company or to any other server; who you give the file to is up to you.
When you choose Save this screen in an app, Bohm writes what the app shows now as one HTML file to your Downloads folder. The data on the screen goes into that file, including what is typed in fields (password fields are left out), and Bohm tells you so before saving. It is not sent to the Company or to any other server; who you give the file to is up to you.
When you choose Get for an AI model in Settings, Bohm asks huggingface.co for the model's size, shows it to you with the model's licence, and downloads the model files from there only if you go ahead. The request names the model and comes from your network address; nothing of your apps or their data goes with it, and it does not pass through the Company. Hugging Face handles it under its own terms. Once downloaded, the model runs on your PC without the internet. The speech-to-text model (from 0.10.12) is got the same way, after Bohm shows you its size. Your IT administrator can turn this off.
2. What we collect
- Sign-ups (early access, news, the Mac version) — your email address, the optional note you write, the page language, and the network address (IP address) the request came from.
- Messages — what you write, your email address if you give one, the page language, and the network address it came from.
- Sent from Bohm — the message you write or the email address you give for news, the language of Bohm's screens, Bohm's version, and the network address it came from. Handled as messages and sign-ups below.
- Diagnostics and usage record from Bohm — as described in section 1, with the network address it came from (not stored with the reports).
- Visit statistics — this website uses Google Analytics, which records pages visited, the referring page, approximate location, device and browser type, and sets cookies to tell visits apart.
3. Why
- Sign-ups: to send the news you asked for and to tell you when Bohm for Mac is out (early access sign-ups: to invite you to try Bohm).
- Messages: to answer you and to improve Bohm.
- Diagnostics and usage record: to find and fix crashes and errors and to improve Bohm.
- Visit statistics: to understand which pages are read and improve the website.
The Company does not sell this information or use it for advertising.
4. How long
- News sign-ups: kept until you unsubscribe — every news email says how — then deleted within thirty days.
- Mac version sign-ups: kept until we email you that Bohm for Mac is out, then deleted within thirty days.
- Early access sign-ups: early access ended on October 1, 2026; they are deleted by April 1, 2027.
- Messages: deleted within twelve months of receipt.
- Diagnostics and usage record: deleted after ninety days.
- Visit statistics: kept by Google Analytics for up to fourteen months.
Anything can be deleted sooner on request.
5. Services that process it for us
- Microsoft Azure — hosts this website, stores form submissions, and receives diagnostics (Application Insights, Korea Central region) (Microsoft Corporation).
- Google Analytics — visit statistics (Google LLC).
These services may store data outside the Republic of Korea.
6. Your choices and rights
You can ask to see, correct or delete what you gave us, or to stop receiving email, by writing to hello@bohmbrowser.com. You can block or delete cookies in your browser, or use Google's opt-out browser add-on, to stop visit statistics.
7. Contact
iyulab, inc. — hello@bohmbrowser.com
8. Changes
If this policy changes, the new version is posted on this page with its effective date.