Legal

Data Processing Agreement.

Last updated: 21 October 2026

This Data Processing Agreement (the DPA) forms part of the agreement between BrainBoxIT Limited trading as BeckonDesk (the processor), a company registered in England and Wales, company number 11703272, and the customer (the controller) for the provision of the BeckonDesk visitor and contractor management platform.

It reflects the requirements of the UK GDPR, the EU GDPR where applicable, the UK Data Protection Act 2018, and applicable US state privacy laws. Where a customer has signed a negotiated agreement that addresses data processing, that agreement takes precedence over this document.

1. Roles

The customer is the data controller for personal data processed within their workspace, including the visitor, contractor and employee records they collect. BrainBoxIT Limited is the data processor and processes that personal data only on the customer's documented instructions.

2. Subject matter and duration

  • Subject matter. Provision of the BeckonDesk visitor and contractor access management platform, including sign-in, sanctions and watchlist screening, badge and pass issue, host notification, contractor compliance, parcel logging, staff sign-in and evacuation roll call.
  • Duration. The term of the underlying agreement, and afterwards until the customer data is deleted under section 8.
  • Categories of data subject. The customer's visitors, contractors and contractor company contacts, employees and hosts, parcel recipients, and the customer's own users of the platform.
  • Categories of personal data. Name, company, email address and phone number; host and visit purpose; answers to sign-in questions and custom fields; arrival and departure times; badge and pass records; signatures where the customer collects them; staff sign-in and sign-out times; certificates, insurance and induction records for contractors; parcel recipient and pickup details; sanctions and watchlist screening results; the names, email addresses and roles of the customer's users; and audit log entries, which include IP addresses.
  • Special category data. BeckonDesk does not use facial recognition, does not take visitor photographs and does not store biometric identifiers. Government-ID documents are not stored.

3. Sub-processors

The customer authorizes BeckonDesk to engage the following sub-processors. BeckonDesk will give the customer at least 30 days' notice before adding or replacing a sub-processor, during which the customer may object on reasonable data protection grounds.

  • Microsoft Azure (Microsoft Corporation). Application hosting, database, backups, secret storage, logging and monitoring. The applications, Key Vault and logs are in the East US region; the database and its backups are in Central US. United States.
  • Microsoft Entra External ID (Microsoft Corporation). Sign-in for the customer's users, served at login.beckondesk.com through Azure Front Door, which handles that traffic at the Microsoft network location nearest the user. Sign-in data is stored in the United States.
  • Azure OpenAI Service (Microsoft Corporation). The AI processing described below, through a US Data Zone deployment on a resource in East US. Under Microsoft's terms for Data Zone deployments, prompts and responses may be processed anywhere within the United States. United States.
  • Azure Communication Services Email (Microsoft Corporation, United States). Sends the platform's email from [email protected]: invitations and pass links, host notifications, approval requests, alerts and reports. The service is set to the United States data location. Delivery records (recipient address, status and time) are kept in BeckonDesk's Azure logs for 30 days. No mailbox copy of sent messages is kept.
  • Microsoft 365 / Exchange Online (Microsoft Corporation). Receives replies and messages sent to BeckonDesk addresses, such as [email protected] and the support inbox, under Microsoft's terms.
  • Cloudflare, Inc. DNS for the beckondesk.com domain, and a proxy in front of app.beckondesk.com. Traffic to app.beckondesk.com passes through Cloudflare's network, where it is decrypted and re-encrypted, so Cloudflare sees IP addresses and request details in transit. Handled at Cloudflare locations worldwide, normally the one nearest the user.
  • Stripe. Subscription billing. Stripe receives the billing contact and a reference to the workspace. Card details are entered directly on Stripe's checkout page and do not pass through BeckonDesk. No visitor data is sent to Stripe. Processed by Stripe in the United States and other countries under Stripe's own data protection terms.

Three flows send personal data to the Azure OpenAI Service:

  • Sanctions review. When a kiosk sign-in produces a borderline sanctions match, the visitor's name and company and the matched list entries are sent so the model can add a “likely namesake” or “possible genuine match” note for the admin who decides. The model never clears or refuses anyone.
  • Parcel label reading. When the customer scans a shipping label, the label image, which usually shows a recipient name and address, is sent to read the carrier, tracking number and recipient. BeckonDesk does not store the image.
  • Error triage. Excerpts of BeckonDesk's own error logs are sent to help diagnose faults. Email addresses, phone numbers, IP addresses, tokens and passwords are removed first; other text, such as a name, can remain.

Under Microsoft's published data, privacy and security terms for Azure OpenAI, prompts and responses are not made available to OpenAI and are not used to train generative AI foundation models without the customer's permission. Microsoft's abuse monitoring may store flagged content for review in the United States.

Sanctions and watchlist screening runs inside BeckonDesk against copies of the OFAC SDN List, the US Consolidated Screening List, the UN Security Council Consolidated List, the EU Consolidated Financial Sanctions List and the UK Sanctions List, downloaded from their publishers. Visitor data is not sent to the list publishers or to a third-party screening provider.

The following are not BeckonDesk sub-processors: Microsoft Teams, Slack, webhook endpoints, a customer's own Microsoft 365 mailbox or Entra ID directory, and any other destination the customer connects. Data goes there on the customer's instruction under the customer's own agreements with those providers. Plausible Analytics is used only on the beckondesk.com marketing website, with visitor consent, and receives no customer data; see the privacy notice.

4. Security measures

  • Encryption in transit and at rest. The applications are served over HTTPS, the database accepts only connections using TLS 1.2 or later, and Azure encrypts the database and its backups at rest with AES-256. Integration secrets are additionally encrypted within the database.
  • Workspace isolation in the application. All customers' records are held in one shared PostgreSQL database. Every record carries the ID of its workspace, and the application filters every query by that ID so that users of one workspace see only that workspace's records. Customers do not each have a separate database.
  • The database firewall does not accept connections from the general internet; it accepts connections from within Azure, each of which requires TLS and a password. The application's secrets are held in Azure Key Vault and not in source code.
  • Role-based access control within each workspace (Admin, Receptionist and Viewer), with optional restriction of any user to particular sites.
  • Access by BeckonDesk staff is restricted to BeckonDesk platform administrators. When a platform administrator opens a customer workspace to give support, the session lasts at most 30 minutes and is recorded in BeckonDesk's platform audit log with who opened which workspace and when. Each change made during the session is also recorded in the customer's workspace audit log as made by BeckonDesk support, with the staff member's email address.
  • An audit log in each workspace records every record created, changed or deleted, with the user, time, IP address and the change.
  • Automated backups with a 7-day point-in-time restore window, held in the same Azure region as the database. There is no geo-redundant backup.
  • Application logs are kept in Azure Log Analytics for 30 days, and Application Insights telemetry for 90 days. They can include IP addresses and other request details.
  • Retention controls that purge records on the schedule the customer configures (section 8).
  • Monitoring: an automated health check every 6 hours, error-log checks every 15 minutes while the API is running with email alerts, and Azure platform health alerts.

BeckonDesk will notify the controller without undue delay, and in any case within 48 hours of becoming aware, of a personal data breach affecting their data. The controller's own obligation to notify its supervisory authority runs to 72 hours, so this commitment is set shorter to leave the controller time to act.

5. Hosting location and international transfers

Customer data is hosted in Microsoft Azure regions in the United States. The application runs in East US and the database and its backups are in Central US. BeckonDesk does not offer a choice of hosting region.

Some processing may take place outside the United States, as set out in section 3: replies sent to BeckonDesk addresses are received by Microsoft 365 under Microsoft's terms, Cloudflare handles traffic to app.beckondesk.com at its network location nearest the user, and Stripe processes billing data under its own terms. Beyond those sub-processors, customer data is not copied outside the United States without the controller's written instruction.

Where the controller is established in the United Kingdom or the European Economic Area, or otherwise processes personal data subject to UK or EU GDPR, transfers to the United States are made under the UK International Data Transfer Addendum to the EU Standard Contractual Clauses, or under the EU Standard Contractual Clauses, as applicable. Those clauses are incorporated into this DPA by reference and take precedence over any conflicting term.

6. Data subject rights

The platform lets the controller's admins find a person, export that person's records as a file, and erase that person. Erasure removes or clears the person's details across the workspace: their visitor profile; the custom-field answers, signed documents and signatures, purpose and badge code on their visits; access events; pre-registrations, with upcoming ones cancelled; sign-in holds; screening log entries; messages sent to or about them; evacuation roll-call entries; their contractor record and certificate files; company contact details; parcels, including the name, email address, pickup signature and photo; desk bookings; and security alerts that name them. Visits and parcels remain as anonymous records, and a single audit entry records the number of records changed, not the person's details. Erasure does not change the controller's own users or staff attendance records, or watchlist entries, which the controller manages separately. A desk booking that holds only a typed name, and a screening log entry for a refused walk-in with no linked record, may not be found by erasure, so the controller should check for those by name. The visitor log, contractor compliance, staff timesheets, screening log and audit trail export as CSV. Where a request cannot be fulfilled in full through the platform, BeckonDesk will assist the controller on request and within a timeframe that allows the controller to meet its statutory deadline.

7. Audit

The controller may audit BeckonDesk's compliance with this DPA. That right is satisfied in the first instance by documentation: BeckonDesk will provide its security documentation and complete the controller's security questionnaire, under NDA where BeckonDesk asks for one.

Where the documentation is not sufficient to demonstrate compliance, the controller may carry out an on-site or live audit once per 12 months, on 30 days' written notice, during business hours, and subject to confidentiality. Each party bears its own costs; the controller bears BeckonDesk's reasonable costs for work beyond a standard documentation response.

Independent audit reports for the underlying platform layer, including ISO 27001 and SOC 2, are published by Microsoft Azure and are not BeckonDesk certifications.

8. Retention, return and deletion

Each workspace sets its own retention period: 30 or 90 days, 6 months, 1 or 2 years, a custom number of days, or keep forever. The default is 365 days. Records older than that period are purged, including visit records, staff attendance, visitor profiles and signatures no longer linked to a visit, past pre-registrations, deliveries, notification logs, access events, roll-call marks, closed approvals and contractor visit records. The workspace audit log is not purged.

The controller can export its data through the platform at any time while it has access. When a trial ends without a subscription, the workspace becomes read-only and its data is kept. When a subscription ends or a workspace is closed, the workspace is archived: its users can no longer sign in, and its data is kept so the workspace can be restored.

The controller can ask for permanent deletion at any time by writing to [email protected]. BeckonDesk then permanently deletes the workspace from the live database: every record it owns, including stored files, is deleted in a single transaction, and BeckonDesk's platform audit log keeps only the workspace ID and the number of records deleted. Deleted data leaves the backups when the 7-day point-in-time restore window expires, and log entries expire on the schedules in section 4. BeckonDesk will confirm deletion in writing on request.

Contact

Data protection enquiries: [email protected]. How BeckonDesk handles personal data collected through this website is set out separately in the privacy notice. Technical and organizational measures are summarized on the security page.