Privacy Policy
Last updated 10 November 2026
This policy explains what information HughBee collects, why, how long we keep it, who we share it with, and your rights. It’s written in plain language. If anything is unclear, email privacy@hughbee.com.
1. Who we are
HughBee is run by HUGHBEE LTD, a company registered in Northern Ireland (company number NI744753). Registered office: 77 Glenvale Park, Londonderry, BT48 0GB.
- Registered with the UK Information Commissioner’s Office (ICO): registration number ZC291479.
- Our representative in the European Union for data protection: email privacy@hughbee.com for their details.
- Contact for anything about your information: privacy@hughbee.com.
HughBee provides AI agents, including AI receptionists, that work for businesses and sole traders. An AI receptionist answers a business’s calls and messages, takes people’s details and arranges bookings on the business’s behalf.
2. Whose information this covers
This policy covers three groups of people.
- Business customers: the businesses that sign up to HughBee, including sole traders, and the people who run them.
- People who contact a business that uses HughBee: anyone who phones, messages or emails one of our business customers and reaches HughBee’s AI agents, or who is contacted about a booking. In this policy we call them end customers.
- Visitors to hughbee.com and my.hughbee.com.
Our role is different for each group, and that matters for your rights.
- For business customers and visitors, HughBee decides how information is used. In data protection law we are the controller.
- For end customers, the business you contacted decides how your information is used, and HughBee handles it on that business’s behalf under a written agreement. The business is the controller and HughBee is its processor. Section 4 explains what this means for you.
3. Business customers: what we collect and why
| What | Why | Legal basis |
|---|---|---|
| Name, business name, whether you’re a sole trader or a company (and your company number), where the business is based, business address, mobile number, email | To create and run your account, send you alerts, and contact you about the service | Contract |
| How you sign in (Google or an email link). With Google sign-in, we receive your name, email address and profile picture from Google | To let you sign in securely | Contract |
| Your settings: what your business offers, prices you allow the AI agents to give, areas, hours, booking rules, the AI agents’ name and voice, the pronouns they use for you, your greeting, instructions and facts | So the AI agents answer calls and messages and make bookings the way you want | Contract |
| Details for registering your phone number: for a sole trader, photo ID and proof of address; for a company, company details and a named contact. We pass these straight to our telecoms supplier and don’t keep copies once the number is approved | Telecoms rules require every number to be registered to whoever uses it | Legal obligation and contract |
| Bank details and VAT number, if you add them for your invoices | To show them on the invoices you send | Contract |
| Connections you make to Stripe, WhatsApp, Facebook, your calendar and other services: account IDs and access tokens (stored encrypted) | To work with the services you’ve connected | Contract |
| Your acceptance of our Terms of Service and Data Processing Agreement (which document, which version, when, your business name and email at the time) | To keep a record of our agreement with you | Legal obligation and legitimate interests (proof of agreement) |
| Your billing details when paid plans start, including your VAT number and the country your business is in. Card details are handled by Stripe, never stored by HughBee | To charge for the service and keep tax records | Contract and legal obligation |
| Messages to and from us (for example support emails), and suggestions you send with “Suggest an improvement” | To support you and improve HughBee | Contract and legitimate interests |
| Tips you mark as “OK to share” | To add them, without your business details, to the reference material every business’s AI agents use | Legitimate interests |
| Technical information: when you sign in, error reports | To keep the service secure and working | Legitimate interests |
Do you have to give us this information? We need the details in the first four rows to open your account and give you a phone number. Without them we can’t provide HughBee.
Emails from us. We email you about your account and the service. We may also tell you about new HughBee features; you can opt out of those at any time with the link in each email.
Alerts. Alerts about bookings and calls go to your mobile by WhatsApp, from HughBee’s own WhatsApp number, with a text if an urgent alert isn’t delivered.
4. End customers: people who contact a business that uses HughBee
When you phone, message or email a business that uses HughBee, you may be speaking or writing to an AI agent, an automated assistant. It always tells you this at the start. On calls it also tells you the call is transcribed and, if the business has recordings switched on, recorded.
What is collected: your name, phone number, email if you give it, what you need, the times that suit you, how you’d like to be contacted, and anything else the business needs for your booking. For a home visit, that includes your address and Eircode or postcode; for a restaurant, your party size and any requests. On calls, a written transcript and, if switched on, a recording. In messages, the messages themselves. Your phone number is captured when you call, even if you hang up early.
Health information: some businesses need it for your booking, for example an allergy when you book a table, or something relevant to a beauty treatment. It’s used only for that booking. The AI agent never tells you whether something is safe for you; the business does that.
Why: so the business can arrange and provide what you asked for, confirm your booking, remind you, take payment and send you an invoice.
Who decides: the business you contacted is responsible for your information. HughBee handles it for them, following their instructions and our Data Processing Agreement with them. If you want to see, correct or delete your information, contact the business. You can also contact us at privacy@hughbee.com and we’ll pass your request on and help them deal with it.
Texts and booking pages: texts about your booking come from the sender name “HughBee”, with the business’s name at the start. You can’t reply to them, so texts that need an answer include a link to your own booking page. The page shows only what’s needed for your booking (for a home visit, your first name, town and Eircode or postcode), and stops working a week after your booking.
Payments: if you pay a business by card, you pay on a secure page run by Stripe, for the business’s own Stripe account. Stripe handles your card details under its own privacy policy. HughBee never sees or stores them.
WhatsApp and Facebook Messenger: if you message a business on WhatsApp or Messenger, Meta also handles your messages under its own privacy policy.
Calendars: if the business has connected its Google Calendar, your booking details (your name, phone number, address, what the booking is for and the problem described) are added to that business’s calendar. Google holds them there under the business’s own agreement with Google.
What the AI agents don’t do: they don’t take card or bank details, give prices the business hasn’t set, or make decisions about you that have legal or similarly significant effects. They make bookings within the business’s own rules, and either the business or you can change or cancel them.
5. How we improve HughBee
To keep the AI agents working well, authorised HughBee staff may look at calls and messages when needed to support a business or fix a problem. We also remove names, phone numbers, addresses, Eircodes, postcodes and other identifying details from call records, and use what’s left to improve how the AI agents work for every business, and to produce statistics. We don’t use end customers’ information to train AI models, and one business’s customers’ details are never shared with another business. Call recordings are never used for this work. We keep de-identified records for up to 2 years. We do this on the basis of our legitimate interests in keeping HughBee working well and improving it.
6. Cookies and visitors to our websites
We only use essential cookies on hughbee.com and in the HughBee app (my.hughbee.com). We don’t use analytics, advertising or tracking cookies. If that changes, we’ll update this policy and ask for your consent first.
- Essential cookies keep you signed in, and remember what you’ve typed on the sign-up form for up to an hour while you confirm your email. The service can’t work without them, so they don’t need your consent.
The app uses Google Maps to look up addresses and show maps. Google receives your IP address and what you search for, under Google’s own privacy policy.
7. How long we keep information
| Information | How long |
|---|---|
| Call recordings, transcripts and summaries | 90 days, then deleted. Businesses can turn recordings off. |
| Booking, customer and job details, messages, and invoices a business sends its customers | While the business’s account is open, unless the business deletes them sooner. Deleted within 30 days of the account closing |
| Identity documents for phone number registration | Not kept once the number is approved |
| De-identified call records used to improve HughBee (section 5) | Up to 2 years |
| Business customer account information | While the account is open, then deleted within 30 days, except as below |
| HughBee’s own invoices and billing records | 6 years, as tax law requires |
| Records of acceptance of the Terms of Service and Data Processing Agreement | 6 years after the account closes, as proof of the agreement |
| Support emails and suggestions | 2 years |
| Backups | Deleted on a rolling basis within 30 days |
8. Who we share information with
We share information only with the companies that help us run HughBee (our “sub-processors”), and only what each needs. The full list, what each does and where, is in Annex 3 of our Data Processing Agreement at hughbee.com/dpa. In summary:
- Supabase: database and file storage, in Ireland (EU).
- Vercel: hosting the app, with servers in Dublin (EU).
- ElevenLabs: the AI agents’ voice on calls (speech recognition and speech).
- Anthropic: the AI model (Claude) during calls, and for summaries and written replies.
- Twilio: phone numbers, calls and text messages.
- Resend: sending and receiving emails.
- Meta: alerts to business customers by WhatsApp.
- Google: our own email.
- When those features are switched on: our task scheduler and Sentry (error reports).
Some companies receive information as controllers in their own right, under their own privacy policies:
- Google for address and place lookups and maps (Google Maps Platform), and for the calendar if a business connects it.
- Stripe, Meta (WhatsApp and Messenger) and other services a business connects to HughBee, under the business’s own agreement with them.
- Twilio, for the details needed to register phone numbers.
We don’t sell information, and we don’t use end customers’ information to advertise.
AI models: the AI model we use is Claude, from Anthropic, under Anthropic’s business terms, which don’t allow information sent through our account to be used to train its models. This covers calls too, because ElevenLabs connects to Claude through our own Anthropic account. We’ve also switched off ElevenLabs’ option to use our data to improve its own models. Your information isn’t used to train AI models.
Google information: HughBee’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.
Google Calendar. If a business connects its Google Calendar, HughBee asks Google for two permissions: to see when the business is busy, and to add and change calendar entries. We use them only for the business that connected, and only for the following.
When the business is busy: we check the busy times in the business’s main calendar, so the AI agents and the booking screens never offer a time that’s already taken. The AI agents are only told which times are free, never what’s in the calendar. We don’t keep the busy times.
The business’s own events: to show the business its whole day on the Bookings calendar in HughBee, we read the events in its main calendar for the dates it’s looking at: each event’s title (up to 120 characters), its start and end time, and whether it’s all day. Events marked private, and events with no title, show only as “Busy”. Cancelled events and events marked “free” are left out. Only that business sees them, and we don’t keep them.
Entries for bookings: we add an entry to the business’s main calendar for each booking in HughBee, including upcoming bookings already in HughBee when the calendar is connected. Each entry contains the customer’s name (or phone number), what the booking is for, the address, the problem described, the customer’s phone number and a link to the booking in HughBee. We move the entry when the booking moves and remove it when the booking is cancelled. We only ever change or delete entries HughBee added. We never change or delete the business’s own events.
What we store: the connection to Google (encrypted, in Ireland), the Google email address it belongs to, and the ID of each entry we added.
What we don’t do: we don’t sell calendar information, use it for advertising, use it to train AI models, or share it with anyone except the hosting providers that run HughBee (listed above). HughBee staff don’t read calendar information, except with the business’s permission to help with a support request, for security, or where the law requires it.
Disconnecting: a business can disconnect Google Calendar at any time in Settings, Connections, which also tells Google to end HughBee’s access. Closing a HughBee account removes HughBee’s upcoming entries from the calendar and ends the access.
We may also share information if the law requires it, to protect someone’s safety, or with a company that takes over HughBee (which would have to follow this policy).
9. Information that leaves the UK and EU
Our database and app servers are in Ireland. HughBee itself is in the UK; information from businesses and people in the EU reaches us under the European Commission’s adequacy decision for the UK. Some suppliers process information in the United States or elsewhere, for example ElevenLabs, Anthropic and Twilio during a call, and Resend for email records. When they do, we use the protections the law requires: the UK International Data Transfer Agreement or Addendum, the EU Standard Contractual Clauses, binding corporate rules, or an adequacy decision such as the EU-US Data Privacy Framework where the supplier is certified. We copy call recordings and transcripts to our own database and delete the suppliers’ copies as soon as practical.
10. Keeping information safe
All information is encrypted while it travels and while it’s stored. Each business can only ever see its own information, which is enforced in the database itself and tested. Access by HughBee staff is limited to what’s needed to run and support the service. Card details are never taken by the AI agents or stored by HughBee.
11. Your rights
You have the right to:
- ask for a copy of your information
- ask us to correct it
- ask us to delete it
- ask us to limit how we use it, or object to our using it
- ask for your information in a format you can take elsewhere
- withdraw consent, where we rely on consent
Email privacy@hughbee.com. We’ll reply within one month. If you’re an end customer, see section 4.
If you’re unhappy with how we’ve handled your information, you can complain to:
- the Information Commissioner’s Office (UK): ico.org.uk, 0303 123 1113
- the Data Protection Commission (Ireland): dataprotection.ie
We’d like the chance to sort it out first, so please contact us.
12. Children
Business accounts are only for people aged 18 or over. People of any age may contact a business that uses HughBee, and a parent may book for a child. That information is handled in the same way as anyone else’s, and the business is responsible for it.
13. Changes to this policy
We’ll update this policy when HughBee changes. The date at the top shows the latest version. If a change is significant, we’ll tell business customers by email or in the app before it takes effect.