Privacy Policy

What Digui collects when you try the demo, use your account, or call or chat with a receptionist built on Digui, why, who processes it for us, and what you can ask us to do with it.

Who we are

Digui (digui.ai) is run by [COMPANY LEGAL NAME], [POSTAL ADDRESS], [COUNTRY]. For the data of people who visit our site, try the demo or have an account, we decide how it's used: we're its controller.

For the people who call or chat with a business's receptionist, the business is the controller: it chooses to use Digui, decides what its receptionist says and does, and what happens with its callers' information. We process that data for the business, on its instructions, as its processor (or service provider).

Questions about this policy: [CONTACT EMAIL].

When you try the demo

The website you type. We read its public pages (the home page and up to 8 linked ones) to build a receptionist from them.
Your name, and your phone number if you give it. We keep them with the website, as a lead, to follow up with you about Digui, also when the website can't be read. They never go in the receptionist.
Your call. When you call in the browser, your microphone's audio goes straight to ElevenLabs, which understands what you say, answers in the receptionist's voice and keeps a transcript. The live captions use ElevenLabs' speech recognition too.
The receptionist itself: its name, website, colors, greetings and what it knows from the website. Anyone with its link can open it and call it.

When you have an account

Your sign-in: your email address, name and password, or your Google sign-in. Clerk runs the accounts for us; we keep the id Clerk gives your account.
Your plan and payments: Clerk Billing runs the checkout and Stripe processes your card. We never see or store your card number; we ask Clerk which plan you have.
Your receptionists: their settings, prompts, greetings, voices and pronunciations, and your business's phone number, which we check is yours with a code sent by text message or WhatsApp (Twilio Verify).
Your documents: what you write, what we read from a website you give us, and the files you upload (up to 10 MB each). We keep the file, and a text copy in ElevenLabs' knowledge base so your receptionists can search it during calls.
Your tools: the apps you connect, the name of each account you connected (often an email address), the instructions you write, the email addresses or phone numbers you list, and for a database, its address, its user and password (kept encrypted) and the query you write.
Your requests: when you ask us to build a tool, what you ask for and the email to reach you at.
Your usage: each call's length, the AI it used and what it cost, to show your minutes and bill you.

Callers and chat visitors of a business

When someone calls a business's receptionist, or chats with it on the business's website, the business decides what happens with their data: it's responsible for telling its callers, and for any consent its law requires. If you called a business and have a question about your data, ask the business; we'll help it answer.

What we process for the business:

The caller's phone number, which reaches us through Twilio and is given to the receptionist so it can use it, for example in a message or a booking.
What the caller says or types. It's processed live to understand them and answer, and a transcript and a summary of each call or chat are kept, which the business sees in its Logs. ElevenLabs may also keep the call's audio.
What the caller gives during the call (their name, email, the time they want, an order number) and what the receptionist does with it in the business's apps: booking in its calendar, Calendly or Square, emailing the addresses the business listed, looking up an order in its Shopify store, or transferring the call to a number the business listed.
Who a chat visitor is, when the business's website tells its chat (their customer ID in the business's system, for example), to look up their own records. We keep it for about a day.
The business's records its receptionist looks up in the business's database to answer (an order's status, an appointment): only what the business's query allows for that caller or visitor. They're processed and kept by ElevenLabs, in the conversation's transcript, which the business sees in its Logs, and the AI model reads them to answer. We never keep them in our own logs.

Your connected apps

When you connect an app, you sign in to it through Pipedream, which keeps the login (its access tokens); we keep only which account it is. Deleting the tool in Tools deletes its login too.

Your receptionists use each app only for what Digui's tools do:

Google Calendar and Outlook: see when your calendar is busy, and add events at free times. No one is invited.
Gmail: send emails, only to the addresses you list.
Calendly: see your event types and free times, and book callers into them. Calendly emails them the confirmation.
Square: see your services and free times, find or add a customer by phone number, and book them.
Shopify: look up products, prices and stock, and an order's status for a caller who gives its number and the email it was placed with.
Call transfer: no login. A phone call can only be moved to the numbers you list.
SQL database (PostgreSQL or MySQL): no Pipedream login. We keep its password encrypted, and your receptionists only run the query you write, to read, for the person they're talking to.

Why we use it

Only for these purposes. We don't sell personal data, and we don't use it for advertising.

To provide Digui: build and run your receptionists, answer calls and chats, and show your logs and usage. This is to perform our contract with you, or the business's with us.
To bill your plan and extra minutes, and keep the records the law requires.
To follow up about Digui with people who tried the demo, in our legitimate interest. You can object at any time.
To keep Digui safe and working: limits on how often anyone can build receptionists, call them, type codes on the phone line or get verification codes, and preventing abuse, in our legitimate interest.
To answer you when you write to us.

Who processes it for us

These providers, each only to provide its service to us:

Railway: hosts our website, our servers and our database.
Clerk: accounts, sign-in and billing, with Cloudflare's bot check when you sign up.
Stripe: card payments, inside Clerk's checkout.
ElevenLabs: runs calls and chats: speech recognition, the receptionist's voice, live captions, call transcripts and summaries, and the search index of your documents.
OpenAI: reads a website's text to write a receptionist, or a document, from it.
The AI model each receptionist answers with, through ElevenLabs: Anthropic's Claude by default, or OpenAI's GPT or Google's Gemini if you pick them. It gets the conversation, to write the replies.
Twilio: the phone line, call transfers, and verification codes by text message or WhatsApp.
Pipedream: keeps your connected apps' logins and passes your receptionists' requests to them.
The apps you connect (Google Calendar, Gmail, Outlook, Calendly, Shopify, Square) and your own database: they get what your receptionist sends them, under your own account with them.
Others only when the law requires it, to protect Digui and its users from fraud or abuse, or a buyer if Digui is sold or merged, under this policy.

How long we keep it

Demo leads (name, phone and website): [LEAD RETENTION PERIOD], or until you ask us to delete them.
Your account's data: while your account is open. When you delete a receptionist, a document or a tool, we delete it, with its copies at ElevenLabs and, for a tool, its login at Pipedream.
Call and chat records (transcripts and summaries, with the records looked up in them): [CALL RECORD RETENTION PERIOD].
Usage records (each call's length and cost): as long as we need them for billing and the law requires.
The IP addresses and phone numbers our limits count: about a day.

Deleting your account

To delete your account and everything in it, write to us at [CONTACT EMAIL]. Deleting your sign-in in Manage account doesn't delete your receptionists, documents or tools: ask us and we will.

Your rights

Wherever you live, you can ask us to:

Give you a copy of your data, and tell you how we use it.
Correct it, if it's wrong.
Delete it.
Stop using it, or use it only in some ways, including following up with you about Digui.
Send you the data you gave us in a common format.

How to use your rights

Write to [CONTACT EMAIL]. We may need to check it's you, and we answer within the time your law sets (one month under the GDPR, for example). If you called a business's receptionist, ask the business first: it decides about your data, and we'll help it answer.

In the European Economic Area, the UK and Switzerland, these are your rights under the GDPR, and you can also complain to your data protection authority.

In California and other US states with privacy laws, you have the right to know what we collect and how we use it, to correct and delete it, and not to be treated differently for asking. We don't sell or share personal data for cross-context behavioral advertising.

International transfers

Our providers may process data outside your country, including in the United States. When data from the European Economic Area, the UK or Switzerland goes to a country without an adequacy decision, we rely on safeguards such as the European Commission's Standard Contractual Clauses in our providers' data processing terms.

Cookies and local storage

We don't use analytics, advertising or tracking cookies. What the site keeps in your browser, which you can clear in its settings:

Clerk's cookies, which keep you signed in. Signing in needs them.
Stripe's, in Clerk's checkout, and Cloudflare's bot check on sign-up, which may store what they need to prevent fraud.
In your browser's local storage: the site's language you pick, and after the demo, your first name, so the receptionist you built greets you by it.

Children

Digui is for businesses, not for children. Accounts are for people 18 or older, and we don't knowingly collect children's data for ourselves. If you think a child gave us theirs, write to [CONTACT EMAIL] and we'll delete it.

Security

Digui only works over HTTPS, each account sees only its own receptionists, documents and calls, and the logins to your apps stay with Pipedream. No system is perfectly secure: if a breach affects your data, we'll tell you as the law requires.

Changes to this policy

When our practices change, we update this page and its date. If a change matters to you, we tell account holders by email or in the dashboard before it applies.

Contact

[COMPANY LEGAL NAME], [POSTAL ADDRESS], [COUNTRY]. Email: [CONTACT EMAIL].