Private AI characters, with profiles kept in your browser

Private can describe two different boundaries

A private character can mean a profile that other users cannot browse. It can also mean a conversation whose saved history stays on your device. Those are related, but they are not the same promise. A profile can be hidden from a public directory while its prompts still travel to a hosted model, and browser-local history does not make a network request local.

nokeep uses the second boundary as its starting point. Characters are personal profiles in the chat workspace, not public community listings. The browser keeps the profile and saved work for that device. The service does not promise a public marketplace, an automatic importer, or cross-device synchronization.

What stays in the browser

The browser keeps the character’s name, one line, who they are, how they look, their portrait, the voice you picked for them, and your stories and pictures with them. A call is kept the same way: when you hang up, the whole call stays in the chat as text. Open Characters and press a character to see their page and everything saved with them.

Local storage is useful when you want a personal shelf of recurring characters without publishing them. It also creates a responsibility: clearing site data, changing browsers, or losing a device can remove the local copy. Copy important personas and export work you want to preserve. Someone who can use the same browser profile may also be able to see its saved work.

What the model provider still receives

To generate a reply, the hosted inference service receives your message, the character’s name and description, and relevant conversation context. Drawing a portrait sends the appearance description to an image service. The model runs on hosted infrastructure even though the saved character stays in your browser.

Voice works the same way. On a call, what you say is sent to be turned into text and answered, and the reply is turned into speech in the character’s voice. Both are processed under zero-data-retention terms: nokeep does not keep the recordings or the audio, and does not train on them. Calls are in beta.

Treat privacy and model behavior as separate questions. A service may keep no cloud chat-history archive while still sending a prompt to a provider. Read the privacy explanation for provider handling and operational records, and avoid putting real names, secrets, or another person’s private material into a character brief unless the task truly requires it.

A practical private-character routine

Write only the details the role needs. Use a fictional name, a concise motivation, a speaking style, and a scene goal instead of copying a real person’s profile. Keep a separate backup of the persona if it matters. Review the browser device before sharing it with someone else, and delete local profiles or media when they no longer belong there.

You can edit a character you made on their page whenever their manner or motivation changes. For a new scene, press Chat on their page; your latest story stays under Your stories with Continue. Review the response and correct the role when it drifts; the saved character and story provide context, but cannot guarantee perfect recall.

Choose a local profile when you want repeatable setup

Private AI characters are useful when the value is your own recurring cast: a writing partner, a game narrator, a tutor for a fictional subject, or a role you want to revise over time. They are less suitable when your main reason for using a character service is browsing a large public library, following creators, or syncing a profile across devices. nokeep starts with the character you define and the device where you keep it.