Data Processing Agreement
This agreement sets out how Honeyguide processes personal data on behalf of each business that uses the service, as UK GDPR Article 28 requires. It is accepted at sign-up and needs no separate signature.
1. Parties and acceptance
This Data Processing Agreement (the "DPA") forms part of the Honeyguide Terms of Service and is entered into between:
- Honeyguide — Honeyguide Ltd (formerly BeamPay Ltd), registered in England and Wales (company no. 16903978) at 128 City Road, London EC1V 2NX (the "Processor"); and
- the Customer — the business or sole trader that creates a Honeyguide account or confirms a Honeyguide record (the "Controller").
The Customer accepts this DPA by ticking the acceptance box on the sign-up form or by confirming its record with Honeyguide. Honeyguide records the date, time and version accepted. If the Customer later disagrees with a change to this DPA, they may close their account and the data will be deleted as described in section 3.9.
This DPA applies for as long as the Customer has a Honeyguide account and until all personal data has been deleted or returned. It is governed by the laws of England and Wales. Terms such as "personal data", "controller", "processor", "data subject" and "processing" have the meanings given in the UK GDPR and the Data Protection Act 2018.
2. What Honeyguide processes, and why
Honeyguide processes personal data only to provide the service described in the Terms: building a record of the Customer's business from the information and sources the Customer provides, checking it with the Customer, publishing it on honey-guide.uk, serving it to AI assistants when their users ask about local services, recording taps on the links in it, and, where the Customer connects Instagram or Google Business Profile, keeping those channels in line with the record. The Customer decides what the record contains; Honeyguide does not use the data for any purpose of its own.
| Item | Detail |
|---|---|
| Subject matter | The Customer's business record and the sources it was built from; taps on the record's links; where Instagram is connected, customer messages and the assistant's replies |
| Duration | The life of the Customer's account, plus the deletion period in section 3.9 |
| Nature of processing | Receiving and storing sources; drafting the record with an AI model; publishing it; serving it to AI assistant providers on request; counting and attributing link taps; producing reports for the Customer |
| Purpose | Making the Customer's business accurately findable by AI assistants and their users, and showing the Customer the result |
| Data subjects | The Customer and the people the Customer names in its record (owners, practitioners, staff); people who tap links (not identified); where Instagram is connected, the Customer's customers who message the business |
| Categories of personal data | Names, roles, professional titles, qualifications and languages of people named in the record; the Customer's contact details; anonymous link-tap events; where Instagram is connected, message content, handles and booking details |
| Special category data | Not intended. A Customer's record may describe medical or aesthetic treatments the business offers, which is information about the business, not about a person. Customers may volunteer health details in an Instagram message; the assistant is designed to hand such messages to the Customer rather than act on them, and Honeyguide stores them only as part of the message history |
| Location of processing | United Kingdom and the European Economic Area, except as listed for sub-processors in Annex A |
The Customer remains the controller of this data. Honeyguide acts only as the Customer's processor. AI assistant providers that receive published records are independent controllers of what they show their users.
3. Honeyguide's obligations as processor
Honeyguide will:
- Act only on instructions. Process personal data only on the Customer's documented instructions, which are the Terms, this DPA, the record the Customer confirmed and the settings the Customer chooses in the product. If UK law requires Honeyguide to process data otherwise, Honeyguide will tell the Customer first unless the law forbids it. If Honeyguide believes an instruction breaks data protection law, it will say so.
- Keep it confidential. Make sure everyone who works on the data for Honeyguide is bound by confidentiality and has access only to what they need.
- Keep it secure. Apply the technical and organisational measures in Annex B, and keep them appropriate to the risk as the service develops.
- Use only approved sub-processors. Use the sub-processors listed in Annex A. Honeyguide will give the Customer at least 30 days' notice by email before adding or replacing one. If the Customer objects on reasonable data protection grounds and the parties cannot resolve it, the Customer may close their account without penalty. Honeyguide stays responsible for its sub-processors.
- Not train models on the Customer's data. Not use the Customer's personal data to train or improve AI models for use by other customers, and ensure sub-processors do not either.
- Help with people's rights. Tell the Customer within 5 working days if Honeyguide receives a request from a data subject (for access, correction, deletion or objection), and help the Customer respond within the legal deadline.
- Help with security and compliance. Give the Customer the information they reasonably need for data protection impact assessments or dealings with the ICO, taking into account the nature of the processing.
- Report breaches. Tell the Customer without undue delay, and in any case within 48 hours of becoming aware, of a personal data breach affecting their data, with the information the Customer needs to notify the ICO within 72 hours.
- Delete when it ends. Within 30 days of the account closing, delete all of the Customer's personal data from live systems, and from backups within a further 60 days, unless UK law requires it to be kept. Before deletion the Customer may export their data from the product.
- Allow audits. Make available the information needed to show compliance with Article 28, and allow an audit by the Customer or an auditor the Customer appoints, no more than once a year on 30 days' notice, at the Customer's cost, in a way that does not disclose other customers' data.
- Keep data in the UK and EEA, and transfer it elsewhere only with a lawful transfer mechanism such as the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses, as recorded in Annex A.
4. The Customer's obligations as controller
The Customer is responsible for deciding why and how their customers' data is used, and for the lawfulness of that use. In particular the Customer will:
- Have a lawful basis for the processing Honeyguide carries out on their behalf. For publishing the names, roles and qualifications of the people who provide its services this is normally the Customer's legitimate interest in running the business, with those people informed; for replying to enquiries, where Instagram is connected, it is the steps needed before a contract with the customer.
- Tell each person named in the record that Honeyguide publishes their name, role, qualifications and languages, using the notice in Annex C, and, if Instagram is connected, tell customers that an AI assistant handles messages, using the second notice in Annex C.
- Give Honeyguide only instructions that comply with data protection law, and use the product's settings to limit what the assistant may do (for example which people and which details appear in the record).
- Keep their own account secure: protect their login, and connect only social media and business accounts they are authorised to connect.
- Respond to their customers' rights requests, with Honeyguide's help under section 3.6.
- Be registered with the ICO where required (most UK businesses that process customer data must pay the data protection fee).
Each party is liable for its own breaches of data protection law. Neither party excludes liability for anything that cannot be excluded by law; otherwise the liability caps in the Terms of Service apply to this DPA.
Annex A — Approved sub-processors
Honeyguide uses these providers to deliver the service. Customers are emailed 30 days before any change to this list.
| Sub-processor | What it does | Data it handles | Location | Transfer mechanism |
|---|---|---|---|---|
| Microsoft Ireland Operations Ltd (Azure, Microsoft 365) | Hosting, database and storage for records and source documents; email and support correspondence with the Customer | All Customer data; Customer contact details and support emails | Sweden Central (EU); Microsoft 365 data in the UK/EU | Within the UK/EEA; Microsoft Products and Services DPA |
| Cloudflare, Inc. | Website hosting, the connector through which AI assistants read published records, and the links that record taps | Published records; link-tap events; web traffic data | EU and global edge network | UK IDTA / UK Addendum to SCCs |
| Anthropic, PBC | AI model that drafts a record from the sources the Customer provides; the draft is checked with the Customer before publication | Source pages and documents the Customer supplies, which may name staff | United States | UK Addendum to SCCs under Anthropic's Commercial Terms; prompts not used for training |
| OpenAI, Google, Anthropic, Perplexity and other AI assistant providers | Independent recipients, not sub-processors: they receive published records when their users ask, under their own terms | Published records only | Various | Public data served on request |
| Meta Platforms Ireland Ltd (only if the Customer connects Instagram) | Instagram messaging and profile API | Messages, comments, handles, profile data | Ireland / EU, with transfers to the US under Meta's own terms | EU–US Data Privacy Framework and SCCs, under Meta's Platform Terms |
| Google Ireland Ltd (only if the Customer grants Business Profile access) | Google Business Profile API | Profile details, hours, services, performance data | Ireland / EU, with transfers to the US under Google's terms | EU–US Data Privacy Framework and SCCs, under Google's API terms |
Annex B — Security measures
Honeyguide applies the following measures and reviews them at least once a year:
- Encryption: all data encrypted in transit (TLS 1.2 or higher) and at rest using the cloud provider's managed encryption.
- Access control: access to Customer data limited to named Honeyguide staff who need it, protected by multi-factor authentication, with access logged and reviewed. Customers' Instagram and Google connections use OAuth tokens that can be revoked by the Customer at any time; Honeyguide never holds the Customer's passwords.
- Separation: each Customer's data is logically separated from other customers' data.
- Data minimisation: the registry stores only the record the Customer confirmed, the sources it came from (deleted after 180 days) and link-tap events with no personal identifiers; AI model calls are not used to train models, and model providers are contractually bound not to retain prompts beyond abuse monitoring.
- Backups and resilience: daily encrypted backups held within the EEA, with tested restore procedures.
- Vulnerability management: dependencies and infrastructure kept patched; security updates applied promptly; an annual review of the application's security.
- Incident response: a written procedure for detecting, containing and reporting breaches within the timescales in section 3.8.
- Staff: confidentiality obligations and data protection training for everyone with access to Customer data.
- Deletion: data deleted on account closure as described in section 3.9, with secure disposal of storage.
Annex C — Notices
For people named in the record. The Customer should give this to each owner, practitioner or staff member it names:
Our business is listed on Honeyguide (honey-guide.uk), a registry that AI assistants such as ChatGPT and Gemini use to answer questions about local services. Your name, role, qualifications and the languages you speak appear in our listing so that customers know who provides each service. Honeyguide Ltd publishes this on our instructions; if you would like anything changed or removed, tell us, or email hello@honey-guide.uk.
For customers, if Instagram is connected. The Customer can paste this into an Instagram bio, pinned post or first reply:
Messages to this account are answered with help from Honeyguide, an AI assistant that works for me. Honeyguide only reads messages sent to this business and replies on my behalf; I see every conversation and can step in at any time. Your messages are stored securely in the UK/EU and are not used to train AI. Questions about your data, or want a human straight away? Just say so in a message.