Privacy Policy

interim · ToS v0.5 · Privacy v0.22 · 2026-11-04

Interim publication: this text has not yet been reviewed by counsel and will be revised when it has. The document is published in English; the English text is the binding one.

1. Who is responsible

The data controller is Artur Zagidullin, an individual established in Vietnam (the operator named in the Terms of Service §1), reachable at [email protected].

2. What we collect

On the website (qarap.io), whether or not you sign in:

• A session cookie. One strictly necessary cookie that keeps your session and links it to the characters you create. Without sign-in it expires 7 days after your last activity; signed in, 30 days after your last activity. Signed in, it also opens your account at qarap.io/app. We set no analytics or advertising cookies.
• Technical data: a pseudonymised identifier derived from your IP address (we do not store the address itself) and your browser's User-Agent string. We use them to prevent abuse and to name the browser in security notices (§8).
• What you provide: the subjects you search for, the characters you create, and the messages you exchange with characters in the web chat, which are stored as conversations (§3).
• Usage data: how you use interactive elements of the chat (such as buttons) and records of the cost of the features you use.
• Optional feedback. If you arrive through a link from one of our studies, we may ask a few multiple-choice questions after a game and keep your answers together with how the game ended. There is no free text; without such a link we do not ask.

On sign-in through Telegram: Telegram provides your Telegram user ID, name and username; we keep them with your account, together with a record of each sign-in (time and browser). What you did as a visitor is merged into your account.

On sign-in by email: your email address. We use it only to sign you in, to confirm sensitive actions (such as deleting your account or changing its addresses) and for the security notices of §8 — never for newsletters or marketing. Sign-in codes are short-lived, single-use and not kept. What you did as a visitor is merged into your account. You can add or remove addresses on your account page (§7).

Directly from Telegram, when you interact with a persona or the qarap bot:

• What you send, as received, with the data Telegram attaches to it: your Telegram user ID, username, display name, language setting, message text, media references, reactions and the chat context.
• Information about chats where a persona is present.
• Documents you send to a persona you own, and information derived from them.

From Threads, when a persona has a Threads feed:

• Replies under the persona's own Threads posts, as Meta provides them: the author's Threads username, the text, the time, what the reply answers and its link. We access nothing else on Threads — not your profile, your other posts or your followers.
• From the owner who connects a persona's Threads account: the account's identifier and username, its profile bio (to check the AI marker, §9) and an access token, stored encrypted.

From the mini app: the Telegram account data Telegram provides to it (ID, username, locale), your plan, and the persona configurations you create.

From payments: subscription events from our payment provider (Tribute): order and subscription identifiers, plan, period. We never receive or store your card data.

From Telegram channels a persona publishes to: aggregate reaction and subscriber counts, and comments on the persona's posts (processed as group messages, §5).

What we do not collect: precise location, contacts, phone number (unless Telegram includes it in something you send), or anything from chats where no persona is present.

3. What we derive: persona memory and knowledge

This is the core of the Service and the part you should actually read.

Personas remember. From conversations and sources we create:

• Conversation memory: summaries of past conversations, and what a persona has learned about each participant;
• Knowledge: information a persona draws from its sources and from documents its owner gave it, with a record of where it came from;
• Search indexes of the above, held by our storage processor (§4) so that a persona can recall them;
• A persona's attitude toward you, inside its fiction, which changes with the course of your conversations. We keep the kind of interaction that changed it, not your words. It is being introduced in one-on-one chats, and applies to visitors too;
• Engagement statistics per chat.

Profiles influence behaviour. What a persona has learned about you, and how you engage with it, may affect whether and how it replies. This is automated profiling, and you are entitled to know about it. Its effect is limited to the fictional conversation: it has no effect on your account, plan or payments (Terms §8).

The attitude is held to the same boundary. It never depends on whether you signed in or paid, and never affects either. It is deleted with your data, the persona or the chat; signing in carries it over to your account.

Legal basis. Memory and knowledge are processed to perform the contract with you (the Terms of Service): remembering is what the Service is. The technical data of §2 and the security notices rest on our legitimate interest in keeping the Service working and your account safe. In group chats and under a persona's Threads posts, messages of participants who have no account with us are processed on our legitimate interest in operating the persona the administrator added; §5 says how to object.

Visitors. Conversations of characters owned by a visitor (not signed in) are stored, but not turned into long-term memory. Once you sign in, they are.

How to not be remembered. There is no per-user memory switch. What you can do today: leave the chat; ask the group's administrator to remove the persona; delete a character you own (this deletes its memory and knowledge); or send us a deletion request (§7).

4. Who processes your data

We use processors; your data reaches them only as needed to operate the Service:

About Gonka. Gonka is a decentralised inference network: a request is answered by a node run by a third party we do not choose and cannot audit. We send there only the processing named in the table — never a person's conversation with their own persona. We cannot promise what an independent node does with a request beyond answering it; do not send sensitive personal information in a conversation with another owner's persona or in a document.

Training. We do not train AI models of our own. Our central language-model providers are used under terms stating that inputs and outputs are not used to train their models; for the decentralised network and for our storage processor we have no such written assurance yet, and we say so rather than imply one.

Primary storage is in Germany (EU). Google processes data in the United States, including the indexed content it processes for Iney.

5. Group chats, channels and Threads

In a group chat with a persona, the persona processes the group's messages, including those of participants who never addressed it; that is what makes it a participant. A persona joins a group only when an administrator adds it and its owner approves. If you do not want a persona processing your messages in a group: ask the administrator to remove it, leave the group, or send us a deletion or objection request (§7).

A persona connected to a Telegram channel reads aggregate reaction and subscriber counts and the comments on its own posts. Comments are processed as group messages.

A persona with a Threads feed reads the replies under its own Threads posts and may answer them publicly. Replies are stored as conversations and may become part of the persona's memory; we build no profile of a Threads author. If you do not want a persona processing your replies, do not reply under its posts, or send us a deletion or objection request naming your Threads username (§7).

6. Retention

• Visitors (not signed in): your user record, your characters, their conversations and their memory are deleted automatically 7 days after your last activity on the website. Signing in, through Telegram or by email, stops this timer.
• Feedback answers (§2) are kept after that deletion in anonymised form, without any link to you or your conversation.
• Accounts signed in only by email (no Telegram) and without a running subscription: after 90 days without activity, an account that never placed an order is deleted as a visitor's is; an account that ever placed an order is suspended instead — its characters stop responding and its data is kept until you sign in again or ask us to delete it (§7), because a refund needs the order record. We write to every email address of the account 14 days before; signing in keeps the account and restarts the period. This expiry is being introduced; until it applies, such accounts are kept like the accounts below.
• Accounts signed in through Telegram: conversations and memory are kept while the Service operates and your data has not been deleted under §7. There is no automatic expiry for active content, and we say so rather than invent one. Earlier versions of memory summaries are deleted within 90 days after they are replaced.
• An email address you removed from your account is kept, unable to sign in, for 14 days so that you can restore it (§7); then it is deleted.
• Web sessions expire per §2 and can be ended by you at any time (§8). Sign-in codes and security links are short-lived.
• Technical logs are kept for a limited period and are not used to profile you.
• Published persona content (channel posts, Threads posts and replies) remains where it was published; see §7.

7. Your rights, and the honest boundary of deletion

You have the rights of access, rectification, erasure, restriction, and objection. Send requests to [email protected]; we will answer within 30 days.

What you can do yourself today:

• Delete a character you own on the website, in the mini app or through the API. This deletes its configuration, knowledge and memory of every chat it was in.
• Delete your account, if you signed in only by email and never placed an order: on your account page at qarap.io/app, after confirming with a code sent to your address. This deletes the account and its characters with their memory, knowledge and documents; we send a last email confirming it. An account with Telegram, or one that ever placed an order, is deleted on request instead (below), because a refund needs the order record.
• Remove an email address on your account page. It stops signing in at once and can be restored for 14 days from the email we send it. The last way into an account cannot be removed.
• Sign out of every web session from the bot or from a security email (§8), or of one browser on your account page at qarap.io/app.
• Do nothing, if you are a visitor: everything expires in 7 days (§6).

What we do on request:

• Find your data. We keep records that let us identify the data relating to you across the Service, so an access or erasure request is answered from a full inventory, not a guess. A visitor without a Telegram account is identified by their session and covered by the 7-day expiry.
• Delete it: your messages and the memory derived from them.
• We do not restore a lost mailbox. If you lose access to the only email address of an account, we cannot move the account to another address: proving you own it is exactly what the mailbox was for. If the account also has Telegram, sign in through Telegram and add a new address; if not, it expires under §6. A paid period on such an account is settled by a refund.
• A Threads author is identified by username. Usernames can change, so name the one you replied under, or link the reply.

Where the boundary honestly is:

• Shared memory. The memory of a group conversation combines the contributions of all its participants. Erasing yours means rebuilding it from the others'; we do this on a valid request, within the 30-day period.
• Our storage processor deletes data at our request. We have asked it to confirm in writing that deletion is permanent and how long its backups keep deleted data; until we have that answer, this policy does not claim it.
• Meta's data-deletion request for a persona's Threads account disconnects that account. It does not delete replies other people left under the persona's posts: those are deleted with the persona, or on request.
• Content published outside the Service (persona posts in Telegram channels and on Threads, and its Threads replies) cannot be recalled by us once published; ask the platform where it lives, and we will delete the underlying data on our side.
• Requests beyond what you can do yourself are fulfilled manually by the operator. Apart from deleting an email-only account and deleting a character, there is no self-service deletion, and this policy will not pretend there is.

8. Sign-in security notices

When a new browser signs in to your account, we notify you through every way into the account: a message in Telegram, if the account has it, and an email to each of its addresses. The notice names the browser and lets you end every web session ("this wasn't me"); doing so also revokes recently added sign-in methods. We notify you the same way when an email address is added or removed. The browser information is used for this purpose only. You can also sign out of a single browser on your account page at qarap.io/app; your other browsers and the Telegram app stay signed in.

9. AI processing disclosure

Persona replies are generated by AI. Your messages in persona conversations are sent to the providers listed in §4 for that purpose. Personas are marked as AI in their Telegram profiles, in their Threads bio, on their public pages and in the web chat (Terms §4).

10. Public pages

Every persona has a public page at a random address that is not derived from your account or the persona's name. The page exists from the persona's creation, whether or not you share it, unless the persona depicts a real person whose likeness may not be shown publicly. If you have signed in, search engines may index the page. The page of a persona whose owner has not signed in asks search engines not to index it and is reachable only through its link. To remove a page from search results, delete the persona; a search engine may keep showing it until it revisits the address. The page shows the persona's name, portrait, description and world and, if a Telegram channel is connected, its posts with aggregate counts. It shows no data about you, with one exception: how many badges you yourself earned with your persona, by kind. When a persona is deleted, its page only says that the persona is gone. We record visits to the page and shares of its link, without IP address or account, to learn whether characters are shared; a visit counts as activity of the owner for a visitor's 7-day expiry.

11. Children

The Service is not directed at children and requires users to be 18 or older (Terms §2). We do not knowingly collect personal data from anyone under 18 and delete it when we learn of it. Personas depicting minors are prohibited outright (Terms §5).

12. Changes

We will announce material changes in the bot, the mini app or on the website before they take effect. The current version is always available at this address.