GDPR and BuddyCRM
Draft of 19 November 2026, for review. Highlighted text needs confirming before this replaces the current page. This draft covers both the new BuddyCRM and legacy BuddyCRM.
In short
The data in your BuddyCRM belongs to you. You are the data controller; we are your data processor. We store it in the UK, we use it only to provide the service, and the contractual commitments the UK GDPR requires of a processor are built into the data protection schedule of our Subscription Terms, so you do not need to negotiate a separate agreement.
The law in the United Kingdom is the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018. Customers in the EU are covered by the EU GDPR, which makes the same demands. This page explains how we meet them. It is information, not legal advice; responsibility for your own compliance stays with you as controller, and this page does not replace the terms of our contract.
What we process, and why
We process only the data you and your team put into BuddyCRM, or connect to it: your accounts, contacts and leads, the activities, quotes, cases, emails and documents linked to them, and the sales and product data fed from your ERP or accounts system. The purpose is the one you have engaged us for: running your sales, support and marketing. We do not use your data for any purpose of our own, we do not use it to train AI models, and we do not share it with anyone except the sub-processors listed below.
Typically this is ordinary business contact data: names, job titles, work email addresses and phone numbers, company details and the history of your dealings with them. BuddyCRM is not designed to hold special category data (health, ethnicity, politics, religion, union membership, sexual orientation, biometrics or criminal records). If you choose to store any, you are responsible for having a lawful basis for it.
You will need a record of processing activities of your own. A starting point for the BuddyCRM part of it is on the record of processing at the foot of this page.
Where your data lives
New BuddyCRM (app.buddycrm.com)
- Application and database: London. The service runs on Fly.io in its London region, with a managed PostgreSQL database in the same region. Each customer's rows are isolated by row-level security enforced inside the database itself, not only in the application.
- Files: UK. Attachments, imported documents and exports are kept in object storage in a UK bucket, encrypted at rest.
- Backups: UK. The database platform keeps rolling backups for ten days. In addition, every night a full export is written to a separate backup store with a different provider, in the UK, kept for 90 days. Confirm the off-site backup provider chosen (Backblaze B2, Cloudflare R2 or AWS London) and that its bucket encryption and object lock are on.
- A United States option. Customers in North America can have their database and files held in a US region instead. A customer's data lives in one region only; it is never copied between them.
Legacy BuddyCRM (login.buddycrm.com)
- Hosted in UK data centres with 24-hour security, with the database replicated to Microsoft Azure in the UK for disaster recovery. Confirm the legacy hosting is unchanged.
- Backed up daily and held for seven days in more than one location.
None of your data is stored outside the UK (or the US region, if you chose it). Our engineers are in the UK. If a provider outside the UK ever needs access, for example when we raise a support ticket with them, it happens under the transfer safeguards described below.
Sub-processors
These are the companies that handle customer data on our behalf. We will give you at least 30 days' notice before adding or replacing one, by email to your primary contact, so that you can object. Several are used only if you connect the service concerned: those are marked.
| Provider | What for | Where |
|---|---|---|
| Fly.io, Inc. | Hosting the application and the managed database (new BuddyCRM) | London data centre; US company |
| Tigris Data, Inc. | File storage (new BuddyCRM) | UK bucket; US company confirm the bucket is pinned to a UK region |
| Off-site backup provider | Nightly database backups (new BuddyCRM) | UK |
| Twilio SendGrid | Sending the emails BuddyCRM sends for you: campaigns, acknowledgements, notifications | United States |
| Anthropic, PBC | The AI features described below. Only for customers who switch them on | United States |
| Microsoft | Mailbox and calendar sync, and sign-in with Microsoft. Only if you connect them; the data stays in your own Microsoft 365 tenant | Your tenant's region |
| Gmail and Google Calendar sync, and sign-in with Google. Only if you connect them | Your Google Workspace region | |
| Meta Platforms | WhatsApp Business Platform, for WhatsApp cases and templates. Only if you connect it | United States and EU |
| Legacy BuddyCRM hosting name the provider | Hosting legacy BuddyCRM | United Kingdom |
| Microsoft Azure | Disaster recovery copy of legacy BuddyCRM | United Kingdom |
Your ERP and accounts systems (Epicor Prophet 21, Xero, QuickBooks Online), Mailchimp, Companies House and any system you feed data from or to are your providers, under your own contracts: BuddyCRM reads from and writes to them with the credentials you give it, and they are not our sub-processors. GitHub holds our source code, never your data.
The AI features
Several features of the new BuddyCRM use a large language model, Claude, run by Anthropic. Each is off until your administrator switches it on, and you can see exactly what each one sends:
- Ask sends your question and the figures that answer it.
- Agents send the account's recent history and the signals that fired, to draft the chasing email a person then approves, edits or discards.
- Email signals (off by default, separately from mailbox sync) send the emails already logged against a customer, in batches per account, to look for buying signals. Every signal quotes the sentence it came from; nothing is read from a mailbox that was not already matched to a customer.
- Business card, order and quote scanning send the photograph to be transcribed. The model only reads the text; matching to your products is done by BuddyCRM against your catalogue.
- Tender evaluation sends the tender document.
- Help sends your question about how to use the product.
Anthropic processes this data in the United States under its commercial terms. It does not use data sent through its API to train its models. Anthropic's standard commercial retention is 30 days for trust-and-safety purposes; confirm, or confirm zero-data-retention has been agreed, before this goes live. No AI feature acts on its own: every draft, signal and scan is shown to a person in your team before anything is sent or saved.
Security
The measures below are what we do today. They are listed for information and do not replace the terms of our contract.
New BuddyCRM
- All traffic is encrypted in transit (HTTPS only). Databases, volumes and file storage are encrypted at rest.
- Every customer's data is separated by row-level security in PostgreSQL, so a query cannot reach another customer's rows even if the application made a mistake.
- Passwords are stored as salted hashes. Two-factor authentication (authenticator app) is available to every user and can be made compulsory for a whole company. Sign-in with Microsoft or Google is available, and is bound to the verified identity, not to an editable email field.
- Sessions are held in HttpOnly, SameSite cookies, so they cannot be read by scripts or used from another site.
- Tokens for connected mailboxes and calendars are encrypted with a key held separately from the database. Connecting a mailbox is refused if that key is not configured.
- API keys are issued per customer and stored only as hashes. Access can be revoked at any time.
- An audit log records who changed what, exportable by your administrators.
- Secrets are held in the platform's secret store, never in code. Every change to the software is reviewed and deployed through a CI pipeline from source control; nothing is deployed by hand.
- Access to production is limited to named engineers in the UK. All staff are bound by confidentiality and trained in data protection.
- Reports and business intelligence copies exclude password hashes, two-factor secrets, API keys and connected-service credentials by construction.
Legacy BuddyCRM
- Passwords stored as hashes; UK data centres with 99.9% availability, 24-hour manned security, CCTV, card and biometric access control; multi-tenant infrastructure with multiple web servers and active/passive SQL databases; replication to Microsoft Azure for disaster recovery; firewalls tested by a CREST-approved security team; infrastructure access restricted to BuddyCRM offices.
The old page said we had "committed to starting the process of becoming ISO 27001 accredited". Confirm the current position, or leave it out.
Retention and deletion
- While you are a customer. When a user deletes an account, lead or contact, it is soft-deleted: hidden, with everything that hangs off it, and restorable by your administrator. Soft-deleted records are permanently removed after two years (the current rule), or sooner on request. Decide whether the new product should keep the two-year rule or shorten it; 12 months would be more usual.
- Data you send our support team, such as import files, is deleted two years after it was last used.
- When you leave. You can export your data yourself at any time (Excel export of records, reports and the API). At the end of a subscription we give you a full export on request, and we delete your data from the live system within 30 days of termination. Backups age out within 90 days after that, at which point no copy remains.
- Mailbox sync. Disconnecting a mailbox revokes the token immediately. Emails already logged against customer records stay, because they are part of the customer history, until you delete them.
If something goes wrong
We monitor for intrusion and failed sign-ins and treat any suspected breach as a major incident. If we confirm a breach that affects your data we will tell your primary contact within 24 hours of confirming it, with what we know about which records were involved, and keep you updated as the investigation continues, so that you can meet your own 72-hour duty to notify the ICO. We will also record the incident and what we changed as a result.
How we help you comply
- Subject access and erasure. Search finds every record that mentions a person; you can export it or delete it yourself. Where you need our help with an occasional request, support will assist as part of the service. Regular or large-scale requests can be supported on a chargeable basis, agreed with your account manager.
- Consent and preferences. Contact records carry marketing preferences and custom fields of your choosing, and those preferences travel with the contact into campaigns and to Mailchimp if you use it.
- Audit trail. Who changed what, when, available to your administrators.
- Access control. Roles, compulsory two-factor authentication, single sign-on, and API keys you can revoke.
- Processor terms. Already in the data protection schedule of the Subscription Terms: processing on your instructions only, confidentiality, security measures, sub-processor approval, assistance with your obligations, return or deletion at the end, and audit rights.
Who to contact
We are not required to appoint a Data Protection Officer, but all our staff are trained in data protection and the person responsible for it is name and role to confirm; the old page said the Chief Technical Officer. Email info@buddycrm.com or call 0121 288 0808.
Record of processing: the BuddyCRM part
A starting point for your own record of processing activities. What else goes in it depends on how you have set BuddyCRM up.
| Purpose | Data subjects | Data | Processor |
|---|---|---|---|
| Managing customer and prospect relationships: the record of accounts, contacts, dealings and contact preferences | Your customers, prospects and suppliers, and their staff | Name, job title, company, work email, phone, address, history of contact, preferences | Sense 6 Software Limited and the sub-processors above |
| Email, calendar and WhatsApp communication logged against those records | As above | The messages and appointments matched to a customer | As above, plus Microsoft, Google or Meta where connected |
| Marketing campaigns and journeys | Contacts who have consented or are business contacts | Name, email, preferences, engagement | As above, plus Twilio SendGrid; Mailchimp if you use it |
| Sales and product data from your ERP or accounts system | Usually companies rather than people; sole traders where applicable | Orders, invoices, prices, margins | As above |
| AI assistance (if switched on) | As for the feature used | The data each feature sends, listed above | As above, plus Anthropic |