DavbySign in

Privacy policy

Effective November 12, 2026

Davby is an online scheduling service. It lets professionals (“hosts”) share a booking page, and lets the people they meet (“clients”) book time with them. This policy explains what information Davby collects, how it's used and shared, and the choices you have. Davby is operated by Bennett Liu in the United States. Questions go to support@davby.com.

Information we collect

From hosts

  • Account details: your email address, and anything you add to your profile, such as your name, firm, website, phone number and photo.
  • Your settings: meeting types, working hours, booking rules and the text of your emails.
  • Connections: if you connect Google Calendar, Microsoft, Zoom, HubSpot, Salesforce or Slack, we store the access tokens those services give us, encrypted. For Slack, that includes the address of the channel you chose (a webhook), also encrypted.
  • API keys: if you make a key for Zapier, we store only a fingerprint of it (a hash), its first few characters so you can tell keys apart, and when it was last used, plus the Zapier addresses your Zaps asked us to send bookings to.
  • Calendar information: for the calendars you choose to check, the start and end times, busy or free status and titles of events, as described below.

From clients who book

  • Your name, email address, time zone and preferred language, and anything else the host asks for, such as a phone number, answers to questions, or guests' email addresses.

Automatically

  • A single cookie that keeps hosts signed in. We don't use advertising or tracking cookies.
  • Basic technical information, such as IP addresses, used briefly to limit abuse and keep the service secure.

How we use Google user data

If you connect Google Calendar, Davby asks for these permissions, and uses them only for the features described:

  • View and edit events on your calendars (calendar.events): to find when you're busy on the calendars you choose, so clients are only offered times you're free; to check again at the moment someone books; to add each booking to the calendar you choose, with a Google Meet link if you selected one; to update or remove that event when the booking is moved or cancelled; and to notice when you move or delete an event Davby created, so the booking stays in step.
  • See the list of your calendars (calendar.calendarlist.readonly): so you can choose which calendars to check for conflicts and which one gets new bookings.
  • Your email address and basic profile (openid, email): to sign you in, if you choose to sign in with Google.

We store event times and titles for the calendars you choose to check, for roughly the next four months, so we can show you why a time isn't offered. Only you see them. Clients never see your event titles or details, only which times are open. We refresh this information regularly and replace it each time.

Davby'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.

Specifically, we use Google user data only to provide and improve the features you use in Davby. We don't sell it, use it for advertising, use it to determine credit-worthiness or for lending, or transfer it to anyone except as needed to provide the service, for security, or to comply with law. We don't use Google user data to develop, improve or train generalized artificial intelligence or machine learning models. No person reads your Google data unless you ask us to (for example, for support), it's needed for security or to investigate abuse, or the law requires it.

How we use Microsoft data

If you connect a Microsoft account (Outlook or Microsoft 365), Davby asks for these permissions, and uses them only for the features described:

  • Read and write your calendars (Calendars.ReadWrite): to find when you're busy on the calendars you choose, to add each booking to the calendar you choose (with a Microsoft Teams link if you selected Teams), and to update or remove that event when the booking changes.
  • Your basic profile and email (User.Read, openid, email): to know which account you connected, and to sign you in if you choose to.
  • Stay connected (offline_access): so bookings keep reaching your calendar when you're not signed in.

We don't read your email, files or contacts. We don't sell Microsoft data, use it for advertising, or use it to train AI models. Disconnecting in Settings, or removing Davby at myapps.microsoft.com (work or school) or account.live.com (personal), stops our access, and disconnecting deletes the tokens and calendar information we stored.

How we use Zoom data

If you connect Zoom, Davby uses it only to make a Zoom meeting for each booking that uses Zoom:

  • Create, update and delete meetings: a new meeting when someone books, changed when the booking moves, and deleted when it's cancelled. The meeting link goes in the confirmation, the calendar invite and the reminders.
  • Your Zoom user ID and email: to know which Zoom account you connected.

We don't access your recordings, chats, contacts or other meetings. We store your Zoom tokens encrypted, and the ID and link of each meeting we made. If you remove Davby from your Zoom account (in the Zoom App Marketplace, under Manage, Added apps), Zoom tells us and we delete your Zoom tokens straight away. Meetings already made stay on your Zoom account; you can delete them in Zoom.

How we use HubSpot data

If you connect HubSpot, Davby asks for these permissions, and uses them only to log your bookings there:

  • Read and write contacts (crm.objects.contacts.read, crm.objects.contacts.write): to find the client's contact by email, or create it, with their name and phone number; and to log a meeting on that contact for each booking (HubSpot's meetings are covered by these permissions). Moving a booking updates the meeting's time; cancelling marks it Canceled. Nothing is deleted.
  • Who connected (oauth): HubSpot's account ID and the email of the person who connected it, so Settings can show which account is connected.

HubSpot receives, for each booking: the client's name, email and phone number, the meeting type, the time, the location or video link, guests' email addresses, the client's comment and answers, and a link to the booking in Davby. We store the IDs of the contact and meeting we made, and nothing else from HubSpot. We don't read your deals, emails or other records.

How we use Salesforce data

If you connect Salesforce, Davby asks for these permissions, and uses them only to log your bookings there:

  • Access your data through the API (api): to find a Contact, or an open Lead, with the client's email, to create a Lead when there isn't one (name, email, phone, and the email's domain as the company), and to add an Event for each booking. Moving a booking updates the Event; cancelling renames it “Cancelled: …” so your activity history stays complete. We also read your own user record's email, to show which account is connected.
  • Stay connected (refresh_token): so bookings keep reaching Salesforce when you're not signed in.

The Event carries the same details HubSpot gets (above). We store the IDs of the Lead or Contact and the Event we wrote, and nothing else from Salesforce. We don't read your opportunities, accounts or other records.

How we use Slack

If you connect Slack, Davby asks only to post to one channel you choose (incoming-webhook). It posts a short message when someone books, moves or cancels: the client's name, the meeting type, the time in your time zone and a link to the booking in Davby, which only you can open. You can choose which of the three it posts about. We can't read anything in your Slack, and everyone in that channel can see the messages, so choose a channel accordingly.

How we use Zapier

If you make an API key and use it in Zapier, your Zaps can receive your bookings when they're made, moved or cancelled: the booking's ID, status, meeting type, times and time zones, the client's name, email and phone number, guests, location or video link, the client's answers and comment, the cancellation reason, and links to manage the booking. What happens next is up to the Zaps you build, under Zapier's own terms and privacy policy. Revoking the key in Settings stops it straight away, along with every Zap using it.

How we use other information

  • To run the service: show booking pages, take and manage bookings, and send confirmations, reminders and updates to hosts, clients and guests.
  • To keep it secure and working: prevent abuse and double bookings, fix problems, and answer support requests.
  • To tell hosts about their account: for example, if a calendar disconnects.

We don't send marketing email to clients.

How information is shared

  • Between hosts and clients: a client's booking details go to the host they booked. A host's name, firm and contact details appear on their booking page and in emails.
  • Service providers that run Davby for us, under contracts that limit their use of the information: Amazon Web Services (hosting, database and email delivery).
  • Services you connect: Google, Microsoft or Zoom, to create and update events and meeting links you've asked for; HubSpot or Salesforce, to log your bookings as you've asked; Slack, to post about them in the channel you chose; and Zapier, to send them to the Zaps you made with your API key.
  • When required: to comply with law, enforce our terms, or protect anyone's rights or safety.

We don't sell personal information.

Security

Information travels over encrypted connections (HTTPS). Access tokens for every connected service are encrypted when stored, API keys are kept only as a hash, and each host's data is kept separate from everyone else's in our database. Access to production systems is limited to the operator. No system is perfectly secure, so please contact us at once if you suspect a problem.

Keeping and deleting information

  • Disconnecting a calendar in Settings revokes Davby's access and deletes the tokens and calendar information stored from it. You can also remove access at any time from your Google Account permissions page.
  • Disconnecting HubSpot, Salesforce or Slack in Settings, Connections revokes Davby's access with that service and deletes the tokens (and the Slack channel address) and the IDs of records we made. Contacts, leads, meetings, events and messages already there stay; remove them there if you want. You can also uninstall Davby from HubSpot (Settings, Integrations, Connected apps), Salesforce (your personal settings, Connected Apps OAuth Usage, or your admin's setup) or Slack (the workspace's app management page).
  • Revoking an API key in Settings, Connections, Zapier stops it at once and deletes its Zap subscriptions.
  • Deleting your account in Settings revokes every connection and deletes your account, settings, bookings, connections and API keys right away. Copies in our backups are removed within 30 days.
  • Otherwise, we keep information for as long as the host's account is open.
  • Clients who want their information changed or removed can ask the host they booked with, or write to support@davby.com and we'll help.

You can download everything in your account at any time from Settings.

Your choices and rights

You can see and change your information in the app, download it, or delete it. Depending on where you live, you may have further rights, such as to ask for a copy of your information or to object to how it's used. Write to support@davby.com and we'll respond within 30 days.

Sensitive information

Davby isn't designed for health information, Social Security numbers, financial account numbers or tax documents. Please don't ask for them in booking questions or include them in bookings.

Children

Davby isn't meant for anyone under 16, and we don't knowingly collect their information.

Where information is stored

Davby stores information in the United States.

Changes to this policy

If we change this policy, we'll update the date above, and tell hosts by email before any change that affects how we use their information.

Contact

Bennett Liu, operator of Davby: support@davby.com