DesireBorn
New here? Create your free account
This is adult fiction for adults only. Every character in a sexual context is an adult.
This is adult fiction for adults only. Every character in a sexual context is an adult.
Built around your fantasy, not someone else's.
This site publishes explicit fiction for adults.
Everything here is fiction. Every character in a sexual context is an adult. By continuing you confirm you are 18 or older and that adult material is lawful where you are.
This is a self-declaration, not an age check.
We cannot offer this service in your jurisdiction.
Some places require every visitor to upload government identification before reading written fiction. We are not willing to collect and store identity documents from readers, so we do not operate there. That is a deliberate choice, not a technical limitation.
If the rules change, we will email you once. Nothing else.
This describes what the service does today, not what we intend it to do. When the one changes, so does the other.
Every premise, character note, standing instruction and chapter is encrypted before it is written to our database. Each story has its own key, and the key that unlocks those keys is outside the database. The practical consequence is the one worth stating plainly: if our database were copied, stolen or leaked tomorrow, whoever held that copy would not be able to read a word of anyone's story.
What they would get instead is the readable part described further down: Anonymised account ID , the choices made from our menus, and counts.
The engine runs on our servers, so it has to read your premise, your instructions and the chapters so far in order to write the next one. That happens in memory, for the duration of that one request, and the result is encrypted again before it is stored. We do not read your stories as routine work, and we have built our own admin tools so that they cannot: no screen in this service can display the text of anyone's story. That is a deliberate constraint on ourselves, and it is the one we would notice removing.
Some services describe themselves as zero-knowledge, meaning not even the operator can read your data. That is not possible for a service that writes the story for you, and we would rather say so here than let the word do work it cannot do. The encryption protects your stories where they sit. It does not, and cannot, protect them from the engine that writes them.
Generating a chapter means sending your text to a provider that runs the model. We send those requests with data retention switched off and training on your content refused. We do not send your email address or your account identifier with it.
An anonymised user ID, which site you signed up on, when you last signed in, and counts: stories, sections, words, and what the generation cost. Alongside those, the choices you make from our menus - the genre, the tags you tick, the explicitness level, the narrator, the length - stay in readable form, attached to your anonymised user ID. We use them in aggregate to decide what to build next.
That is the one part of your activity that is not encrypted, and we would rather name it than let it sit unmentioned between two paragraphs about encryption. Your own words are not in that category. Nor is your email address. It is encrypted the same way your stories are, and what sits next to it is a one-way index: it lets us find an address we have already been given, and it does not let us read out a list of who is here. We can open the address itself, and we have to - a sign-in code has to reach an inbox, and an answer to a message has to reach the person who sent it.
To work out which themes we should offer, we count how often individual words appear across everything written here. Those counts carry no account and no story: there is no column in that table that could be joined back to a person, which is why the counting is done at the moment of writing rather than by reading the stories afterwards.
Which country you connect from, where you arrived from, whether your screen is phone, tablet or computer sized, which sections you opened and how long you stayed. Inside the app we also record the steps you take, so we can see where something does not work: which screen you are on, which button you press, how long you wait for a section, and whether an error was shown. When you type in a field, we record that the field was used and how many characters it held - never what you wrote. That goes to our own database. There are no cookies and no advertising network on this site.
Under each section you can tell us whether you liked it, tick a reason and write a few words. We keep that with your account so we can see which story and section it is about, and it is deleted with your account. It is read by the people who build the service, and it is never sent to the model.
After your first sign-in we ask once whether you are a man, a woman or non-binary. It is optional: you can skip it, and you can change it or remove it on the account page at any time. We keep it with your account and use it only in totals, to understand who reads here. It is never shown to anyone and never sent to the model, and it is deleted with your account.
On the public pages, and on the screen where you sign up or sign in, we also use Plausible Analytics, a cookieless analytics service hosted in the EU. We use it so that we have a second count we did not make ourselves. It gets the address of the page you are on, where you arrived from, and the name of a handful of steps: that you passed the age gate, took the test, sent the sign-up form or signed in.
It does not get anything you write, the choices you make in the app, your email address or your account. It sets no cookie and does not store your IP address, and it cannot recognise you from one day to the next. Once you are signed in, nothing more is sent to it at all.
Your browser does not contact Plausible directly. The request goes through our own address, and we pass on only what it needs to count the visit: the details above and your IP address, which it uses to tell visitors apart for the day and does not store.
We would rather name the one thing it does see: the address of a public page tells what that page is about. A visit to a guide about a kink is a visit to that guide, and Plausible counts it as one.
Some countries and US states require identity documents from every reader of adult fiction. We do not collect those, so we have to know where a request comes from and close the door where the law would require them. To do that, the country and, for the United States, the state are read from a copy of three public IP-location datasets that we keep in our own database: GeoLite2 data created by MaxMind, the IP to City Lite database from DB-IP (CC BY 4.0), and the IP2Location LITE database from IP2Location. Your address is looked up in our copy, never sent to any of them.
You delete your account yourself, from the account page, without asking anyone. It goes immediately and it cannot be undone. What goes: your account, every story and every section in it, your waiting-list entry, and any message you have sent us through the contact form.
A deleted story takes its own encryption key with it, in the same operation. There is no copy of that key anywhere else, so the text is not merely unlisted - it is unreadable afterwards, by you and by us.
What stays, and we would rather say so than round it off: two rows of numbers. What your generations cost us, and any star rating you gave a story. Both keep the amount, the date and which model ran; both have your account and the story removed from them, so there is nothing left in either that points back to you. We keep them because we cannot run the service without knowing what it costs, and because a rating is a fact about a story engine rather than about a person.
The contact form keeps your email address, what you wrote, which site you wrote from, the country the request came from, and a one-way hash of your IP address. The hash is there so we can tell whether the same sender is flooding the form; it cannot be turned back into an address. Messages are deleted when they are dealt with.
Reach us through the contact page - we do not publish an email address, because an address on a page like this one is harvested within a day and cannot be taken back.