Security and privacy
Follow a customer's message from the moment they open the chat to the moment you delete it, and see what protects it at every step. Where a promise is written into our DPA or policies, we link straight to it.
Last updated: 20 November 2026
At a glance
Step by step
Before anyone types, the chat says what it is, and can know who it's talking to.
const token = jwt.sign(
{ sub: user.id, aud: CHATBOT_ID,
email: user.email, name: user.name },
SIGNING_KEY,
{ algorithm: "HS256", expiresIn: "1h", keyid: KEY_ID }
);
// then pass the token to the chat widget
It travels encrypted, straight to our servers in the EU.
Including any screenshot, photo or file they attach.
From your knowledge, without ever learning from it.
Mostly in the EU, encrypted, and seen only by people who need to.
| Conversations and settings | EU (Ireland) · Heroku |
|---|---|
| Knowledge-base search index | EU (Ireland) · Pinecone |
| Images and files sent in website chat | EU, deleted within 30 days · Cloudflare R2 |
| Writing replies, reading images, building the search index | Worldwide, under SCCs · OpenAI |
| App logs | United States, under SCCs · Papertrail |
| Notification emails | Worldwide · Google Workspace |
Whenever you like. The moment you delete something, the AI loses access to it.
Around every step
Our hosting providers' data centres hold ISO 27001 and SOC 2 certifications.
If a breach affects your data, we email you without undue delay, and always within the time the law requires.
Files customers send are limited to 10 MB, checked for type, and served back in a sandbox.
The code libraries we use are checked automatically for known vulnerabilities.
Tell us at [email protected], with enough detail for us to reproduce it. We'll confirm we've got it and keep you updated while we fix it.
Compliance
We're your data processor. These documents set out exactly what that means.
Part of our Terms, so there's nothing to sign. Covers UK and EU GDPR, with the Standard Contractual Clauses and UK Addendum. Want it countersigned? Just ask.
Read the DPA →Every provider that handles your data, where, and how transfers are protected. We email you at least 10 days before any change.
See the list →How we handle personal data for our own purposes. Registered with the ICO under ZB810494.
Read the policy →The cookies our website uses, and how to choose which ones you allow.
Read the policy →FAQ
The questions buyers and security reviewers ask us most. Something missing? Email [email protected].
Your conversations, settings and your chatbot's knowledge-base search index are stored in the EU, in Ireland. Anything customers send in website chat, such as images and files, is kept in the EU for 30 days at most. Some processing happens outside the UK and EU: OpenAI writes the AI's replies and builds the search index, our application logs are kept in the United States, and notification emails go through Google Workspace. Our Subprocessors page lists every provider and how each transfer is protected.
Written in: Subprocessors page →No. We don't use your data to train any AI model, ours or a subprocessor's. The AI looks your content up when it answers, and loses access the moment you delete it. OpenAI doesn't train on data sent through its API. It may keep a request for up to 30 days to check for abuse, then deletes it.
Written in: DPA, section 7.2.3 →Yes. Every connection uses HTTPS, enforced with HSTS, and the data we store is encrypted with AES-256. The database is backed up daily, and the backups are encrypted and access-controlled.
Written in: DPA, Schedule 2 →Only people who need it to run the service and help you. Access is least-privilege, sign-in to production systems uses multi-factor authentication, and everyone is bound by confidentiality.
Written in: DPA, Schedule 2 →In website chat, yes, by default: the greeting introduces it as your AI assistant. The EU AI Act (Article 50) asks chatbots to make that clear. You can change the greeting, so keep the AI mention if you do, and add your own wording in other channels, such as email.
It's built to resist that, which is called prompt injection. The customer's conversation is kept inside clear boundaries, and the AI is told never to take it as instructions. When it reads a screenshot or photo, it's told to report the text in it, never to follow it.
Yes, if you set up visitor identification. When your customers are signed in to your site or app, your server signs a short-lived token (a JWT) saying who they are, with a key only you and we know. The chatbot checks the signature on every message, so a visitor can't simply claim to be one of your signed-in customers.
Yes, whenever you like. Delete a chatbot with all its data, one knowledge source, or a single image or file a customer sent, along with what the AI read from it. If you leave, deletion starts within 5 working days.
Written in: Privacy policy →Yes. It's part of our Terms of Service, so it applies automatically and there's nothing to sign. It covers UK and EU GDPR and includes the Standard Contractual Clauses with the UK Addendum. For a countersigned copy, just ask. We're also registered with the UK Information Commissioner's Office, under ZB810494.
Written in: DPA →Not as a company. Our hosting providers' data centres hold ISO 27001 and SOC 2 certifications, and the measures we take ourselves are set out in our DPA.
Written in: DPA, Schedule 2 →No. Resolve247 isn't built for health records, payment card details or government ID numbers, and it isn't HIPAA compliant.
Written in: DPA, Schedule 1 →Yes. Email it to [email protected] and we'll answer in writing.
Written in: DPA, section 7.7 →Email [email protected]. We'll confirm we've got it and keep you updated while we fix it. The rules for testing are in "Found a security issue?" above, and our security.txt file is at resolve247.ai/.well-known/security.txt.
Ask our chatbot, email [email protected], or book a call and we'll walk you through it.
30 day free trial, no cc required!