# dex Privacy Policy Version: 2026-10-29.2 Short version: YUKI keeps your stuff on your own machine. The online parts (dex account, membership, dex inference) keep the least they need to work, never your chats or your images, and there's no tracking, no ads and no selling of anything. dex.place and yukiai.app are the same service. ## YUKI on your devices Your chats, files, settings and generated media stay on your PC. YUKI only sends things where you point it: a model provider you chose, your own paired phone, or dex inference if you use it. Update checks (YUKI's releases on GitHub, or dex.place for a bought copy) and crash reports (below) are the exceptions. The phone link goes through a relay at link.dex.place that forwards end-to-end encrypted messages it holds no key for; it can see when and how much is sent, the room id, and the device names exchanged when pairing, never the content. "Report a problem" opens a GitHub issue with logs you can read and trim before sending; it sends nothing on its own. ## What the dex account keeps - **From your sign-in** (Discord, GitHub or Google): the account id they give us, your username (for Google, your name), display name and avatar link. Never your email address itself: if they tell us you verified an email, we keep only a keyed hash of it (HMAC-SHA256 under a secret key that stays on our server). That's enough to recognise your Ko-fi email later. We can't read the address back from it or mail you, and someone holding only a copy of the database can't check guessed addresses against it either. - **Sessions:** a hashed sign-in token, when it was made and last used. Web sessions expire after 30 days, app sessions after 180. A sign-in in progress expires after 10 minutes and is cleared out within a day. - **Your choices:** which version of the Terms you accepted, and when. ## What Ko-fi sends us When you pay on Ko-fi, Ko-fi tells dex.place about it. We keep: the payment type and tier, amount and currency, time, Ko-fi's ids for the payment, the name you show on Ko-fi, and your email **as the same kind of hash**. We don't keep your message, your address or anything else Ko-fi sends. Payment details stay with Ko-fi and its payment providers. ## Paying by card Gumroad, Lemon Squeezy, Paddle or Creem handle card payments. We give them only your dex account id, and keep it with the plan, its status and dates, whether it was a test, their order ids and, if they send your email, only the same kind of hash. Card numbers and addresses stay with them. ## Buying the YUKI app - **Download links** are made for your account and last a short time. The installer's file name carries a short code worked out from your account id (a keyed hash), and we keep each link's code, file, version and time, so a copy shared in public can be traced back to its buyer. - **Activation:** YUKI sends its version and a hash of your PC's machine id (never the id itself). We keep them with when that PC was first and last seen, and when you took a PC off your list (for the monthly limit). Your account page shows each PC by a short code. - **Updates** for a bought copy come from dex.place instead of GitHub. Each check shows that PC's licence and marks the PC as seen. ## dex inference - Your prompts and results pass through dex.place to a host and back to you. dex.place **doesn't store them**. The host's machine sees your request while it runs it (it has to, to answer). Hosts are people lending their PCs: they agree not to keep or look at requests and results, but dex.place can't check what happens on someone else's machine. Hosts never learn who sent a request. When dex inference rents GPU servers (from RunPod), your requests run there the same way: our software keeps nothing, and RunPod runs the hardware. - When YUKI on your PC uses dex inference as its brain, a request also carries what YUKI sends with it: the tools it offers the model (their names and descriptions) and the results of the tools it ran on your PC for that conversation (for example, part of a file it read for you). Tools run only on your PC; hosts never run them. - **No logs by default:** request logging is switched off on dex.place's servers. - Safety checks run on the host, in YUKI's pool software, with a small safety model on that machine (see the [Acceptable Use Policy](/api/legal/acceptable-use)). They read picture requests and the pictures made (chat isn't checked) to decide, then keep nothing but the result: the host tells dex.place the category, and dex.place keeps a count per category per day. - **Web search:** our server sends the words you or Yuki search for to Serper (Brave as backup), never who asked; results are cached up to an hour under a hash of the words. Pages Yuki opens are fetched by dex.place, so sites see our server, not you. - We keep a daily count of your messages, pictures, searches and Deep thinks (for the daily limits) and, for hosts, a daily ledger of requests, tokens and GPU time they contributed. Hosts get only what the model needs to answer a request. ## Sync Sync is off until you switch it on in YUKI. When it's on, your chats, your prompts and the settings that make sense on another PC are encrypted on your device before they leave it, with a key made from a recovery code only you hold (YUKI shows it once and keeps it in your PC's credential store). dex.place stores the encrypted pieces under random names, with their sizes and when they changed, and can't read them: without your recovery code nobody can, us included, and a lost code can't be recovered. Switching sync off with "and delete what dex.place keeps" ticked, or deleting your dex account, deletes all of it from dex.place. Switching off without that box ticked keeps the encrypted copy on dex.place for your other devices. ## Error and crash reports Sentry (EU) gets a report when something breaks: - **dex.place's servers:** which kind of request failed (like /api/pool/v1/chat/completions), the error type and the server version. Never the request, your account or your address. - **The YUKI app,** when it crashes or a part of it stops: the error type and message (with quoted text, web-link details, emails, IP addresses, keys, file paths, and your Windows user and PC names removed), where in YUKI's code, YUKI's version and channel, Windows' version, and which part it was. Never your chats, files or prompts; Sentry is told not to keep your IP address. On by default: switch off "Send crash reports" in YUKI's settings. - **The web app,** when a page breaks: a similar report, never your chats, prompts or account. ## Who else is involved - **Cloudflare** runs dex.place's servers, database and storage (Workers, D1, Durable Objects, R2). - **Ko-fi** handles membership payments. - **Discord, GitHub, Google** handle sign-in. - **Gumroad, Lemon Squeezy, Paddle, Creem** handle card payments. - **Sentry** gets error and crash reports. - **Serper, Brave** get search words only. - **RunPod** rents GPU servers to dex inference. - **Discord** also carries notices to Dex, if he has switched that on: when dex inference is paused on an account (its account id and block counts) or a new host asks to join (its account id and the host's name), a message goes to his own Discord channel. Never content or emails. Each has its own privacy policy. Nobody else gets your data from dex.place. ## Deleting Delete your dex account from your account page (or ask Dex) and it's gone: sign-ins, sessions, email hashes, Ko-fi links, hosts, card payments tied to your account, activated PCs and download records, earlier days' counters, synced data, and notes about the account in Dex's admin view. What stays: - Ko-fi payment records and the membership dates for your Ko-fi email, because they're Dex's bookkeeping. They hold no email, only its hash. Unlinking or cancelling on Ko-fi stops new payments being matched to you. Card payments tied only to your email stay the same way. - Today's usage counts, kept under the same kind of hashes until that day ends and cleared out within a day, so deleting and coming back the same day doesn't reset the daily limits. - If your account had usage-policy blocks in the last 30 days, or dex inference was paused on it: a hash of each of your sign-ins and emails, kept with those block counts (category and day) and the pause, so that deleting and coming back doesn't reset them. Returning through one does not clear the others: each returning account carries the restriction once. The hashes expire once the blocks are more than 30 days old, or a year after deleting if dex inference was paused. ## Children The dex account is not for anyone under 13 (or the minimum age where you live). dex inference is 18+. ## Changes and contact When this policy changes, the version at the top changes. Questions or requests: email saniczlord@gmail.com, or contact Dex through dex.place.