Data processing
Last updated: 9 November 2026
Version 1.0
What this is
These terms are for the businesses that use Ben Connect: our clients, "you" below. When you use Ben Connect, CONFLUXUS LTD ("we", "us") processes personal data on your behalf. You are the controller and we are the processor. Article 28(3) of the UK GDPR requires a written contract between us, and this is it. It forms part of your agreement with us, and if the two conflict about personal data, this document wins.
If you provide your phone service on behalf of another business (an end customer), and you are its processor, you confirm that you have its written authority to appoint us as your sub-processor on these terms. We then act on your instructions, and you pass on instructions, notices and requests between us and your end customer.
We are a controller, not your processor, for your business contact, contract and billing details, for your staff's portal sign-in accounts, and for the security records we use to protect the service. Our privacy policy covers those.
Each party's liability under these terms is subject to the limits and exclusions in your agreement with us. These terms are governed by the law of England and Wales.
What we process, and why
- The service: Ben Connect, a business calling app for iPhone, Mac, Windows and the web (and Android once it is released), connected to your phone system. Its cloud service sets up devices; stores your branding, support contacts, users, devices, push tokens and encrypted phone system logins; wakes phones for incoming calls; and copies your extension list and phonebook from your phone system through the Ben Connect connector.
- Purposes: setting up the apps and delivering each user's phone system login; showing your branding and support contact in the apps; waking users' phones for incoming calls, and recording whether each wake-up arrived; showing your extension list and phonebook in the apps; counting seats for invoicing; and giving you support, keeping the service secure and keeping backups.
- Call quality reports, only while switched on for you: a short report after each call a user answers or makes that connects, and after an incoming call a user answered that never connected, to spot calls that sound poor and to plan capacity. Each report holds the user and phone, the kind of device, which of your phone systems the call was on, when the call connected and how long it lasted, whether it was incoming or outgoing, whether it was with a colleague's extension, how it ended, the kind of network (Wi-Fi, mobile data, wired, unknown, or changed during the call), whether the sound went through a relay server, sound-quality figures and whether we count the call as poor, the app version, when the report reached us, and a random reference the app gives it so that a report sent twice is kept once. It never holds phone numbers, names, call audio, internet addresses, network names or location. We switch reports on only after at least the notice period in your agreement has passed since we told you in writing, and off when you ask. While they are off we store no new reports: any that reach us are discarded without being stored, and each app stops measuring calls and sending reports the next time it checks in with us. From the reports we also keep hourly totals for you as a whole, with no names or user details: calls, calls with colleagues, talk minutes, calls with sound-quality figures, poor calls and the most calls at once. We count active users from the reports. For users whose calls sounded poor, our staff can see how many of their calls in the last 4 weeks were poor out of how many they made, and the time, length and sound figures of up to 20 recent poor calls; we show no other call counts, minutes or call times for any one person, and we do not use the reports to measure how much anyone works or to judge their performance. Where you have only one or two users, your totals amount to those people's own figures. We store each phone's app version for every client, whether or not reports are on.
- People: your users (your staff, or your end customers' staff); people who call your users; people listed in your phonebook and extension list; and your staff named as support contacts.
- Data: for users, the name, extension number, email address (optional), account status, support contact, phone system username and password (the password stored encrypted), and for each device its type, the name it reports, when it last checked in, whether it was removed, its push token and a hashed device token, with their setup codes. For callers, the number and name your phone system reports, a call reference, the time and the extension called. For phonebook entries, names with phone numbers or extension numbers. For support contacts, the name, phone number, email address and web page you enter.
- Not processed: call audio, which never passes through our servers, and the address books and favourites on users' devices, which stay there. We do not expect any special category data.
- How long: for as long as you use Ben Connect, and until the data is deleted or returned as described below. Our privacy policy's table sets out how long each kind of record is kept; call quality reports are kept for 90 days, and the hourly totals for 2 years.
We act only on your instructions
We process your data only on your documented instructions: your agreement with us, these terms, and the settings you choose in the portal. If the law requires us to do something else, we tell you first, unless the law forbids it. If we think an instruction breaks data protection law, we tell you straight away, and we may pause acting on it until you confirm or change it.
We will never sell your data, use it for our own marketing, or use it to train any artificial intelligence system.
Confidentiality and security
Everyone we authorise to handle your data is bound by a written duty of confidence, and access is limited to the people who need it for their work. We protect your data with measures that include:
- encryption in transit (HTTPS) for every connection to our cloud; the apps reach your phone system over an encrypted link, and call audio is encrypted;
- phone system passwords encrypted at rest with AES-256-GCM, using a key held in the server's environment, outside the database. They are never shown in either portal, and never written to logs;
- portal passwords stored only as Argon2 hashes, and device, connector and portal session tokens stored only as hashes;
- setup codes and links that work once and expire after 24 hours;
- every record linked to one client, so each client's portal sees only its own data;
- portal sessions in secure, HttpOnly, same-site cookies, with a check against forged requests on every change. Sessions end after 12 hours without use, and always after 7 days;
- sign-in protection that locks out repeated wrong passwords, and works the same whether or not an account exists;
- support sessions by our staff limited to 30 minutes, and recorded in the audit log;
- an audit log of the changes made in the portals: who, what and when;
- our own staff portal kept off the public internet, reachable only over our private network;
- only web traffic reaching the server from the internet; the database cannot be reached from it;
- nightly database backups, and a daily backup of the whole server kept by our server host. Our nightly database backups hold portal passwords only as hashes, and phone system passwords only in encrypted form, without the key.
Sub-processors
You give us general written authorisation, under Article 28(2) of the UK GDPR, to use sub-processors. Our sub-processors page lists the current ones. We give 14 days' notice before adding or replacing one, by email and on that page. You may object on reasonable data-protection grounds, and if we cannot resolve your objection, you may end the affected services without penalty and get back anything you prepaid for the time after they end.
Each sub-processor is bound by written terms at least as protective as these, and we remain fully liable to you for its work. In an emergency, for example to keep the service running after a provider fails, we may appoint a replacement at once and tell you as soon as we can afterwards. Your right to object still applies.
If something goes wrong
We will tell you about any personal data breach affecting your data within 24 hours of becoming aware of it. The notice says what happened, who and how many records are affected, the likely consequences, and what we have done or plan to do, with a contact for more information. If we do not know everything at first, we tell you more as we learn it.
We help you notify the ICO and the people affected where that is needed, but the decision to notify is yours. We will not notify them about your data for you unless you agree or the law requires it.
Helping you meet your obligations
If someone asks us directly about data we hold for you, we pass the request to you within two working days, and we do not answer it ourselves unless you ask us to. Much of what a request needs you can do yourself in the portal: viewing, correcting, disabling and deleting users, and removing devices. Where you need more, we help within a reasonable time. We also help with data protection impact assessments (DPIAs), and with any consultation with the ICO about Ben Connect.
Getting your data back, and deletion
When your agreement with us ends, you choose what happens to your data: we delete it or return it to you and then delete it. To have it returned, ask within 30 days of the end, and we send it in a common, machine-readable format such as CSV within 30 days of your request.
We delete your data from our live systems within 30 days of the end, or of sending it back if that is later, and confirm in writing when it is done. Backups may hold it for up to 30 days afterwards, so a failed migration can be recovered; then they expire too. Until then they stay secure and are used only to recover from a fault. If UK law requires us to keep any of the data, these terms keep applying to it.
Deleting a user in the portal deletes that user's devices, phone system login and setup codes at once. Records kept for a fixed period, such as push records, are deleted at the end of that period.
Checking we are doing this properly
On request, we give you the information reasonably needed to show that we keep to these terms; a completed security questionnaire usually does this. If that is not enough, you, or an independent auditor you appoint who is bound by confidentiality and is not our competitor, may audit us. We allow an audit on 30 days' notice, once in any 12 months, or more often after a breach or if a regulator requires it. Audits take place in working hours, without disrupting the service or putting other clients' data at risk, and each party bears its own costs.
Where your data is held
Your data is held on our server in Canada (OVHcloud, Beauharnois, Quebec), which UK adequacy regulations recognise. Our nightly database backups are kept on the server itself. The server host, OVHcloud, takes a daily backup of the server and keeps it for 24 hours, in the same data centre in Canada.
Our staff in the UK, and contracted personnel in South Africa, may access your data while doing support and development work. The transfer to South Africa is made under the UK International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses, supported by a transfer risk assessment, which we share with you on request.
Apple, and Google once the Android app is released, deliver wake-up messages from the United States. Those transfers rely on the UK-US data bridge where the company is certified under it, and otherwise on the UK International Data Transfer Agreement or the UK Addendum, under that company's own data processing terms.
We make no other transfer of your data outside the UK unless it meets the requirements of Chapter V of the UK GDPR.
Changes to this document
We review our policies regularly, and they may change; when this document changes, we update the date at the top. We cannot change this document in any way that reduces the protection given to your data without your agreement. Changes take effect only by agreement, or where the law requires them. Previous versions are available on request.
Company details
CONFLUXUS LTD
Registered in England and Wales, company number 17400384
Registered office: 66 Paul Street, London, England, EC2A 4NA
ICO registration number: ZC227857
Contact: hello@confluxus.co.uk