Privacy

Privacy policy

Plain words. Last updated November 2026.

Webgochi is a widget and a cabinet operated by Webgochi [legal entity placeholder] (“we”). This page explains what we learn about two groups of people: customers, who sign in to the cabinet and put the widget on their sites, and visitors of those sites, who meet the character there. Questions or requests: [email protected].

Two roles

For visitors of a customer’s site, the customer decides why the widget is there and what it asks; the customer is the data controller and we are the processor, handling that data on the customer’s instructions and under the terms of service. For customers themselves, we are the controller of the account and billing data described below.

What we collect from customers

• Account. Your Google profile when you sign in with Google: email address, name and profile picture. If you sign in with an email code, your email address.
• Sites. The sites you create: name, domain, allowed origins, the character’s settings, the knowledge and prompts you write, tours, integrations (a Telegram chat id, a webhook URL, a notification email address), and the briefs and references you send for a custom character.
• Billing. Subscription status and dates. Payments are processed by Stripe; we store Stripe’s identifiers for your customer and subscription, never your card number.
• Usage. Server logs with your IP address and the requests you make to the cabinet, kept briefly for security and debugging.

What the widget collects from visitors of customer sites

• Chat. The messages a visitor types, the answers, and the operator’s replies. Messages are sent to an AI model through OpenRouter to write the answers.
• Page. The URL and title of the page the widget is on, and the referrer.
• Device. The browser’s user agent, the approximate country, and the IP address stored only as a one-way hash.
• Leads. What a visitor leaves in a lead form or in the chat: name, email, phone, message, as the customer has configured the form.
• Events. That the widget was shown, opened, poked, that a tour started, that a lead was sent, and similar, so the customer can see how the character is used.

The widget identifies a visitor with a random id kept in the browser, not with a cookie, and not with anything that identifies the person across other sites.

How we use it

To run the service: show the character, answer questions, deliver leads and handoffs to the channels the customer connected, bill subscriptions, send the emails the service needs (sign-in codes, notifications, trial and billing notices), and keep the service secure. We do not sell personal information and we do not use it for advertising. Chat text is not used to train AI models by us; our AI providers process it to generate the answer.

Who processes data for us

Each provider handles only its part of the job:

Cookies and browser storage

• The widget sets no cookies. It keeps a random visitor id and small state (such as whether the character was dismissed and the current conversation) in the browser’s local storage and session storage under keys that start with wg:. Clearing site data removes them.
• The cabinet sets a session cookie when a customer signs in, to keep them signed in. We use no advertising or third-party tracking cookies anywhere.

How long we keep it

• Visitor data (chats, events, leads) is kept for the retention period the customer sets for the site; the default is 180 days, after which it is deleted. Leads the customer keeps in the cabinet stay until the customer deletes them.
• Customer accounts and sites are kept while the account exists.
• Billing records are kept as long as accounting and tax rules require.

Your choices

Customers can edit or delete their sites and the visitor data in them from the cabinet, and can ask us to delete the whole account. Visitors of a customer site should contact that site’s owner first (the controller); we help the owner fulfil the request. Anyone can write to [email protected] to ask what we hold about them, to correct it, or to have it deleted; we answer within 30 days.

Security

Data travels over TLS and lives on servers in a European data centre. Access to production is limited to the people who run the service. Webhook deliveries are signed so the receiving system can verify them.

Children

The service is for businesses and is not meant for children under 16. We do not knowingly collect their information.

Changes

If we change this policy we update this page and the date at the top; for material changes we email customers.