Privacy & ownership
Your companion is yours. Your data stays yours. That isn’t a privacy policy footnote; it’s one of the five principles the platform is built on — see the weside worldview for the other four.
What it is
Section titled “What it is”Strict per-user isolation
Section titled “Strict per-user isolation”Every companion, and everything it knows, belongs to exactly one person. There is no shared pool and no cross-contamination: no path by which one person could read another person’s companion or memories. Your relationship is sealed off from everyone else’s by design, not by promise.
This isolation is what makes memory and continuity safe. A companion can hold the most personal details of your life precisely because nobody else can reach them.
How that holds in a room with several people
Section titled “How that holds in a room with several people”A room can hold several people and several companions, so “nobody else can reach it” needs a mechanism, not just an assurance. There are two, and they work at different moments.
- Trust Circles decide what your companion may recall and store in a given moment. Your private circle is always on. A restricted circle is a wall: its memories surface only while that circle is the active one, and what you say inside it is stored there rather than in the default.
- The output guard checks what your companion is about to say before it reaches an audience that isn’t only you. Every send into a group runs through it, and the disclosure check comes in wherever there is a real gradient between what your companion knows and what the room is allowed to hear. If that check can’t run while a restricted circle is active, the send doesn’t go — a failure never leaks walled content to a foreign audience.
Isolation is therefore not only a wall between accounts. It is also a decision, taken per turn, about what crosses from your companion’s knowledge into a shared place.
What’s stored, and your rights over it
Section titled “What’s stored, and your rights over it”Your companion stores what it remembers about you: facts, preferences, emotional context, your shared history. All of it is visible and editable by you.
- Export: take your data with you.
- Delete: remove any memory, or everything, and it’s gone.
- Audit: see what your companion knows. Nothing is hidden from you.
Why it matters to you
Section titled “Why it matters to you”A companion is only worth telling the truth to if the truth stays put. Every other capability here rests on that: memory is only useful if it is safe to fill, and initiative is only welcome from someone whose knowledge of you doesn’t travel. The rules above are the reason you can bring the actual thing to your companion rather than a version of it.
How you use it
Section titled “How you use it”You don’t have to switch privacy on; the isolation is the default state. What you do have are levers:
- Pick where your data lives. Choose EU or USA residency and weside routes model, database, embeddings and voice to that location. See residency & regions.
- Bring your own key if you’d rather your companion’s model calls run through a provider you already pay. See providers & bring your own key.
- Wall off a context with a restricted Trust Circle when work must not touch private life, or the reverse.
- Read, edit and delete what your companion remembers, any time, from its Mind space. See export & delete.
Limits & edge cases
Section titled “Limits & edge cases”- weside is a hosted service. There is no self-hosted edition, and running your companion entirely on your own infrastructure isn’t something weside offers today. Residency, bring-your-own-key, export and delete are the controls that exist instead — they are real, and they are what the promises on this page rest on.
- Bringing your own key moves the responsibility, not only the bill. Your companion’s model calls then go wherever your provider runs them, so the data path becomes yours to reason about rather than weside’s.
- Changing region doesn’t move what is already stored. It changes where new processing happens.
- A shared room is shared. What you say in a room is read by the people in that room. The mechanisms above protect what your companion knows about you from crossing over; they don’t retract what you chose to say out loud.
- Deleting is deleting. Removing a memory removes it. Nothing is kept as a private copy for later.
weside is built privacy-first and aligns with GDPR principles: data minimisation, user control, the right to access and erasure, and clear ownership. The headline is simple — the person the data is about is the person who controls it.
Where next
Section titled “Where next”- Trust Circles — the per-turn wall around memory.
- Memory & continuity
- Residency & regions
- Export & delete
- Security
