Privacy Policy
Effective Date: July 28, 2026
This Privacy Policy explains what information yeon (“yeon,” “we,” “us,” or “our”) handles when you use the yeon browser, the yeon licence service, the yeon Discord bot, and this website — what stays on your own computer, what reaches a server we run, and why. It is written to describe what the software actually does. Where a common privacy promise would not be true of yeon, we say so instead of making it.
1. The short version
- Your identities, autofill profiles, saved accounts, cookies, proxies, purchase history and stored credentials stay on your computer. We do not receive them. The one exception is team queue telemetry, described in section 4, which sends details of your ticketing queue sessions — including the account email on the tab — to your team’s dashboard. It is always on in the current build.
- yeon does send us a small daily usage summary tied to your licence, and that summary includes the hostnames of sites you opened — not full addresses. This is described in full in section 4, and there is currently no setting to switch it off.
- Team queue telemetry sends your ticketing queue sessions to your team owner’s dashboard as they happen — the event, the full web address, the identity and profile in use, the account email signed in on the tab, and every queue position. This is always on in the current build and cannot be switched off. It is described in section 4.
- Our licence server holds your licence record, the devices it is bound to, your team membership, and — if you use the Discord bot — your Discord user id.
- Crash reports stay on your device. yeon is built with Google’s metrics, crash-report and variations uploads switched off and with no Google API keys — though yeon is built on Chromium, and some standard browser features still contact their own providers unless you turn them off (section 3).
- This website runs no analytics, no advertising, and sets no cookies.
- We do not sell your information, and we do not share it with advertisers or data brokers.
2. What this policy covers
This policy covers the yeon browser, the yeon licence service at bridge.yeon.sh, the yeon release service at download.yeon.sh, the yeon Discord bot, and this website at yeon.sh.
What it does not cover. We also operate separate websites of our own that are unrelated to the yeon product, and we carry out browser-fingerprinting research on visits to those sites. That research has nothing to do with yeon customers, is not linked to any yeon licence, account or person, and its subjects are visitors to those sites rather than readers of this page — so notice for it belongs on those sites, not here. The one place that work touches the yeon product is the “Online device profiles” feature, which draws on the device data we collected there; that connection is described in section 5.
This policy also does not cover the websites you visit through yeon, or third-party services you choose to connect to yeon, such as an email mailbox, a sign-in-code provider, or a proxy provider. Those are governed by their own policies.
3. What stays on your computer
The great majority of what yeon holds never leaves your machine. yeon is a browser: it stores this data locally in your yeon user-data folder, the same way any browser stores your profile. We have no copy and no way to read it.
- Your identities and their per-identity device profiles, cookies, and site data.
- Your autofill profiles and saved accounts, including names, addresses, phone numbers, email addresses, and payment-card details you import or enter.
- Your proxy list and proxy credentials.
- Your recorded purchase history.
- Your stored secrets — mailbox credentials and sign-in-code provider keys. Some of these, such as your mailbox password and your text-message provider tokens, are write-only in the interface: yeon will tell you whether a value is set but will not display it back. Others, including proxy and account passwords and saved card details, can be read back in yeon’s own settings, since that is where you manage them.
- Your licence key, cached locally so yeon can start when you are briefly offline.
- Crash reports. yeon writes crash data to a folder inside your own user-data directory. It is not uploaded.
- Persona details used for form filling, which are passed only to a helper running on your own machine over a local loopback connection that never leaves the computer.
One feature copies some of this off your machine: team queue telemetry (section 4) sends the identity, profile name and account email attached to a ticketing queue tab to your team’s dashboard along with that queue session. It is always on, and it is the only thing in this section that ever leaves.
This information is held in ordinary files in your yeon user-data folder, protected by your computer’s own user account rather than by a separate yeon passphrase. Anyone with access to your operating-system account, or to an unencrypted backup of it, can read it. If that matters for your situation, use full-disk encryption.
yeon is built with Google’s metrics, crash-report, variations and sync uploads switched off and with no Google API keys, so the usual browser telemetry to Google is not present. yeon is nonetheless a Chromium-based browser, and a few standard browser features still talk to their own providers at their usual defaults — address-bar search suggestions go to your search engine, and the built-in check for passwords caught in known breaches contacts Google. Both can be turned off in yeon’s settings.
4. Usage reporting — please read this section
This section covers the two ways yeon reports on how you use the browser, and we would rather state them plainly than bury them. The first, a daily usage summary, is always on. The second, team queue telemetry, is always on — and it sends far more.
The daily usage summary. Once yeon is activated with a licence, it keeps a running daily tally on your computer and periodically uploads it to our licence server. Each day’s summary contains:
- how many seconds the browser was actively in use, and how many sessions;
- the hostnames of pages you opened in a top-level tab, with a count of how many times each was opened — for example
example.com, up to fifty hostnames per day; - the yeon version you are running;
- your licence key, and an identifier for your device. The device identifier is a one-way value derived from your operating-system installation or from a random value stored on first run — yeon does not read hardware serial numbers, MAC addresses or disk identifiers. On our server the summary is stored against a hash of your licence key rather than the key itself.
The first upload happens about a minute after the browser starts, and roughly every five minutes after that.
What the daily summary deliberately excludes. In this summary only the hostname is recorded. Full web addresses, paths, query strings, search terms, page contents, form data and page titles are never recorded or sent into it, and the browser refuses to store anything in it that is not a bare hostname. This is a statement about the daily summary, not about yeon as a whole — the team queue telemetry described below does send full web addresses, and it is a separate feature with a separate switch. Only ordinary web pages count: internal yeon and browser pages are ignored, and so are frames inside a page. Nothing is sent at all before the browser is activated.
We use this to understand how much yeon is used, on which versions, and which sites need engineering attention.
There is currently no setting to turn the daily summary off. We are telling you that rather than implying a control that does not exist. If this matters to you, please raise it with us at admin@yeon.sh before purchasing.
Team queue telemetry — always on. yeon records your ticketing queue sessions (Ticketmaster, AXS, Queue-it, Live Nation): which event you are waiting for, your position in the queue as it moves, and whether you reached checkout. That recording stays on your computer. Separately, you can switch on team queue telemetry, which sends those records to your team owner’s dashboard while the queue is still running, so a team can see who is through and who is stuck. It is always on and has no off switch. Neither does the recording it depends on: yeon records your queue position on those sites always. The only queue setting in yeon’s toolkit is how tabs are ordered.
While it is on, each queue session we receive contains:
- the event, venue, date and site;
- the full web address of the page — the whole link, including anything after the
?. This is not the hostname-only rule described above; that rule applies to the daily summary and not to this; - which yeon identity the tab was using, that identity’s profile name, and the email address of the account signed in on it;
- every queue position, percentage and checkout-timer reading yeon saw, with timestamps, and whether the session ended in checkout or a purchase;
- your licence, your device identifier and the yeon version, as above.
Payment details, card numbers, passwords, page contents, form fields and screenshots are not part of this and are never sent by it.
Who sees it. Your team owner — the manager seat on your licence team — sees every seat’s queue sessions on your team’s dashboard, including the addresses, profile names and account emails above. Everyone else, including every other seat on the team, sees only their own. If your licence is not part of a team, only you can see it. Which of those applies is decided on our server from your own licence, not from anything your browser asks for. If you are on someone else’s team, switching this on means that person can see the accounts you are queueing with. That is the purpose of the feature, and it is why it is off until you choose it.
Switching it off stops the sending, not the recording: your own local queue history stays exactly as it was.
5. Online device profiles
yeon can give each identity a device profile drawn from real-world device data we collected ourselves, so that an identity presents a coherent, ordinary device rather than an obviously synthetic one. This setting is on by default, and you can turn it off in yeon’s settings, which returns yeon to generating device profiles entirely on your own machine.
This is a download, not an upload. Every request yeon makes for a device profile only reads from our server. The browser never sends us a measurement of your own device, and it never uploads anything about your hardware, your browsing or your identities to it.
When the setting is on, those requests:
- carry no cookies, no licence key and no device identifier;
- fetch, at most once per browser run, the list of sites we support — a request that carries no site name at all, because the list is the same for every user;
- and, only when you navigate to a site that is already on that published list, ask for a device profile suited to it. The only site name ever transmitted is one we published ourselves, and only the bare domain — never the page you were on. Every other page you visit is silent, and we do not learn it;
- include an opaque identifier, derived one-way from the proxy you assigned to that identity, so that the same identity keeps getting the same device rather than a new one each time. It is not your proxy details, and it does not identify you to us.
Separately, when an identity is bound to a proxy, yeon asks a server we operate to report which country and time zone that proxy exits in, so the identity’s clock and locale match. That request is made through your proxy and carries no cookies and no data; the server sees the proxy’s exit address simply because it is the address the request arrives from. Your own address is not sent, and no third-party geolocation service receives anything from your browser.
6. Licensing, devices and teams
Our licence server holds, for each licence:
- a hash of the licence key, used as the record’s identifier, together with an encrypted copy of the key itself. The encrypted copy exists for one reason: so a team manager can retrieve the keys they are responsible for handing out. Some older licences have no recoverable copy and show as “not stored”.
- the plan and product, the expiry date, the device allowance, and whether it is revoked;
- an optional label, when the licence was created, and when it was last seen;
- the devices the licence is bound to — a device identifier, the yeon version, and first- and last-seen timestamps;
- team information where applicable: the team, its seat count, which seat is the manager, and a record of which Discord user each seat was assigned to and by whom.
A team manager can see the full licence key of every seat on their own team, through the dashboard on this site and through the Discord bot. The team is determined on the server from the manager’s own key, so no one can request another team’s keys. An ordinary seat holder sees only their own. Where a seat has switched on team queue telemetry (section 4), the manager also sees that seat’s queue sessions, decided the same way.
While yeon is running it re-checks your licence with our server every few minutes, sending your licence key, your device identifier and the yeon version. This is what keeps a revoked or expired licence from continuing to work, and it is what updates the “last seen” timestamps above.
As with any internet service, our servers necessarily receive your network address in order to answer a request. We do not store your address in our records: there is no address column in any of the tables above. It can appear in ordinary server logs, and one action — resetting your bound devices — deliberately writes a log line recording the address it was requested from, so that a licence being passed around can be investigated.
7. Updates
yeon checks for a new version shortly after it starts and then periodically. The check is a plain request for the latest published version for your operating system. It sends no licence key, no device identifier, not even your current version, and no cookies.
If you choose to install an update, the download itself is authorised with your licence, so that step does identify your licence to our release service. Our release service keeps no per-user record of downloads.
8. Discord
If you use the yeon Discord bot, we store the Discord identifiers needed to make it work: your Discord user id against your licence seat, so the bot can confirm a licence is yours and deliver keys privately; the id of a team’s owner; and, where a server has set up the cart assistant, that server’s id and the channel id it nominated, together with the id of the administrator who configured it.
Replies containing licence information are sent privately to you, so they are safe to request in a shared channel. Your use of Discord itself is governed by Discord’s own privacy policy, not this one.
9. The cart assistant
If you use the cart assistant, yeon posts an approval card to Discord when a cart is held. That card carries the cart’s details as text: the event, the seats, the price and fees, the web address of the checkout page, and the email address from the autofill profile being used. Your licence key is not included. These details are not redacted — they are the substance of what your team is being asked to approve.
If your Discord server has nominated a channel, cards go there. If it has not, a card may instead reach a yeon-operated channel, because otherwise the feature could not work at all. If you would rather that did not happen, nominate a channel of your own — or do not use the cart assistant.
Cart records are held in memory on our server for a few minutes so the buttons keep working, and are then discarded. The message posted to Discord, however, stays on Discord — we do not delete it, and we could not.
Separately, yeon can send a screenshot of the checkout page to your team’s own Discord channel. This is deliberately manual and deliberately visible:
- nothing is captured unless you press the button yourself;
- payment and personal fields — card number, expiry, security code, password, phone, email, name, address and postcode — are covered automatically by default, as is any payment form hosted by the payment processor;
- the covered areas are painted out before the image is encoded, so those pixels are genuinely absent from the file rather than hidden under a layer;
- you are always shown the exact image, and the destination channel is named, before anything is sent — and you can cover more of it yourself, or cancel;
- the automatic covering can be switched off in that preview, with a warning. If you do, the payment and personal details on that page are sent exactly as they appear;
- the image is delivered only to the channel your own team or server configured. It cannot be routed anywhere else;
- we do not store or log the image. Only its file name, type, dimensions and size are noted in passing, and the image is discarded once delivered.
Please remember that everyone who can read that Discord channel can see what you send, and that anything a page prints as ordinary text rather than as a form field — an order summary, for example — is not covered automatically. That is why you get to review the picture first.
10. This website
yeon.sh runs no analytics, no advertising, no tracking pixels and no third-party scripts, and it sets no cookies. Two values are kept in your browser’s local storage and are never sent to us: your light/dark theme choice, and — only if you sign in to the dashboard — your dashboard session, so the page can show your licence without asking for it again. Signing out removes it.
The site runs on a server we operate, and Cloudflare carries the requests needed to serve these pages.
11. When we share information
We do not sell your information and we do not share it for advertising. We share it only with the service providers that host and operate yeon’s infrastructure, acting on our behalf; with Discord, to the extent you choose to use the Discord bot; and where we are required to by law, or where it is necessary to protect our rights, our users, or the security of the service.
12. Keeping, correcting and deleting information
We keep licence, device and team records for as long as the licence exists and for as long afterwards as we need them for our records. Daily usage summaries are kept as historical rollups, with no automated deletion schedule — we would rather tell you that than quote a retention period the software does not enforce. Team queue telemetry (section 4) is the exception, because it is the one thing here that is deleted on a schedule our software actually runs: a queue session is deleted 90 days after it was last seen, and its position readings 30 days after they were taken.
You can unbind every machine from your licence yourself at any time, using Reset devices in the dashboard; the next machine you sign in on is bound afresh.
For anything else — a copy of what we hold about you, a correction, or deletion — write to admin@yeon.sh and we will deal with it manually. Depending on where you live you may have rights of access, correction, deletion, portability or objection under laws such as the GDPR or the CCPA; that address is how to exercise them. Deleting your licence record ends your ability to use the software.
13. Security
Traffic between yeon and our servers is encrypted in transit. Licence keys are stored as a hash plus, where recovery is supported, a separately encrypted copy — never as plain text. Access to team keys is decided on the server from your own licence, not from anything your browser or Discord client claims. No system is perfectly secure, and we cannot guarantee absolute security.
14. Children
yeon is not directed to children. We do not knowingly collect information from anyone under the age at which they could agree to these terms in their own country. If you believe a child has provided us with information, write to admin@yeon.sh and we will remove it.
15. Where information is handled
yeon is operated from the United States, and the infrastructure that runs it may process information in the United States and elsewhere. If you use yeon from another country, you understand that your information will be handled in countries whose data-protection laws may differ from your own.
16. Changes to this policy
If we change what yeon collects, we will update this page and change the effective date above. Where a change is material we will take reasonable steps to tell you, such as a notice through the service or in our Discord. Continuing to use yeon after a change takes effect means you accept the updated policy.
17. Contact
This policy is effective as of July 28, 2026. If you have any question about it, or about anything yeon holds, write to admin@yeon.sh.
Read the Terms of Service, return to the yeon home page, or read the documentation.