Privacy policy
Last updated: 9 November 2026
Version 1.0
This policy explains how CONFLUXUS LTD handles personal data in Ben Connect: the Ben Connect apps, the cloud service behind them, the portals our clients use, and this website, getbenconnect.com.
In short:
- Your provider decides how your work phone service is used. For most of the data about you, your provider is in charge and we act on its instructions.
- Calls travel between your app and your provider's phone system. Our servers do not carry, hear or record the sound of your calls.
- Your iPhone address book and your favourites stay on your device. We never upload them.
- We do not sell personal data, show adverts or track you across other apps or websites.
Who we are
Ben Connect is provided by CONFLUXUS LTD, a company registered in England and Wales (company number 17400384), whose registered office is 66 Paul Street, London, England, EC2A 4NA. In this policy, "we", "us" and "Confluxus" mean CONFLUXUS LTD.
ICO registration number: ZC227857.
You can contact us about privacy at hello@confluxus.co.uk, or by post at our registered office.
Ben Connect is a business calling app. We provide it to businesses that run their own phone system (a "PBX"), and we call these businesses our clients. Our clients give the app to their staff, often with their own logo and colours. If you use the app, we call the client that set it up for you your provider. Your provider may be your employer, or the company that supplies your work phone service.
Who is responsible for your data
Data protection law uses two roles. A controller decides why and how personal data is used. A processor handles personal data on a controller's behalf, and only on its instructions.
| Data | Who is responsible |
|---|---|
| App users' details, devices, setup codes, phone system logins, push records and the company phonebook | Your provider is the controller, and we are its processor. |
| The portal sign-in accounts of our clients' staff | We are the controller. |
| Our clients' business contact details, contracts, seat counts and invoices | We are the controller. |
| Security records used to protect the service: sign-in attempts, the audit log and server logs | We are the controller, for keeping the service secure. |
| Enquiries sent from this website, and emails you send us | We are the controller. |
Sometimes your provider runs the phone service on behalf of another business, such as your employer. Then your employer may be the controller, your provider its processor, and we a sub-processor. Your provider can tell you how this applies to you.
Where your provider is the controller, its own privacy notice explains how it uses your data and the lawful basis it relies on, so please ask your provider for it. If you contact us about data your provider controls, we will pass your request on and help your provider respond.
What we collect
App users
When your provider sets you up, and while you use the app, our cloud holds:
- Your user record: your name as your provider entered it, your extension number, your email address if your provider added one, whether your account is active or disabled, and the support contact your provider chose for you.
- Your phone system login: the username and password your app uses to sign in to your provider's phone system. Our cloud stores the password encrypted. It is sent to your device when you set it up and when the password changes, and it is never shown in the portal.
- Your devices: the type of device (for example iPhone, Mac, Windows or a web browser), the name your device reports, when it last checked in, the version of the app it runs (we store this for every phone, whether or not call quality reports are on, so we can see which phones need an update), whether it has been signed out or removed, and a security token that lets the device talk to our cloud. We store only a scrambled (hashed) copy of that token.
- Push token: a code from Apple (and, once the Android app is released, from Google) that lets us wake your phone when a call comes in.
- Setup codes: the one-time code, QR code or setup link your provider gives you. Each one works once and expires after 24 hours. The secret part of a setup link stays in the link itself: opening the link does not send it to our servers or our logs. Only the app sends it, once, to set itself up.
- Push records: for each incoming call we wake your phone for, we record your extension, the caller's number and name as your provider's phone system reports them, a call reference, the time, and whether the wake-up reached each of your devices. The app also uses these records to show you the calls you missed while Do Not Disturb was on.
People who call app users, and phonebook contacts
- Callers: when someone calls you, your provider's phone system tells our cloud the caller's number and name, so we can wake your phone and show who is calling. We keep these in the push record described above.
- The company phonebook: if your provider uses the Ben Connect connector (a small program installed on its phone system), the connector copies the extension list (names and extension numbers) and your provider's phonebook (names and phone numbers) to our cloud, so they appear in the app.
Portal users
If you sign in to the business portal, we hold your email address, a scrambled (hashed) copy of your password, your role, and records of your sign-in sessions. We record failed sign-ins against the email address used and the internet (IP) address they came from, so we can block password guessing. We keep an audit log of the changes made in the portals: who made each one, what changed and when.
Our clients
For each client we hold business contact details, contract and billing details, the number of seats in use each month, branding (the business name, logo and colours) and the support contact details the client shows to its users. Support contact details may include a member of staff's name, phone number and email address.
Technical data
Our servers keep technical logs of requests, including internet (IP) addresses, the address requested and the time. Passwords, security tokens and sign-in headers are removed from these logs.
What stays on your device
Some data never leaves your phone, computer or browser:
- Your iPhone address book. The app reads your iPhone contacts only after you choose to see them and iOS asks your permission. They are shown in the app so you can call them through your work line, and they are never sent to our cloud. If you allow access to only some contacts, the app sees only those.
- Favourites. Contacts you star are kept on your device only.
- Call history. Your list of recent and missed calls is kept on your device.
- Your phone system login. The iPhone app keeps it in the iPhone's secure keychain. The Mac and Windows apps keep it encrypted with your computer's own secure storage. The web phone keeps its setup in your browser's local storage.
- Camera. The iPhone app uses the camera only to scan a setup QR code, and does not keep the image.
- Microphone. The app uses the microphone only during calls.
When you call a number, that number goes to your provider's phone system, as it would from any work phone.
If your provider removes your device or disables your account, the app deletes your phone system login from the device the next time it checks in with our cloud. The app checks in when it opens, when it comes to the front, and every hour.
Calls and their sound
- Your app connects directly to your provider's phone system, and the connection and the sound of your calls are encrypted between the two. Our servers do not carry the sound of your calls, and we cannot listen to them or record them.
- Your provider's phone system may record calls or keep its own call logs. That is your provider's decision, and its privacy notice will cover it.
Call quality reports
Call quality reports are off unless we switch them on for your provider. We switch them on only after telling your provider in writing and the notice period has passed, and your provider can ask us to switch them off at any time. While they are on, the app's Settings says "Call quality reports are on for your company". While they are off, we store no new reports: our cloud discards any that reach it without storing them. When they are switched off, the app stops measuring calls and sending reports the next time it checks in with our cloud. It checks in when it opens or comes back to the screen, and about once an hour while it runs, so a phone that is not in use may check in later.
While they are on, the app sends our cloud a short report after each call you answer or make that connects, and after an incoming call you answered that never connected. A report holds:
- the user and phone the call belongs to, and the kind of device (iPhone, Mac, Windows or web browser);
- which of your provider's phone systems the call was on;
- when the call connected, and how long it lasted;
- whether it was incoming or outgoing, and whether it was with a colleague's extension on the same phone system;
- how it ended: ended normally, dropped, no sound, or never connected;
- the kind of network your phone was on (Wi-Fi, mobile data, wired or unknown), or "changed" if it moved from one kind of network to another during the call, and whether the sound went through a relay server;
- figures for lost sound in each direction, delay and jitter, with an estimated sound-quality score and its worst moment, and whether we count the call as poor;
- the app's version;
- when the report reached us, and a random reference the app gives it, so that a report sent twice is kept once.
A report never holds phone numbers, the names of callers or contacts, the sound of the call, your internet (IP) address, the name of your network or your location.
We use the reports to spot calls that sound poor, and the networks, apps or people affected, so we can help your provider put problems right, and to plan the capacity of our service. From the reports we also count how many of your provider's people made or took a call in a period, to see how widely the service is used. Only our staff in the UK and contracted personnel in South Africa, who may access client data while doing support and development work, can see them, in our private staff portal. For people 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, with whose calls they were. 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 your provider has only one or two users, its totals amount to those people's own figures.
From the reports we also work out hourly totals for each provider as a whole, with no names or user details: the number of calls, calls with colleagues, minutes of talk time, calls that have sound-quality figures, poor calls, and the most calls at once. If fewer than 3 people at your provider use the app for calls, we do not show its busiest times. In the same way, with no user details, we keep when a provider's connector was offline, a check failed or an account was locked out, and the number of failed phone wake-ups each day. Reports and totals are kept for the periods in "How long we keep it" below.
Why we use it, and our lawful basis
When we act for your provider
We use app users' data, callers' details and phonebook contacts (and, only while they are switched on, call quality reports) only to provide Ben Connect to your provider: to set up your devices, deliver your phone system login, wake your phone for incoming calls, show contacts and colleagues, and give your provider support. Your provider decides the lawful basis for this. Usually that is a contract with you or your employer, or the legitimate interest in providing a business phone service.
When we are the controller
| Purpose | Lawful basis |
|---|---|
| Managing our clients' accounts, contracts, seat counts and invoices | Contract with our client; legal obligation (tax and accounting records) |
| Giving our clients' staff portal accounts and keeping them secure | Legitimate interests: providing the portal our client pays for, and protecting it |
| Security: blocking password guessing, keeping the audit log and server logs, and detecting misuse | Legitimate interests: keeping the service and our clients' phone systems safe |
| Support sessions, where our staff open a client's portal at its request to help (each lasts at most 30 minutes and is recorded in the audit log) | Legitimate interests: giving our clients the support they ask for |
| Replying to enquiries from this website, and to emails you send us | Taking steps at your request before a contract; legitimate interests |
| Telling our clients' business contacts about changes to the service | Legitimate interests; you can ask us to stop at any time |
| Dealing with legal claims, complaints and requests from regulators | Legal obligation; legitimate interests |
Where we rely on legitimate interests, we have weighed them against your interests and what you would expect. You can ask us for more detail, and you can object (see "Your rights" below).
We do not use personal data for advertising, we do not sell it, and we do not make decisions about people by automated means that have legal or similarly significant effects.
Enquiries from our website
Anyone can browse this site without telling us who they are.
If you send an enquiry with the form on getbenconnect.com, it asks for your name, your company, your email address, your phone number (optional), how many people need the app, and anything else you want to tell us (optional). There is no hidden collection.
We use these details only to reply to your enquiry and to prepare a quote. Our lawful basis is legitimate interests: you contacted us about our services, and replying is what you would reasonably expect. Where replying is a step towards a contract with you, such as a quote, we also rely on taking steps at your request before a contract. We will not add you to a marketing mailing list off the back of an enquiry without asking you separately and clearly.
Your enquiry is stored in the Ben Connect cloud, on our server in Canada. Only Confluxus admins can read it, in our private admin portal. When an enquiry arrives, we get an email alert that says only that an enquiry is waiting: the alert never holds your details. We keep each enquiry for 12 months after the last change, then delete it automatically.
If you email us instead, at info@getbenconnect.com or hello@confluxus.co.uk, we use your email only to deal with it.
This website sets no cookies and loads nothing from other companies. Our website host, 20i, keeps web server logs, including visitors' internet (IP) addresses, for security and reliability, and its content delivery network serves cached copies of our pages.
You have the rights described under "Your rights" below, and you can complain to the Information Commissioner's Office at ico.org.uk.
Who we share it with
We share personal data only as follows:
- Your provider can see the data about its own users, devices, push records and phonebook in its portal.
- Our service providers, who act on our instructions: our server host, OVHcloud; Apple, which delivers the wake-up message to iPhones; Google, which will do the same for Android phones once the Android app is released; our website host, 20i; and Tailscale, which connects our staff to our admin tools and, while we move to the new server address, carries the connections of apps that still use the old address. Our sub-processors page says what each one does and where.
- The people who work on Ben Connect: our staff in the UK, and contracted personnel in South Africa, who may access client data while doing support and development work (see "Transfers outside the UK" below).
- Apple's App Store and TestFlight. When you download the iPhone app, Apple handles your download under its own privacy policy, and Apple is responsible for that data, not us. If you install the app through TestFlight, Apple may pass us the feedback you choose to send and reports of the app crashing.
- Legal reasons. We may share data if the law requires it, to respond to a valid request from the police or a regulator, or to protect people from harm or fraud.
- Business changes. If our business is sold or merged, the data may pass to the new owner, who must keep protecting it as this policy describes.
Apple's wake-up message holds the caller's number and name, your extension, your provider's reference, a call reference and the time.
The apps and portals do not send email or text messages to app users. Your provider gives you your setup code or link directly.
Transfers outside the UK
- Our server is in Canada (OVHcloud, Beauharnois, Quebec). UK adequacy regulations recognise Canada, so no further safeguard is needed.
- Backups stay in Canada. 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.
- Apple, and Google once the Android app is released, deliver wake-up messages from the United States. Where the company is certified under the UK Extension to the EU-US Data Privacy Framework (the "UK-US data bridge"), we rely on that; otherwise on the UK International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses.
- Contracted personnel in South Africa do some of the support and development work on Ben Connect, and may access client data while doing it. That transfer 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 clients on request.
You can ask us for details of the safeguard used for any transfer.
If you are outside the UK
Ben Connect is used by businesses around the world. Wherever you are:
- Where your data is held: the Ben Connect server is in Canada (OVHcloud, Beauharnois), which UK adequacy regulations recognise. The server host, OVHcloud, takes a daily backup of the server and keeps it for 24 hours, in the same data centre in Canada.
- If you are in the European Union, you have the same rights under the EU GDPR. The European Commission recognises the UK as protecting personal data adequately, so data can pass from the EU to us.
- Everyone, wherever they are, can use the rights described under "Your rights" below, by emailing hello@confluxus.co.uk. You may also be able to complain to the data protection authority where you live.
Cookies and storage on your device
- This website sets no cookies and loads nothing from other companies.
- The portals. When you sign in, we set one cookie:
bc_opfor the business portal, or__Host-bc_adminfor our own staff portal. It keeps you signed in and protects against forged requests. It is deleted when you close your browser, and the sign-in behind it ends after 12 hours without use and always after 7 days. This cookie is strictly necessary, so we do not ask for consent for it. - The web phone keeps its setup in your browser's local storage, so it stays set up when you come back. This is strictly necessary for the web phone to work. Signing out clears it.
- No tracking. We use no analytics, advertising or tracking cookies.
How long we keep it
| Data | How long |
|---|---|
| Push records (the caller's number and name, the extension, and whether the wake-up arrived) | 30 days, then deleted automatically |
| Call quality reports (only while switched on for your provider) | 90 days, then deleted automatically. Deleted at once when your user record is deleted. If reports are switched off, those already collected are deleted when their 90 days end, or sooner if your provider asks |
| Hourly totals for a provider as a whole, with upkeep records and daily wake-up failure counts (no names or user details) | 2 years, then deleted automatically |
| App version of each phone | Kept with the phone's record, and deleted when the phone or user is deleted |
| Setup codes | Each works once and expires after 24 hours; deleted when the user is deleted |
| User record, phone system login, devices and push tokens | Until your provider deletes you, or its contract with us ends; then deleted within 30 days. Deleting a user also deletes their devices, phone system login and setup codes at once. |
| Company phonebook and extension list | While they are on your provider's phone system. Entries removed there are marked deleted in our cloud, so they leave the apps, and are deleted with the rest of your provider's data when its contract ends. |
| Portal sign-in sessions | A sign-in ends after 12 hours without use and always after 7 days (a support session after 30 minutes); its record is deleted within 38 days of signing in |
| Failed sign-in records (the email address and internet address) | Usually minutes, never more than 2 days |
| Portal accounts | Until your provider asks us to remove it, or its contract ends; then deleted within 30 days |
| Audit log | 12 months after each entry is written, then deleted automatically |
| Seat history used for invoices (a user reference and the date a seat started or stopped) | Kept for at least 6 years after the end of the financial year it belongs to, and deleted 7 years after it was written, except the newest record for each user while they still hold a seat |
| Client contract and billing records | For the length of the contract, then 6 years after the end of the financial year they belong to (the UK tax minimum) |
| Enquiries from our website | 12 months after the last change, then deleted automatically |
| Emails you send us | As long as we need them to deal with your message |
| Server logs | Kept on a rolling basis, and overwritten once they reach a fixed size |
| Backups of our database | Nightly backups, kept on our server and deleted after 14 days. The server host, OVHcloud, takes a daily backup of the server and keeps it for 24 hours, in the same data centre in Canada. |
Data deleted from our live database stays in backups until those backups expire. We do not restore deleted data from a backup except to recover from a fault.
How we protect it
We protect data with measures that include:
- encryption in transit for every connection to our cloud (HTTPS), and between your app and your provider's phone system;
- encryption of stored phone system passwords (AES-256-GCM), with a key kept separately from the database;
- portal passwords stored only as Argon2 hashes, and the tokens that let devices and portal sessions talk to our cloud stored only as hashes;
- sign-in protection that locks out repeated wrong passwords, and portal sessions that expire;
- strict separation, so each client sees only its own data;
- an audit log of the changes made in the portals;
- our own staff portal kept off the public internet, reachable only over our private network;
- 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.
No system is perfectly secure. If a security incident affects your data, we will tell your provider quickly, so it can tell you if it needs to. Where we are the controller, we will tell you and the ICO when the law requires.
Your rights
Under UK GDPR you can ask for a copy of your personal data, ask us to correct or delete it, object to or restrict how we use it, and ask for it in a portable format where that right applies. Where we rely on legitimate interests you have the right to object, and where we rely on consent you can withdraw it at any time. These rights have some limits: for example, we may need to keep invoices for tax reasons.
Where your provider is the controller, please make your request to your provider. If you send it to us, we will pass it on promptly and help your provider respond. Where we are the controller, email hello@confluxus.co.uk. We will reply within one month. We may need to check who you are first, and there is normally no charge.
Children
Ben Connect is a tool for work. It is not intended for children, and we do not knowingly provide it to anyone under 18.
Contact and complaints
If you have a question or a concern about privacy, please contact us first at hello@confluxus.co.uk, or write to CONFLUXUS LTD, 66 Paul Street, London, England, EC2A 4NA. We will try to put things right.
You also have the right to complain to the Information Commissioner's Office, the UK supervisory authority:
- website: ico.org.uk/make-a-complaint;
- phone: 0303 123 1113;
- post: Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF.
Changes
We review our policies regularly, and they may change. When this policy changes, we update the date at the top. If a change is significant, we will also tell our clients, so they can tell their users.
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