Where your data is held
Customer data is stored and processed in the UK. The hosting location is the United Kingdom, fixed as a contractual commitment and not a configurable setting. Production, replicas, backups and disaster-recovery copies are all stored and processed in UK data centres. Outgoing email notifications are sent through our own SMTP relay, hosted in the UK and operated by Bondap. Cloudflare handles requests in transit, as described below.
Each customer has a logically isolated tenant with its own compute on UK infrastructure, with data scoped at the application, query and storage layers; a dedicated database and bucket are available as options. We own no data centre and hold no customer data on our own premises.
Bondap staff access the service remotely, to the UK-hosted environment only, through named accounts with multi-factor authentication, least privilege, and time-limited, approved and logged privileged access. Customer data is not copied, exported or stored outside the UK. Our hosting providers' standard terms reserve limited support access from outside the UK; we limit that with three controls: Bondap-held encryption keys, separation of the layers, and contractual restriction to the UK or to jurisdictions with a UK adequacy decision.
Who processes your data
BONDAP LTD is a single supplier, without sub-contractors. The providers below are hosting and infrastructure services we use; they are not sub-contractors. Under UK GDPR they are our sub-processors. Notification emails are sent through our own UK-hosted SMTP relay, which Bondap operates, so it is not a sub-processor.
| Provider | Role | Location |
|---|---|---|
| OVHcloud (OVH LIMITED) | Primary compute and hosting | Erith, United Kingdom |
| Oracle Cloud UK (Oracle Corporation UK Ltd) | Secondary hosting and disaster recovery | London (UK South) and Newport (UK West), United Kingdom |
| Wasabi (Wasabi Technologies UK Ltd) | Object and backup storage | Slough and Chessington, United Kingdom |
| Contabo (Contabo UK Ltd) | Reserve hosting and backup | Portsmouth, United Kingdom |
| Cloudflare (Cloudflare Ltd) | Edge protection only: DDoS protection, web application firewall (OWASP rule set) and DNS. Stores no customer data | Edge network |
Cloudflare's network routes each request to a nearby data centre by anycast; for users in the UK that is normally a UK data centre, but Cloudflare does not guarantee the location unless its Regional Services (Enterprise) are enabled, which we do not use. So in-transit processing (TLS termination, WAF inspection) of a request at a Cloudflare location outside the UK cannot be fully ruled out, for example when traffic is rerouted. Cloudflare stores no customer data; it may keep connection metadata (such as IP addresses) in its security logs; it is covered by Cloudflare's data processing addendum, including UK international transfer safeguards. On request, a customer's service can be served without the Cloudflare proxy (UK-hosted protection only), agreed at implementation.
We review each provider before use and at least annually (ISO 27001 certifications, data processing terms, data location and security notices). Changes to this list are notified to customers in advance, with the right to object.
The terms we process your data under
You are the data controller. Bondap is your processor, acting only on your documented instructions, under a UK GDPR Article 28 Data Processing Agreement forming part of the contract. Our ICO registration number is ZB411849.
Your data is used solely to deliver the service to you. We do not use it for analytics, cross-customer benchmarking, profiling, marketing or product development, and we do not use it to train, fine-tune or evaluate AI or machine-learning models. No customer data is sent to any third-party AI service. This restriction binds our sub-processors by flow-down and survives termination.
The Data Processing Agreement is available on request.
Information classified at OFFICIAL
The service is designed and operated to support information classified at OFFICIAL, including material carrying the OFFICIAL-SENSITIVE handling caveat. We do not hold, and do not claim, a government accreditation for the service.
| Control | Position |
|---|---|
| Data location | Stored and processed in the UK, including replicas, backups and disaster-recovery copies |
| Encryption in transit | HTTPS only. TLS 1.3 preferred and TLS 1.2 enforced as the minimum; TLS 1.0 and 1.1 are disabled; HSTS with preload; mutual TLS between services |
| Encryption at rest | AES-256 (AES-256-GCM) for the database, documents, backups and disaster-recovery copies. Keys are managed by Bondap in a key vault separate from the data and the backups, with automated, audited rotation |
| Authentication | MFA with a TOTP authenticator app, which you can enforce tenant-wide at no charge; or Microsoft Entra ID single sign-on (OpenID Connect), so that your own MFA and conditional access apply |
| Privileged access | We hold no standing access to customer data. Privileged access is granted only for a specific approved task, is time-limited, and every use is logged |
| Role-based access | Named roles, with permissions per module and per record type; your administrators can define their own roles |
| Audit logging | Application audit trail (when, who, what, how), including sign-ins, view and read access and configuration changes, plus infrastructure and security logs; each kept for 12 months. Export and streaming to your SIEM, mechanism agreed at implementation |
| Personnel | Pre-employment screening in line with the Baseline Personnel Security Standard plus a Basic Disclosure check for every member of staff before any access; leavers' accounts removed on their last working day |
| Certification | Cyber Essentials Plus and Cyber Essentials; certified to ISO/IEC 27001:2022 by Technical Standards Institute, valid to September 2027; CSA STAR Level 1 self-assessment; registered with the ICO (ZB411849) |
Retention and disposal
Retention and disposal rules are configurable per module, per record type and per document class, expressed as a period from a defined trigger event, so that incident records, risk assessments, certificates and attachments can each follow your own retention schedule. Rules are set by your administrators, not by us.
When a rule expires, the record is either flagged for review or destroyed automatically, according to how you have set the rule. Every destruction is recorded in the full audit trail.
Deletion is secure: storage is explicitly overwritten before reallocation, and deleted data cannot be directly accessed.
Production data is never replicated into or stored in non-production environments. Development and testing use synthetic or anonymised data only.
Export and exit
During the contract. Your users export from any module, on filtered entries, using built-in export functionality in SQL, CSV, Excel and JSON. This is standard functionality within your licence and carries no charge.
At exit.
| Step | What happens |
|---|---|
| Extract | Free self-service export of your full data in SQL, CSV, Excel and JSON. Optionally, we carry out an assisted extraction within 3 working days, at £1,000. Images and documents are returned as original files, with a CSV or JSON manifest of metadata and checksums |
| Transfer | The data is made available to you through a secure transfer mechanism agreed with you |
| Destruction date | A date for destruction of your data is agreed with you |
| Destruction | Once you confirm you have received your data, your data is deleted from production within 30 days, and all backup copies, including monthly archive points, within 35 days of that confirmation. Storage is overwritten before reallocation, and a certificate of destruction is issued |
Security incidents and breach notification
All incidents we discover are registered, including minor ones, and are automatically escalated to a fortnightly director review. Our target is to resolve the most serious compromises within 12 hours and others within approximately 72 hours.
Where an incident affects you, we notify your nominated contact by email, or another channel you specify, without undue delay and within 24 hours of becoming aware of it (a Severity 1 incident immediately, by phone and email), so that you can meet your own 72-hour duty to notify the ICO. As your processor we do not notify the ICO or data subjects on your behalf unless you instruct us to. Where an incident concerns data for which Bondap is itself the controller, we notify the ICO where notification applies.
Questions about how we handle your data, or to request the Data Processing Agreement: gc@bondap.com
© BONDAP LTD. This document is the property of Bondap and is published for information only. It may not be copied, reproduced, adapted, distributed or used for any purpose without our prior written consent.