← Booki7

Privacy Notice

Version 1.9 · Effective 11 November 2026

1. Who we are

Booki7 ("Booki7", "we", "us") provides AI receptionist software to small businesses. Booki7 is a business name registered in Ireland (Registration of Business Names Act 1963, no. 789582) by Darren Morrissey, who trades under it as a sole trader. Our primary place of processing is in Ireland.

Data controller of this website and our marketing data: Darren Morrissey, trading as Booki7. Contact: admin@booki7.com. Our registered address is available on request and from the Companies Registration Office register at core.cro.ie.

2. Two types of data we handle

Please read carefully — different rules apply depending on which side you're on.

(a) You signed up for Booki7 ("Customer")

You are our customer. We are the controller of the data you give us when you sign up: your business name, your owner email, your billing details, and your account login. We process this to provide the service to you and to bill you. The legal basis is performance of our contract with you and our legitimate interest in operating the platform.

(b) You're a visitor chatting with a Booki7-powered widget on someone else's website ("Visitor")

The business whose website you're on is the controller of your conversation, your booking, and any contact details you share. Booki7 is their data processor — we host and run the AI on their behalf, but they decide what happens with your data. For requests about your data (access, correction, deletion), contact that business directly. They can ask us to action your request, and we will. If you can't reach them, email admin@booki7.com and we'll forward.

The same applies when you book through the booking form on a business's Booki7 page: the business is the controller of that booking. You give your name and an email address or a phone number, and nothing you type is sent until you press Book. The confirmation and the reminder go to your email; a phone number goes to the business, which may text you about the booking. We keep the booking and the page it was made on, as for any booking.

If you become their client, the business may also keep a record about you: notes it writes or dictates, tags, and short facts it remembers (for example a preference, or an allergy you mention in the chat). Section 3 lists this as "Client records", and section 8 explains how our AI reads it.

3. What data we process

CategoryExamplesPurposeLegal basis
Customer accountBusiness name, owner email, password / sign-in key, billing detailsRun your account, bill you, supportContract
Customer configurationBusiness hours, services, FAQ, knowledge base, brandingPower your AI receptionistContract
End-visitor conversation contentChat messages between visitor and your AIProvide the service to you (controller)Contract / legitimate interest of controller
End-visitor identityName, email, phone (when given to book or order)Process the booking or orderPerformance of pre-contract / consent (controller-determined)
End-visitor bookings & ordersBooking details (service, date, time); order details (items, quantity, personalisation notes, collection/delivery date, delivery address where delivery is chosen)Fulfil the booking or order for the business (controller)Performance of pre-contract / contract (controller-determined)
Client records kept by the businessNotes the business writes or dictates about a client (a dictated note is kept as text), tags, and the client card: short facts drawn from those notes and from the client's own chat messages, such as a preference, an allergy or a colour formula. A note may hold health details where the business records them.Let the business remember its clients; let the front desk take a returning client's preferences and any allergy or sensitivity into account; prepare the owner's notes before a visit and inform messages the business drafts to that client (controller)Determined by the business (controller); explicit consent where a record holds health details (see our Terms)
Technical telemetryIP address, user agent, page URL, session IDSecurity, abuse prevention, debuggingLegitimate interest
Visitor safety recordsA one-way hash of the IP address a chat connected from (we do not store the address itself for this purpose); blocks a business has set; reports of illegal content and the decisions taken on themLet a business stop someone abusing its chat, and let us act on reports of illegal contentLegitimate interest; legal obligation for reports and decisions
Push notificationsPush subscription endpointNotify owners of activityConsent
Audit log of platform-admin accessWho accessed what tenant data and whenAccountability (Art. 5(2) GDPR)Legal obligation

4. Where data is stored

Primary processing: Hetzner Online GmbH, a German company, in their Falkenstein, Germany data centre — inside the EU/EEA.

The application database (SQLite) is stored on the same server, reached only over TLS. It is readable only by the server's administrator account and the application itself, and its backups and the server logs only by the administrator account; they are not encrypted at rest. Backups are kept on the same server, in the same data centre.

Some processing is done by sub-processors located outside the EU/EEA. See Sub-processors for the list and the safeguards we apply.

5. How long we keep data

6. Your rights (data subjects in the EEA)

You have the right to:

Customers can exercise these rights themselves from Settings → Plan and privacy in the admin dashboard (export and erasure). End-visitors should contact the business they were chatting with.

We respond to requests within 30 days of receipt.

7. Cookies and similar technologies

The Booki7 widget stores a session identifier in your browser's localStorage so that you can return to a conversation. This is strictly necessary for the chat to work and is treated as functional under the ePrivacy Directive. It is not used for tracking across sites.

Our marketing website does not use third-party analytics or advertising cookies.

8. Automated decision-making and AI

Conversations are processed by large language models (Claude by Anthropic; the optional Voice call tier, where a business enables it, also uses OpenAI). The AI suggests booking times and answers questions; final booking decisions are reviewable by the business owner via the approval flow for out-of-hours requests. No solely-automated decision with legal or similarly significant effect is taken without the business owner's involvement.

Booki7 also drafts messages a business sends its own clients (appointment reminders, aftercare notes, check-ins). Where a business edits one of those drafts before sending, Booki7 keeps a copy of what it suggested alongside what the business actually sent, and uses those examples so later drafts match how that business writes. Client names are removed from those examples before they are stored, they are used only for that same business, and they are not used to train any AI model. A business can see exactly what has been kept, clear it, or switch the whole thing off under Settings → How my front desk talks.

Where a business owner records a voice note on a client's record, the short audio clip is converted to text by speech-to-text software running on Booki7's own server in the EU (Falkenstein, Germany). The audio is never sent to any third party and never leaves the EU: it is processed in memory, is not stored by Booki7, and is not used to train AI models. Only the resulting text is kept, within that client's record, and treated like any other note the business holds about its client, including being read by Claude as described next. No third-country transfer and no external sub-processor are involved in transcribing voice notes.

Client records are read by Claude (Anthropic, USA). The text of a business's notes about a client (typed, or transcribed from a voice note), its tags and the client card are sent to Claude to: keep the client card up to date each time a note is saved; let the front desk take a returning client's preferences and any allergy or sensitivity into account in its replies, without quoting them; write the short line the owner sees before that client's visit; and inform a reach-out message the business drafts to that client. The day's bookings (each client's name, the service and the time) are sent the same way to write the owner's daily note; the weekly and monthly summaries send counts only, no client details. Anthropic processes this as our sub-processor under standard contractual clauses and does not use it to train its models (see Sub-processors). The business decides what it records; health details should be recorded only where the business has the client's explicit consent.

AI-written text is marked. Under the EU AI Act, text written by Booki7's AI is marked so it can be recognised. Emails it writes (for example an aftercare note, or a message a business sends from an AI draft) carry a signed label in their technical headers saying they are AI-generated, when and as what kind of message; the label holds no name, address or other personal data. Chat replies are marked in the chat itself. Every sentence the AI writes is also recorded as a one-way fingerprint (never the text, never who it was for), kept for two years, so that anyone can check a message at /ai-check. That page does not keep what is pasted into it.

9. Security

TLS 1.2+ in transit, role-based access control inside the application (owner and team-member keys), audit logging of every platform-admin change and data export, signature-checked Meta and Stripe webhooks, scoped per-tenant keys stored only as one-way fingerprints, a separate revocable sign-in per device, email addresses and phone numbers masked in server logs, automatic nightly security updates.

Messages and photos sent through a chat are not automatically screened before they reach the business owner. Our Content Policy explains what isn't allowed, what a business owner can do about it, and how anyone can report illegal content to us.

10. Breach notification

If we discover a personal data breach, we will notify affected customers without undue delay and within 72 hours wherever feasible, in line with Art. 33 GDPR. Customers are responsible for onward notification to their end-visitors where required.

11. Requests from public authorities

We disclose personal data to a public authority only where we are legally required to do so. Every request is reviewed for a valid legal basis under Irish or EU law before anything is disclosed; a request that is overbroad, lacks a lawful basis, or falls outside our jurisdiction is challenged or refused. Where the data belongs to a business we process for, we notify that business before disclosing anything unless the law prohibits it. We disclose only the minimum data the request lawfully covers, and we keep a record of every request received and how it was handled. To date we have never received such a request.

12. Changes

We will notify customers by email of any material change at least 30 days before it takes effect. The current version and effective date are at the top of this page.

13. Contact

Email admin@booki7.com. We are not currently required to appoint a Data Protection Officer.