Privacy

Verb runs an AI assistant inside your product so your users can ask for things in plain language. That means we handle two very different kinds of data, and it is worth being precise about both.

Your account

When you sign in we store your email, your name and your profile photo, taken from whichever provider you used. We store which organisation you belong to. That is the whole list.

We never receive your password. Signing in with Google or GitHub means they tell us who you are; they never hand us your credentials.

We email you about getting set up: a welcome, help with your first site and taking it live, and now and then what is new in Verb. We note whether those emails are opened or clicked, to learn which ones help. Every one has a one-click unsubscribe, and if you stop reading them we ask once and then stop on our own. Sign-in codes and notices about your own site still arrive, because they are about something you run.

Your users' conversations

Nothing that follows them around. A visitor who is not signed in gets a random reference that lasts only as long as their browser tab. We deliberately do not keep a cross-session identifier for people who never signed in. What they asked is kept like any other conversation, until you ask us to delete it.

Identity comes from a token your own backend mints. We verify it, hash it with a salt unique to your site, and never store it. Because the salt differs per site, the same person using two products built on Verb cannot be linked between them, including by us.

The record of what happened

Every action the assistant takes is written down: which tool, which arguments, what came back, and whether the change was confirmed to have actually happened. That log is yours. It exists so you can answer "what did this thing do in my product" without taking our word for it.

Paying for Verb

When you pay for a plan, Dodo Payments processes it as our merchant of record. Your card or UPI details go to Dodo and never to us. We keep what we need to run your account: which plan you are on, its renewal date, and a reference to your customer record at Dodo, from which we show your invoices. Dodo's own handling of payment data is covered by its privacy policy.

What the assistant never touches

• Payments, checkout, carts or card details in your product. Not a limitation, a decision
• Your users' passwords or sessions
• Your database. The assistant calls your API, with your user's own permissions

This website

askverb.com, the page you are reading, can use Google Analytics and DataFast to count visits and see which pages people arrive on, but only if you allow it when the site asks. Neither loads until you do. The cookie policy lists everything each part of Verb stores.

None of it is in the product. Neither tool runs in the Verb widget, so nothing about your users or their conversations reaches Google or anybody else. The assistant your customers use is not measured by this.

Where it runs

Our servers, in one region, with tenant isolation enforced by the database rather than by application code. Model requests go to an inference provider; conversation content is sent to produce a reply and is not used to train anything.

Deleting things

Ask and we will delete your organisation and everything under it, or everything about one of your users, identified by the user ID your backend puts in their token. Email vishnu.ps@askverb.com.