skip to content

a friend should be clear with you

your conversations.
our responsibility.

We do not train our own AI models on your conversations.

Hug remembers things, replies, and sometimes checks in first. You deserve to understand how that works—and what happens to the things you share.

a little context goes a long way
“my big presentation is on friday”
conversation memory

Presentation · Friday

“how did your presentation go?”

An illustrative example of memory.
Saved context helps shape a later reply.

One set of data commitments.
Wherever you talk to Hug.

private conversations shared spaces including Discord

01 / the essentials

the things to know first.

These practices apply to Hug across its messaging channels, including iMessage and Discord.

No training our models on your chats.

We use existing AI models to run Hug. Your conversations are not used to train our own models.

read details

No selling your personal data.

We do not sell personal data or use it for advertising. Providers process data to help run the service.

read details

Clear about who can see what.

AI providers process conversations. Authorized team members may review them to operate and improve Hug.

read details

02 / behind a reply

where your words go.

Messages pass through real systems and providers. Here’s the broad picture, from sending a message to getting a reply.

the path of a conversation
  1. 01 / delivery

    Your messaging app

    A message reaches Hug through the channel you use.

  2. 02 / context

    Hug’s systems

    Hug processes the message with relevant conversation history and memory.

  3. 03 / processing

    AI providers

    Existing models process the context to help decide and generate a response.

  4. 04 / reply

    Back to the chat

    Hug sends its response through your messaging app.

Context can persist. Messages and derived memories are stored for continuity.

Operations use data too. Logs can contain messages; authorized staff may review conversations.

A simplified view. Media processing, hosting, logging, and analytics involve the providers listed in our privacy policy.

explore the data we keep and why

03 / memory & models

remembering you.
what that actually means.

A saved memory and a trained model are different things. That distinction matters when we say Hug learns about you.

how Hug uses memory
saved note new message reply

Adding context to a conversation.

Hug can retrieve a fact or earlier exchange to make a reply relevant. That context is stored data, and you can request its correction or deletion.

what we do not do with your chats
your chats model training

Changing a model’s underlying weights.

Training changes how a model works. TAICU does not use your conversations to train its own models. Our details page explains the provider terms too.

read about memory and model training

04 / why we’re building this

research into being
a better AI friend.

Hug is built by TAICU. Our research asks how AI should behave in an ongoing relationship: what it remembers, when it speaks, and how it handles getting things wrong.

Improving Hug can include reviewing conversations and failures. Authorized team access is part of our disclosed data practices.

read about our research
01

Memory

What should be remembered, revised, or forgotten?

02

Initiative

When is a check-in welcome?

03

Repair

How should Hug recover from a misunderstanding?

04

Boundaries

How can an AI respect the people it talks to?

05 / your choices

you have a say.

Across messaging platforms, you can ask about your data, request changes, or ask us to delete it.

  1. 01

    Understand it.

    Ask what personal data we hold about you and request a copy.

  2. 02

    Correct it.

    Ask to correct inaccurate information or remove a saved memory.

  3. 03

    Delete it.

    Request deletion by email. Removing or blocking Hug is separate from deleting stored data.

read about requests and retention

a closer look / Discord

your server.
your boundaries.

The same data practices apply on Discord. Shared spaces also need clear controls over where Hug has access and when it participates.

Hug can receive messages in accessible channels even without a mention. Reply settings determine when it joins in; permissions determine where it has access.

read the Discord details
two different controls
Channel permissionsWhich channels can Hug access?
Participation settingsWhen can Hug join a conversation?
normal
mentions & replies
ambient
can join unprompted

Removing Hug stops new server messages reaching it. Stored data requires a separate deletion request.

keep asking questions

trust is in the details.

Read the fuller explanation, follow the policy references, or talk to the people building Hug.