Kuyun AI · Works to try

Help · Your data

Your data

What Kuyun keeps

What it does not keep

Where it lives

Everything of yours is stored together, separately from every other account, in Google Cloud in the United States (Oregon), run by the Kuyun operator. It is not sold, and it is not shared with other users — sharing a project shares that project and nothing else (see Sharing a project).

On the browser you use, a copy of some lists — your projects, and the first page and topics of Explore — so each page opens at once with what it showed last, then brings itself up to date. With your projects it keeps a short code Kuyun gave it, which says nothing of them: on opening Create or the Shelf it asks whether the code is still the same, and fetches the list again only when something in it changed. It is your account's alone, erased when you sign out or delete your data, and dropped after two weeks. What Explore chose for you because of your interests or your city is not in it.

On the same browser, the cover pictures it has shown you, so a page that shows them again paints them at once. At most 100 MB in all, and no picture over 5 MB; past that, the ones shown least recently go first. They are your account's alone: erased when you sign out, when you delete your data, and when someone else signs in on that browser. Kuyun reads them only to show them to you, and there is nothing to save them with. Signed out, nothing is kept.

Your conversations go to an AI model provider to be answered. That is unavoidable — it is how the answers are produced. See The AI models behind Kuyun for which providers, and what that means.

A written answer on a practice paper goes to one only if you ask. A letter or an essay you write on a paper is kept with your results, whole. It is sent to a model when you press Have it marked on it, that one answer, to the reviewing model in The AI models behind Kuyun — and not otherwise (Practice in a course, "A paper"). The marks are kept with the answer.

Seeing it

Settings → My Files browses everything Kuyun holds about you, like a file explorer. Not a summary of it — the actual contents. A project's tables appear there as one file per project, shown as the tables themselves.

One thing kept with a project you made is not yours to browse: what the people you shared it with did there — where they stopped reading or listening, what they answered in its practice, what they wrote on a paper and how it was marked. That is theirs. My Files leaves it out of your project's history and says that it has, and so does Kuyun when you ask it to read your files for you. What you did in your own project, trying it out, is yours and is shown.

Each project also has a summary file there: where the project stands (its files, its plan, what it is working on), kept so that it opens quickly however long its history is. It holds nothing the project does not, it goes when the project does, and when someone who viewed a project shared with them removes it, the summary is made again without them.

Settings → About Me lists what it believes about you, with where each belief came from, including ones that have been superseded or hidden. You can correct or remove any of them. It also lists what Kuyun has asked you about yourself, and what came of it. Under Your interests, rebuild clears what Kuyun inferred and rebuilds it from your whole history over the next few minutes; interests you pinned or muted survive.

How Kuyun writes for you, also on About Me, says how technical the assistants are with you — everyday language, some technical words, or technical detail — with when and why it was judged. Everyone starts with everyday language. Once a week Kuyun looks at the messages you wrote in the last four weeks, each with a little of the reply you were answering, and adjusts it, at most one step at a time after the first look. Answers you picked from a list are not counted as your words. Only the latest reason is kept; the next judgement replaces it. To change it, just say so in any chat ("simpler, please", or "you can be technical with me"); the assistant follows that right away, and the next weekly look reads it with the rest of what you wrote. Ask it to KEEP that ("always use plain language") and the level changes at once, with your words as the reason, and the weekly look leaves it alone until you ask Kuyun to forget it. Once a week Kuyun also reviews, for itself, how well its replies were written for you — answer first, at your level, in the right form, no longer than needed — and keeps only counts per assistant, none of the words.

How you want to be answered. Ask your home chat or a project's chat (Help does not keep these) to keep how you like your answers — "short answers, plain language", "answer me in French", "use bullet points" — and it saves it at one of two levels:

If you did not say which, the chat asks once: "For all your chats, or just this one?". In a project shared with you, your preferences shape the replies to you, and the replies to other people follow theirs. A rule about the work itself — "British spelling in the lessons" — is not a preference about your answers: tell the project's chat, and it goes into the project. An assistant only says it has kept something once it has.

Deleting it

Two separate actions, both in Settings → Account, both requiring you to type your sign-in name to confirm.

Delete all my data — removes everything: profile, memories, transcripts, projects, files, customisations. Your login stays. You come back to an empty account, as if it were new.

Delete my account — the same, plus the account itself. You are signed out and cannot sign back in.

Both are real deletions, not hiding. There is no undo, and Kuyun says so before you confirm.

A picture you replace or remove, a cover or one in a work, stops showing on Kuyun at once, and its file is erased a day later. So does a sound file, such as a chapter Kuyun read aloud: removed or read again, the old one stops playing on Kuyun at once, a player already playing it can go on for up to ten minutes, and it is erased a day later. A copy kept along the way, in someone's browser or in the cache of the service that stores the pictures, can still show for up to an hour to anyone who has its address, and the same is true of a cover when you unpublish or archive the work. Deleting your account or your data erases your pictures at once, with no such day.

Some things they do not reach, and you should know them before you rely on either.

Deleting your data keeps your tokens record — what you spent each day, by kind of use, and the plan you are on (Tokens) — and your credit record: what each credit paid, for which project. They are account records, not your content: if a wipe refilled the day's free tokens or the credit, it would be a way around them. Deleting your account removes them, and cancels a paid plan at once rather than at the end of its month — Stripe stops charging you from that moment.

If you shared a project with someone, their side of the conversation lives with them, and deleting your account does not reach into their account to remove it — delete the project first if you want it gone for everyone.

If someone shared a project with you as a viewer, you can remove it and everything you did in it — your conversation, your place, what you finished, your practice answers, the marks a written answer was given — without deleting anything else (Sharing a project, "Removing a project you view"). Your tokens record keeps what that use cost, as it does for any deletion. Delete all my data and deleting your account remove the same from every project shared with you: where you were in it, what you finished, the level a placement found for you, the answers you typed in its practice and any marks they were given. What you added to a project you contribute to stays with that project.

A note you sent the people who made a project goes with your data if nobody has answered it yet. One they already answered stays with their project, with the answer, like a letter that was read — remove the project first, and nothing new reaches you about it afterwards either.

A practice answer you sent with I think I'm right goes with your practice answers: it never carried your name, and the people who made the course stop seeing it. If they already agreed and added it to the course, it stays there as part of their work.

A file uploaded in the system's first months may have been stored in an older way that the account-wide sweep does not find; deleting that file on its own, from My Files, does reach it, so do that first if it matters to you.

A project's tables keep their own history: when a value is corrected or a row removed, what it was before stays in that history until the project is deleted. Deleting the project — or all your data — removes the tables and their history together.

The one-line descriptions Kuyun writes beside a project's files work the same way: deleting a file or an entry removes it, but its line stays in the project's history until the project itself is deleted, and nothing shows it once the file is gone.

And if Kuyun ever had to escalate a problem with one of your projects to the people who run it, deleting the project hides your title and what you wrote from anyone reading their operations log — the original entry is not erased, but no one is shown it — while deleting your whole account does not hide them. So if a project's wording matters to you, delete that project first, then the account.

How long the copies last

The terms set the longest a deleted thing may survive in Kuyun's backups (Terms of Service and Privacy Policy, "How long it is kept"). Today the windows are these:

Routine connection logs, which include the address your connection came from, are kept only as long as ordinary logs are.

Before you have an account

Coming back afterwards

You can sign up again with the same email address. It will be a new account — not the old one restored, and without a second welcome credit, which an inbox is given once (Tokens). Your old handle stays retired and cannot be taken again, by you or anyone else, because a name in a conversation has to keep meaning one person.

Remarks you make about kuyun

A tap on "did it help?" after something you asked for ships is a remark too, kept the same way.

To tell kuyun what you think of it, type /remark followed by what you want to say, in any chat — for example /remark the player stops on my phone; typing / alone lists it to pick — or write it in the box on Settings → Remarks. A /remark goes straight to the Kuyun team, never to the assistant you are talking to, and goes at once, even while a reply is on its way; the chat says "Your remark is sent to the Kuyun team", and you are told when they answer. The assistants do not note remarks for you: one you only say to them in passing is a message like any other. Either way, the remark is kept in your own data, where you can see it under My Files, and it is deleted with your account like everything else there. The Remarks page lists what you have said, newest first, with the team's answer under each once it comes, and the request it opened when the review filed one.

A remark says where you made it, so the team can find what you mean without asking you again. Both kinds keep the page you came from (which project or work, for instance — never what you searched for), the app's version, your browser and your screen's size, and a /remark also keeps which conversation it was typed in, with its project and assistant. It keeps nothing of the conversation itself: none of what you or the assistant said is sent with it. It is kept with the remark, in your own data, and deleted with it.

Remarks are not anonymous: the people who make kuyun read them, with your name attached. That is the point — a gripe or a compliment reaches a person who can act on it. Only you send one, so nothing reaches the team as a remark that you did not send yourself — apart from the note an assistant makes when it is stuck, below.

When an assistant gets stuck, the team hears it. If an assistant cannot do what you asked — the same step fails twice, or it has no way to do it at all — it notes that for the team itself, as one of your remarks: what you asked for, what went wrong and what it tried. It names the conversation it happened in, so a person fixing the fault can find the moment it happened (the people running kuyun look at stored data only to fix a problem, Terms of Service and Privacy Policy). The assistant tells you in a few words that the team has it, and stops trying the same thing again; it does not say so unless the note was actually made. Once a day at most five of these are noted for you. It is kept, read, answered and deleted exactly as your other remarks are. Settings → Remarks shows it by what you asked for; what went wrong and what was tried are kept with it for the team.

Your remark is also read on the machine the team works on, once a day, so it can be answered. It is read there, not stored: that machine keeps a record of what the software wrote back that day, with your account's name, and deletes it on its own seven days later — deleting your account does not reach it sooner. The software that reads your remark there cannot open anything else on that machine. It reads that day's remarks from everyone together, so it is told never to repeat one person's words or name to another, and an answer that does is held back rather than sent — your remark then waits for a person at kuyun to answer it instead. If the review turns your remark into a tracked request, the request is filed under your name, kept with kuyun's other requests, and shown to you and the people who run kuyun — never to other users; deleting your account does not remove it. A request the team files themselves from several people's remarks is theirs, not yours. Remarks, the problem reports described above, and a report you send about someone's published work are the only things you tell kuyun that leave your own data.

You get an answer. Every remark is read, and answered — by the review, or by a person when the review held its answer back — sometimes "we have opened this and someone will look at it", sometimes why it already works, sometimes just thank you. The answer arrives as a notification, which opens Settings → Remarks if you want to say more, and if you are mid-conversation the assistant will pass it on. Something worth building becomes a tracked request, and a person at kuyun decides whether it is built; the assistant cannot promise that and will not.

You hear what becomes of it. Under your remark on Settings → Remarks, the request it opened says where it stands, in one of four words: waiting for the team to decide, being built, shipped or not planned. When it moves to being built, ships — which is when the change is live in the app, not when it is written — or is not going to be built, you get a notification, and the assistant passes it on the next time you talk — while the team is still looking at it, nothing is sent. The team can add a sentence for you with their decision, or write to you about it at any time; it appears under the remark too. When it ships, the notification usually says in a sentence or two what changed for you and where in the app to find it — written when the change was made, and read by a person at kuyun before it went out. You never see their internal notes, reports, or anything about other people who asked. You can still ask the assistant about a request by its id.

This is a page of Kuyun's own handbook, the one its assistant answers from — ask it in the app and it will say the same.