Privacy Policy

Who this covers

Two kinds of people meet Dialhop: the businesses that use it and the people who call them. If you run a business on Dialhop, you give us your account and your business's details, and the receptionist handles your callers for you. If you called a business that uses Dialhop, that business chose the receptionist and is responsible for your call; we handle it on its behalf, so to ask about your information, contact the business you called.

What we keep about your account and business

• Your name, email address, and password (stored hashed), or the Google or Microsoft account you sign in with.
• When you signed in, from which IP address and browser.
• Your business: its name, phone number, address, time zone, kind, hours and services, greeting, the number a caller is transferred to, and the email that gets messages.
• The knowledge you give the receptionist: text you write, the text of files you upload (PDF, Word, or plain text), and the public pages of a website you ask it to read. We keep that text, in short passages with a numeric index so the receptionist finds the right one; the uploaded file itself is not stored.
• Feedback and integration requests you send, with the page you were on, filed in our development tracker without your name or email.

What we keep about calls

When the receptionist answers a call, it keeps what the business needs to act on it:

• The caller's number, when it is shown, and when the call started and how long it lasted.
• A transcript of the call and a two-line summary.
• Messages a caller leaves: their name, the number to call back, what it is about, and the message.
• Appointments booked: the caller's name and number, the service, the time, and any detail the business keeps, such as the car.
• A customer record for each person who gives their name: their name, numbers, the details they mention, and the language they spoke.

Telnyx, our telephony provider, carries and transcribes the calls and keeps its own record of the conversation under its policy. Dialhop does not store call recordings today; if that changes, this page will say so first. A business is responsible for telling its callers about the receptionist and the transcription where its state's law requires it.

Your Google Calendar

You can connect a Google Calendar from Integrations. Dialhop asks Google for your email address, the list of calendars you own, and access to the events on the calendars you own. You can disconnect at any time, and Dialhop then gives its access back.

Dialhop uses that access for one thing: booking. Before offering a caller a time, it reads the events on the calendar you picked for the days in question, looking only at when each starts and ends, whether it is marked busy, and whether you declined it. It does not read titles, descriptions, or guests, and it does not keep the events. After booking, it adds an event with the appointment's details, and later checks that event so the appointment moves or is cancelled when you move or delete it.

The tokens Google gives us are stored encrypted. We keep the email of the connected account, the name of the calendar you picked, and the id of each event Dialhop created. Nothing from your calendar is used to train models, shown in ads, or shared with anyone else. You can also remove Dialhop's access from your Google Account at myaccount.google.com/permissions.

Dialhop's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How we use what we keep

We use it to run the service for you, and for nothing else:

• To answer calls in your business's name from the knowledge you gave it, book appointments, take messages, and transfer calls.
• To show you every call, message, appointment, and customer in your dashboard, and to email you a message when you asked for that.
• To answer your questions in Eli, the dashboard's assistant, from your own business's data; those conversations are not stored.
• To keep the service working and safe.

We do not sell your information, use it for advertising, or train models on it.

Who handles it for us

Dialhop runs on services that process data on our behalf, under terms that limit them to that: Vercel hosts the app and routes requests to the language models through its AI Gateway; Neon stores the database, in the United States; Telnyx carries the calls, transcribes them, and gives the receptionist its voice; OpenAI models, through the Vercel AI Gateway, write the receptionist's and Eli's answers, summarize calls, and index the knowledge; Resend sends email; Google provides Calendar when you connect it, sign-in when you choose it, and address suggestions when you type an address; Microsoft provides sign-in when you choose it; GitHub holds the feedback and integration requests you send, as issues.

We also share information when the law requires it, or to protect the service and the people on it.

How long we keep it

Everything is kept while your account is open, except that Google Calendar tokens are deleted and revoked when you disconnect, a knowledge source you remove goes with its text and passages, and sessions expire on their own.

To delete your account and everything in it, write to alex@candoa.app from your account's email. We remove it within 30 days, except what the law makes us keep.

Security

Everything travels over TLS. Passwords are stored hashed and checked against known breaches before they are accepted. Google tokens are encrypted at rest.

Children

Dialhop is for businesses and the adults who run them, not for anyone under 18, and we do not knowingly keep their information.

Changes and contact

When this policy changes, the date at the top changes with it, and a change that matters is announced in the dashboard before it takes effect. Candoa LLC makes Dialhop; write to alex@candoa.app with any question or request about your information.