Minimal permanent storage.

Reading without Identity

You can open Talk, read the current live stream, and use #tags without registration.

You do not need a real name, email address, phone number, password, public profile, or Passkey to read Talk. Talk does not create a permanent Identity for someone who only reads.

Creating an Identity

An Identity is created only when you choose to speak and register through Passkeys / WebAuthn. Your authenticator creates the credentials used to prove ownership. Your private key remains with your device, authenticator, or Passkey provider and is not sent to Talk.

For a registered Identity, Talk may store:

credential_id
public_key
current_name
name_credit

What Talk does not require

Talk does not require a real name, email address, phone number, password, photo, job, or biography. Talk is designed to operate with a pseudonymous Identity. Your public @name does not need to reveal your real-world identity.

Private keys

Talk does not receive or store your private key. Talk cannot reproduce it or sign a WebAuthn assertion on your behalf.

If you lose access to the credential and your Passkey provider cannot restore or synchronize it, Talk may be unable to restore access to that Identity.

No permanent message history

Ordinary Talk messages are part of the live stream. Talk does not treat them as a permanent publication archive or create a permanent personal history of messages you sent, messages you read, people you spoke with, topics you viewed, or conversations you participated in.

Talk does not build a long-term behavioural profile from ordinary live conversation.

Live session data

Talk may temporarily process technical session data required to operate the live service:

session_token
active filters
assigned live node
connection state

This information exists to operate the current live session and is not intended to become a permanent behavioural record.

Session filters

You may use temporary session filters to hide an @name or #tag.

-@alice
-#crypto

These filters affect only what you see in the current session. They are not Identity-level blocks, are not linked to another user's public_key, and do not create a complaint or moderation record.

Talk does not need to maintain a permanent server-side history of your session filters.

Complaints

If you submit a complaint, Talk may store information that you intentionally provide for review, including the reported Identity, relevant @name, your description, screenshots, other supporting materials, review status, and moderation outcome where necessary.

This complaint record is separate from ordinary Talk message history. Submitting a complaint does not automatically create a permanent archive of the surrounding live conversation.

Moderation restrictions

If a review confirms a violation, Talk may temporarily restrict the reported Identity from sending messages. Information necessary to enforce that temporary restriction may be stored for the duration required to apply it.

The restriction affects sending messages only. Reading Talk does not require registration or Identity.

Name changes

Each Identity has one current @name. Talk may store current_name and name_credit to operate paid and unpaid name changes.

When a name changes successfully, the previous name becomes available again and the Identity record is updated. Talk does not maintain a portfolio of owned names.

Payments and refunds

For a paid name change, Talk and its payment provider may process information required to complete the transaction. Talk may retain limited information such as:

payment or order identifier
payment status
amount
currency
transaction timestamp
name-change status

Talk does not need to store full payment-card details when a third-party provider handles payment. If you request or receive a refund, Talk may retain transaction and refund information needed to process it, prevent duplicate refunds, maintain accounting records, and comply with legal obligations.

Technical and security data

Talk may process limited technical information necessary to operate the live service, prevent flooding and automated abuse, protect infrastructure, detect malicious requests, and maintain service security. Where possible, this information is limited to what is necessary for those purposes.

Third-party links

Messages may contain links to third-party websites. Those websites operate independently from Talk and their privacy practices are governed by their own policies.

Legal requirements

Talk may retain or disclose information where required by applicable law, a valid legal process, or where reasonably necessary to protect users, the service, or the rights of others.

Operator

Jupiter Soft LLP
Aktobe, Republic of Kazakhstan
Contact: ai@jupitersoft.kz

The basic privacy principle

Talk is designed to know as little as reasonably necessary. You can read without creating an Identity. To speak, you use a Passkey. Your private key stays with your authenticator. Ordinary conversation does not become a permanent personal archive.

Conversation disappears. Identity and @name remain.