Corefinity Data Processing Agreement
Version 1.2. Last updated 16 November 2026. Effective date: 17 November 2026.
Adapted from the Bonterms Data Protection Addendum, Version 2.0 (Attachment Version), © 2026 Bonterms, Inc., under Creative Commons Attribution 4.0. Corefinity has modified the text; Bonterms did not review and does not endorse this document. The change list below forms part of this attribution.
1. Scope and definitions
1.1 This DPA forms part of an Order that incorporates the Corefinity Terms of Service. Electronic acceptance completes it together with the processing particulars in Annex I. It does not replace a signed DPA for existing Services merely through publication or use of the Control Panel. Terms sections 1.2–1.3 govern signed-agreement priority. It protects Customer Personal Data until that data has been returned or deleted, including after service termination.
1.2 Corefinity is Core Finity Limited, trading as Corefinity, company number 10212438, VAT number GB245191217, Unit D1 Joseph's Well, Hanover Walk, Leeds LS3 1AB, United Kingdom. Customer is the contracting person identified in the Order. Capitalised service terms have the meanings in the Terms. Customer Personal Data means personal data in Customer Content processed on the Customer's behalf, including copies in support or incident records where processed on its instructions. Actual purposes determine roles; routing data through a ticket does not change it into unrestricted controller data.
1.3 Data Protection Laws means the laws applicable to the relevant processing, including the UK GDPR and Data Protection Act 2018 as amended by the Data (Use and Access) Act 2025, EU GDPR, Swiss Federal Act on Data Protection (FADP), and applicable US state privacy laws, including the CCPA as amended by the CPRA and its regulations. Controller, Processor, Data Subject, personal data and processing have their applicable statutory meanings. Sub-processor is a third party engaged to process Customer Personal Data, including an affiliate if it does so.
1.4 Security Incident is a personal-data breach: accidental or unlawful destruction, loss, alteration, unauthorised disclosure of or access to Customer Personal Data. Security Measures are Annex II. Restricted Transfer is a transfer or onward transfer subject to a cross-border safeguard requirement under applicable Data Protection Laws and not covered by a valid adequacy arrangement; it is determined by those laws, not solely by the exporter's physical location.
1.5 EU SCCs are the unaltered clauses in Decision (EU) 2021/914, with the applicable options in Exhibit A. UK Addendum is the ICO's approved International Data Transfer Addendum, version B.1.0, including valid amendments under its mandatory provisions. The incorporated versions are available on request.
2. Roles, precedence and duration
2.1 Corefinity is the Processor, or sub-processor where the Customer is a Processor for a Client. The Customer's role depends on who determines the purposes and means, not merely whether it calls itself an agency. A Customer acting as Processor confirms its Controller's authorisation, has the required processing contract with that Controller and passes on lawful instructions and relevant obligations. Corefinity remains responsible for its own duties.
2.2 Annexes I–III describe the processing, measures and suppliers. Exhibit A applies only when a legally valid transfer mechanism is needed and its conditions are met. Exhibit B supplements this DPA where the identified US laws apply. The DPA continues for as long as Corefinity or its Sub-processors hold Customer Personal Data.
2.3 For covered processing, this DPA prevails over other online contract provisions. Applicable EU SCCs prevail over inconsistent provisions; for UK transfers, the UK Addendum makes its prescribed amendments and applies its own hierarchy. Nothing here restricts mandatory law, standard-clause rights or an existing signed DPA's priority for its Services.
3. Instructions and confidentiality
3.1 Corefinity processes only on documented Customer instructions, including instructions about transfers, unless applicable UK, EU or Member State law requires otherwise. In that case it informs the Customer before processing unless that law prohibits notice on important public-interest grounds. Instructions include this Agreement, the selected configuration, authorised Panel/API/MCP actions and reasonable documented support requests. Authority is limited to the relevant account role and scope. Corefinity does not use hosted data for its own advertising or to train general-purpose AI models.
3.2 Corefinity immediately informs the Customer if, in its opinion, an instruction infringes applicable data-protection law. It may pause that instruction while the parties resolve it lawfully. It has no general obligation to monitor all Customer Content for compliance, but cannot disclaim its statutory notification duty.
3.3 Each party complies with law applicable to its own role. The Customer establishes lawful collection and instructions, gives necessary notices and obtains required consents. Corefinity ensures authorised personnel are bound by written or statutory confidentiality and appropriate access controls. Confidentiality continues while the data is held, irrespective of a shorter general commercial confidentiality term.
3.4 The parties cooperate to address changes in law. Amendments follow section 12; no unilateral amendment authorises processing contrary to the Controller's lawful instructions.
4. Sub-processors
4.1 The Customer gives general written authorisation for the Sub-processors identified in the completed Annex III. Corefinity maintains the current list in Annex III, published at corefinity.com/dpa#sub-processors, with each supplier, processing purpose, locations and safeguards. Affiliate status is not an exception to the list or authorisation requirements.
4.2 Corefinity gives account owners email notice, with a Panel copy, at least 30 days before an intended addition or replacement first processes the data. The notice identifies the entity, processing, locations and safeguards; changing a web page alone is not notice. This 30-day period is an additional online contractual protection.
4.3 The Customer may object within that period on reasonable data-protection grounds. The parties seek a workable solution. Corefinity will not put the affected data with the proposed supplier while a timely reasonable objection remains unresolved. If no solution is available, either party may end only the affected Service before the proposed processing, with lawful return/deletion and a pro-rata refund of unused prepaid Fees within 14 calendar days. Silence after proper notice permits the notified engagement, not a waiver of statutory rights. Termination is not the Customer's exclusive remedy for a breach.
4.4 Corefinity imposes the same relevant data-protection obligations by written contract, including sufficient measures and assistance, and remains fully liable to the Customer for each Sub-processor's performance of those obligations. Where applicable SCCs require it, Corefinity supplies a copy of the sub-processing agreement and subsequent amendments on request, with proportionate redactions to protect confidential information and other personal data; redactions cannot prevent understanding of the relevant obligations.
5. Security and breach response
5.1 Corefinity implements and maintains measures appropriate to the risk under Article 32, considering the processing, data, state of the art and implementation costs. This includes appropriate confidentiality, integrity, availability, resilience, recovery and regular evaluation of measures. Annex II states the service-specific measures. Changes must not materially reduce the agreed level of protection or contravene law.
5.2 Promptly and without undue delay after becoming aware of a Security Incident affecting Customer Personal Data, Corefinity notifies the Customer's designated security/data-protection contact and account owners by email, with a Panel copy where available. It does not wait for a complete investigation or for confirmation of likely harm.
5.3 The notice gives available details of the nature of the incident, affected data and persons and approximate numbers, likely consequences, containment and remedial measures and an incident contact. Missing information follows in stages without undue delay. Corefinity investigates, contains and mitigates, preserves relevant evidence, keeps the Customer informed and assists notifications under Articles 33–34 and comparable laws. Notification is not an admission of liability. A failed attempt without compromise is not itself a personal-data breach, but an availability breach or ransomware loss can be one even without proven exfiltration.
5.4 The Customer handles notices to its regulators and Data Subjects unless law requires Corefinity to act or the Customer instructs it lawfully. Corefinity's own legal notifications remain its responsibility. Payment-industry notification deadlines to an acquirer are separate from this customer notification duty.
5.5 The Customer manages application code and dependencies it controls, user permissions, credentials and its independently selected services. Corefinity manages platform components and its own access and patching. The emergency application vulnerability procedure in Terms 12.3 applies. Neither party's allocation removes the other's Article 32 duties.
5.6 Before processing high-risk special-category or criminal-offence data, the Customer assesses suitability and identifies necessary additional safeguards with Corefinity. No blanket permission substitutes for that assessment. Payment-card data is not an Article 9 special category but has separate security requirements. The Customer is responsible for its own store's card-data handling; Corefinity remains responsible for its own provider PCI scope and commitments in Annex II.
6. Assessments and assistance
6.1 Taking account of the nature of processing and information available, Corefinity assists the Customer with security obligations, impact assessments, prior regulatory consultation and other applicable duties under Articles 32–36. It supplies relevant information reasonably required to demonstrate compliance. Assistance reasonably available through ordinary tools is included; exceptional additional work may be charged only at a reasonable rate agreed in advance, never so as to frustrate a statutory duty. Corefinity does not charge the Customer to remedy Corefinity's own breach.
7. Individual requests and disclosures
7.1 Corefinity promptly refers requests concerning hosted data to the Customer and does not answer substantively except on lawful instructions or where required by law. It assists through appropriate technical and organisational measures, so far as possible, including access, correction, restriction, export and deletion. The Customer's responsibility to reply does not eliminate that assistance.
7.2 Corefinity informs the Customer of a legally binding demand for hosted data unless prohibited, checks its validity, challenges it where there are reasonable grounds and discloses only what is required and legally permitted. Applicable transfer-clause safeguards prevail. It does not voluntarily disclose hosted data to third parties for unrelated purposes.
8. Return, retrieval and deletion
8.1 At the Customer's choice, Corefinity returns Customer Personal Data and deletes remaining copies, or deletes it without return, after provision of the relevant processing Services ends, unless applicable law requires retention. The return includes reasonably necessary formats and assistance; self-service availability alone does not excuse failure to return data Corefinity alone can access.
8.2 Terms 15–16 govern cancellation, transition, free read-only retrieval and a separately confirmed erasure election. Ordinarily retrieval is 30 days after live service or the switching transition; a cancelled Trial has seven days unless the Data Act requires at least 30 days or a longer period is agreed. Ordinary cancellation is not an immediate erasure instruction or a waiver of switching rights.
8.3 At the retrieval deadline Corefinity erases remaining hosted data and digital assets, including copies, unless a later date is expressly agreed or retention is required by law. A switching extension must preserve the Data Act's full-erasure obligations. Backup rotation, log retention and seven-day deleted-Site recovery are not automatic exceptions to a promised erasure date. Corefinity's schedule (Customer Snapshot, Data Retention and Disposal Policy v1.5): snapshots are held for at most one month (7 daily, 4 weekly) unless the Customer arranges otherwise in writing; after a customer leaves, data is held for one month and then permanently removed by automated checks. So at the 30-day retrieval deadline no snapshot older than the deadline remains. Erasure covers every copy: live data, snapshots, disaster-recovery copies, logs, copies in support records and copies held by Sub-processors.
8.4 Where law requires limited retention, Corefinity identifies the basis and period where lawful, isolates the data, maintains protection and uses it only for that legal purpose. It deletes when retention is no longer required. On request it confirms completion or identifies lawful remaining copies and the applicable period. It does not offer inaccessible disk remnants as a retrieval service.
9. Information and audits
9.1 Corefinity supplies information necessary to demonstrate Article 28 compliance, including relevant policy summaries, certifications and independent reports where available. Reports are a proportionate starting point, not a substitute where insufficient or where law or a competent authority requires further access.
9.2 The Customer or its mandated auditor may audit, including inspect, to the extent reasonably necessary. The parties agree reasonable notice, scope, confidentiality and safety measures without obstructing a timely required audit. Ordinarily an audit occurs during office hours and no more than annually; these limits do not apply to a relevant incident, credible evidence of non-compliance, an authority's requirement or any other legally necessary assessment.
9.3 Audits protect other customers' data and genuine security secrets, but may examine the relevant systems and compliance controls and report on them; findings are not restricted to reproducing only the Customer's own data. Corefinity contributes to the audit. For suppliers' facilities it obtains adequate information and assistance through its contracts; lack of physical control does not remove its Article 28 duty. Confidentiality cannot prohibit reports to a regulator or other legally entitled recipient.
9.4 The Customer ordinarily bears its auditor's costs. Reasonable exceptional Corefinity assistance costs require prior agreement and do not apply to fixing its own breach or obstruct mandatory assessment rights. Exhibit B preserves applicable US assessment and remediation rights, including monitoring at least every 12 months where required.
10. Locations and international transfers
10.1 Primary Site storage, ordinary snapshots and the platform's in-Region off-box disaster-recovery copies are in the chosen Region. UK staff may access data to provide authorised support and operations. Site email and other identified processing can use the locations in Annex III. Additional offsite backup locations and support/logging suppliers must be explicitly identified there; a selected Region is not a promise that no authorised data ever leaves it.
10.2 Each party meets the transfer requirements applicable to its role. Where adequacy covers a transfer, no contractual safeguard is required merely because it crosses a border. EEA-to-UK and UK-to-EEA transfers rely on adequacy only while valid and within scope. Where another safeguard is required, Exhibit A applies only if legally suitable; selecting a foreign Region is not by itself a lawful transfer mechanism.
10.3 Corefinity documents safeguards for each onward transfer, including remote access, and conducts the necessary transfer assessment. It does not represent that an unsigned vendor form or an unverified certification already protects a transfer. Where safeguards cannot be established, it does not initiate or continue the unlawful transfer and cooperates on a lawful alternative.
11. Liability
11.1 The applicable Terms' liability provisions govern inter-party claims so far as lawful. For the online Terms, that is the mutual cap of the Fees paid or payable for the Order in the 12 months before the event giving rise to the claim (Terms 21.2), with indirect loss excluded for both parties (Terms 21.4). The relevant signed agreement governs customers it covers.
11.2 Nothing here limits rights or liability under applicable EU SCCs or the UK Addendum contrary to their terms, including inter-party and Data Subject rights, or excludes mandatory statutory liability, regulatory powers or responsibility for Sub-processors.
12. General and contacts
12.1 Material changes require the notice and fresh acceptance specified in Terms section 25. Supplier changes use section 4. Mandatory changes to transfer clauses follow their own procedure. Versions are archived. Changes cannot retrospectively reduce protection for processing already undertaken.
12.2 Data-protection contact: dpo@corefinity.com; Customers may also raise a data-protection support ticket. Contract notices: legal@corefinity.com. Customer security and data-protection contacts are those recorded in its Order/account, which it keeps current. Corefinity's EU representative under GDPR Article 27 is Prighter, through its Irish entity Prighter Privacy IRE Ltd, Dublin, Ireland; until its dedicated address is listed here, contact it through legal@corefinity.com, marked “EU representative”, and we pass the message on promptly. The DSA representative role is described in the AUP.
12.3 Except for rights expressly conferred by transfer clauses, this DPA confers no third-party contractual rights; statutory rights remain. English law and the Terms' forum apply except where mandatory law or applicable transfer clauses prescribe otherwise. Invalid provisions are severed only as law permits. English is the contractual language; this does not restrict required notices or statutory rights in another language.
Exhibit A: International transfer mechanisms
A1. EU transfers
A1.1 For a Restricted Transfer from the Customer to Corefinity for which Decision 2021/914 is legally available, its full SCCs are incorporated unaltered: Module Two for Controller-to-Processor and Module Three for Processor-to-Processor, according to the actual processing. The Customer is exporter and Corefinity importer. The Order's electronic acceptance and Corefinity's acceptance form their signatures; Annex I identifies parties, contacts and date.
A1.2 The options are: Clause 7 docking omitted; Clause 9(a) Option 2 general authorisation, 30 days' prior notice; Clause 11 independent dispute-resolution option omitted; Clause 13 authority determined under that clause and Annex I.C; Clause 17 Option 1, Netherlands law; Clause 18(b), Netherlands courts, preserving Clause 18(c). Annexes I–III below complete the corresponding SCC information. The choice of Netherlands law is a contract choice, not an assertion that its regulator is always competent.
A1.3 The 2021 SCCs cannot be relied on as the Article 46 mechanism where their adoption decision excludes the importer's relevant processing because that processing is already subject to the EU GDPR. Where a transfer is restricted but this instrument is unsuitable, the parties must establish another valid mechanism before it occurs. Neither a customer request nor hypothetical loss of adequacy automatically makes an unsuitable SCC module valid. Clauses 14–16, including assessment, government-access protection and suspension, apply in full where incorporated.
A2. UK transfers
A2.1 Where UK law requires a safeguard and the UK Addendum is legally suitable, it supplements the selected SCCs for the relevant transfer. Table 1: parties, contacts and start date in Annex I.A. Table 2: Decision 2021/914 and the modules/options in A1. Table 3: Annexes I–III. Table 4: both Importer and Exporter may exercise section 19 termination rights. Part 2 is the mandatory approved Addendum, subject only to its permitted amendments; it prevails as it specifies for UK transfers.
A2.2 The exporter assesses protection using the UK GDPR data protection test as amended by DUAA: acting reasonably and proportionately, protection after transfer must not be materially lower than under UK law. The importer supplies necessary information and supplementary measures. The exporter documents its assessment before relying on the safeguard. Corefinity does this for its own onward transfers; it does not shift that responsibility to its customer.
A3. Swiss transfers
A3.1 Where Swiss law applies, the parties use the applicable SCC module with the adjustments recognised by Swiss law: references encompass the FADP, the FDPIC is the relevant Swiss authority, and Swiss individuals' rights and access to their courts are preserved. For solely Swiss transfers, the chosen law and courts are Switzerland; for combined EU/Swiss transfers the EU choices remain, supplemented by Swiss protections without altering EU SCC rights. The parties complete any additional legally required particulars before relying on this mechanism.
A4. Onward transfers and adequacy
A4.1 The Customer-to-Corefinity clauses do not automatically execute Corefinity's separate supplier contracts. Corefinity must have valid safeguards in its own agreements with each Sub-processor, choosing modules to match the actual roles. Annex III records the mechanism and relevant processing/access locations. Supplementary measures and statutory government-access protections apply as required.
A4.2 Corefinity, a UK company, does not claim US Data Privacy Framework certification. It may rely on a recipient's applicable EU-US DPF, UK Extension or Swiss-US certification only after verifying its legal entity, current participation and coverage of the transferred data. Otherwise it must establish another lawful safeguard. Adequacy or certification is monitored and replaced if it ceases to cover the processing.
Exhibit B: US state privacy terms
A. California
A.1 Definitions. "Business purpose", "commercial purpose", "personal information", "sell", "service provider" and "share" have the meanings given in the CCPA. "Data Subject" includes a "consumer", "Controller" includes a "business" and "Processor" includes a "service provider", each as defined in the CCPA. Other capitalised terms have the meanings given in this DPA.
A.2 Obligations. Where Corefinity Processes personal information protected by the CCPA on the Customer's behalf:
A.2.1 the Customer provides the personal information to Corefinity under the Agreement for the limited and specific business purposes of providing the Services as described in Annex I and otherwise performing under the Agreement;
A.2.2 Corefinity will comply with its applicable obligations under the CCPA and provide the same level of privacy protection to the personal information as the CCPA requires of a business;
A.2.3 the Customer has the right to: (a) take reasonable and appropriate steps under section 9 (Audits) to help ensure that Corefinity uses the personal information in a manner consistent with the Customer's obligations under the CCPA; (b) receive notice and assistance under section 7 (Data subject requests) regarding consumers' requests to exercise their rights under the CCPA; and (c) on notice, take reasonable and appropriate steps to stop and remediate unauthorised use of the personal information;
A.2.4 Corefinity will notify the Customer promptly after it determines that it can no longer meet its obligations under the CCPA;
A.2.5 Corefinity will not retain, use or disclose the personal information: (a) for any purpose, including a commercial purpose, other than the business purposes in A.2.1; or (b) outside the direct business relationship between Corefinity and the Customer, except, in either case, where and to the extent the CCPA permits;
A.2.6 Corefinity will not sell or share the personal information;
A.2.7 Corefinity will not combine the personal information with personal information it receives from or on behalf of another person, or collects from its own interaction with a consumer, except to the extent the CCPA permits a service provider to do so; and
A.2.8 Corefinity engages Sub-processors under written contracts that bind them to the same obligations, and notifies the Customer of each engagement under section 4 of this DPA.
B. Other US states
B.1 This section applies where Corefinity Processes Customer Personal Data as a "processor" (or equivalent) under the Virginia Consumer Data Protection Act and the comparable laws of Colorado, Connecticut, Utah, Texas, Oregon and other US states ("US State Laws"), and the Customer is a "controller" under them. It adds to, and does not replace, the rest of this DPA.
B.2 The following are set out for the purposes of US State Laws: the instructions for Processing are the Customer Instructions in section 3.1; the nature and purpose of the Processing, the types of data and the duration are in Annex I; the rights and obligations of both parties are in this DPA.
B.3 Corefinity will: (a) ensure that each person Processing Customer Personal Data is subject to a duty of confidentiality (section 3.3); (b) at the Customer's direction, delete or return all Customer Personal Data at the end of the provision of the Services, unless retention is required by law (section 8); (c) on the Customer's reasonable request, make available all information in its possession necessary to demonstrate compliance with US State Laws (section 9.1); (d) allow and cooperate with reasonable assessments by the Customer or its designated assessor, or arrange for a qualified and independent assessor to assess its policies and technical and organisational measures using an appropriate and accepted control standard or framework and procedure, and provide a report of the assessment to the Customer on request (section 9.2 and 9.3); and (e) engage any subcontractor only under a written contract that requires the subcontractor to meet Corefinity's obligations with respect to the Customer Personal Data, after giving the Customer an opportunity to object (section 4).
B.4 Corefinity will adhere to the Customer's instructions and assist the Customer, taking into account the nature of the Processing and the information available to Corefinity, in meeting its obligations under US State Laws, including responding to consumer rights requests (section 7), the security of Processing and notification of a breach of security (section 5), and data protection assessments (section 6).
B.5 Nothing in this DPA permits Corefinity to sell Customer Personal Data, to use it for targeted advertising or profiling, or to Process it for any purpose other than providing the Services under the Customer's instructions.
Annex I: Processing particulars
A. Parties and acceptance
Customer/exporter where applicable: legal name, address, authorised signatory, operational and data-protection contacts from the accepted Order and account record. Activities: operating Sites, for itself or for Clients. Role: Controller or Processor as determined under section 2. Signature/date: recorded electronic acceptance or the expressly incorporating signed agreement.
Corefinity/importer where applicable: Core Finity Limited, trading as Corefinity, Unit D1 Joseph's Well, Hanover Walk, Leeds LS3 1AB, United Kingdom. Contact: dpo@corefinity.com. Activities: managed hosting and related processing under the Order. Role: Processor or sub-processor. Signature/date: Corefinity's acceptance of that Order. Both parties retain the completed particulars with the accepted version; blank account fields cannot complete an SCC annex.
B. Processing description
| Item | Particulars |
|---|---|
| Subject matter and purpose | Hosting and operation of Sites and Environments, authorised support, migration, backup, recovery, security and deletion under Customer instructions |
| Persons | Customer/Client staff and users; Site visitors, account holders, buyers, subscribers and people whose data the Customer lawfully includes |
| Data | Names and contact details, Site credentials and roles, orders and payment records, communications, uploads and other Site content, IP/device identifiers, configuration and access/application logs; only as selected and supplied for the Services |
| Sensitive data | Special categories such as health or religious data, and separately criminal-offence data, only as identified in the Order or documented instructions with the safeguards required by section 5.6. Payment-card data has separate PCI requirements and is not itself an Article 9 category |
| Safeguards for sensitive processing | Need-to-know access, recorded authorised instructions, appropriate encryption and confidentiality, restricted onward disclosure and applicable agreed additional controls; no unassessed high-risk processing. The Customer tells Corefinity by support ticket of any sensitive categories, and the parties record agreed additional measures, before that processing starts |
| Operations | Storage, organisation, retrieval, transmission, backup, restoration, access for authorised support/security, restriction and erasure; no unrelated provider advertising or general-purpose model training |
| Frequency and duration | Continuous as required during Services, transition and retrieval, then only until lawful deletion under section 8 |
| Sub-processing | Entities, purposes, locations and duration in the completed Annex III; no longer than necessary for the specified service and deletion obligations |
C. Competent authority
For EU SCCs use Clause 13(a): the authority competent for an EU-established exporter; if the exporter is subject to Article 3(2) and has an Article 27 representative, the authority where that representative is established; if exempt from that appointment, an authority in a Member State where affected Data Subjects are located. On request, Corefinity records the authority that applies to the Customer's transfers with the Customer's DPA particulars. It is not automatically the Netherlands authority because Netherlands law was selected. UK matters: the UK data-protection regulator; Swiss matters: the FDPIC. Corefinity completes the appropriate particulars separately for its onward-transfer contracts.
Annex II: Technical and organisational measures
These are the measures agreed for the managed service.
-
Infrastructure and physical security. Google Cloud supplies the underlying physical data-centre facilities and environmental controls. The primary Regions are London (
europe-west2), Ashburn (us-east4), Eemshaven (europe-west4) and Sydney (australia-southeast1). Corefinity manages the hosting platform and reviews relevant provider assurance evidence. Responsibility for physical facilities does not transfer all digital security duties to the Customer. -
Separation. Sites use separate containers/pods, volumes and namespaces, with database and cache services inside the Site's pod and resource controls. This is not a claim of dedicated physical hardware, complete network isolation or immunity from another workload's effect. Per-site network-policy coverage must be described accurately; no unimplemented policy is asserted.
-
Transport and encryption. Panel/API/MCP access uses HTTPS; supported Site certificates are provisioned and renewed for correctly configured domains; SSH/SFTP protects administrative transfers. Encrypted offsite backups are included (item 4). Data stored on Google Cloud, including snapshots and disaster-recovery copies, is encrypted at rest by Google Cloud's default encryption, with keys managed by Google.
-
Availability and recovery. Default scheduled snapshots are every six hours with 30-day retention, configurable within supported settings; manual and safety snapshots and customer restores are available. Encrypted offsite backups are separate disaster-recovery copies held away from the servers that run the Customer's Sites, in the same Region, maintained as 14 sets and restored by staff. Each Region uses one zone; no multi-zone failover is claimed. These settings do not override section 8's agreed erasure dates or establish an RPO/RTO guarantee.
-
Customer access. Roles, scoped tokens, SSH keys and supported allow lists let the Customer limit access. Two-factor setup is required in the new-account flow and MFA is required for MCP access; this is not a statement that every legacy user already has enforced MFA. Customers should protect all their users and review access. Staging/development access protections and search-engine exclusion are available as described in the product settings; customers control changes to them.
-
Staff access and confidentiality. Authorised staff have need-to-know access for support, operations and incident handling, under confidentiality duties and the access-control, joiner-and-leaver and training controls of Corefinity's information security management system (item 12). Access is limited to the Customer's instructions or lawful requirements.
-
Logging and monitoring. Platform monitoring and alerts identify service, certificate and capacity problems. Customer-accessible application logs (kept 90 days by default), the account activity log and recorded browser-terminal sessions support investigation. Log retention does not permit keeping data after the erasure date in section 8.
-
Vulnerability management. Corefinity maintains a risk-based vulnerability process for the systems it manages: advisory review, assessment of severity and exposure, patching or compensating mitigation, tracking, testing and escalation of unresolved risk. The supplied vulnerability policy provides internal/external scans at least quarterly and after significant changes for the cardholder-data environment and supporting scope, with verification after remediation. That scoped policy is not a promise of quarterly penetration testing of every customer application.
-
Patching. Public-facing and critical exposures are prioritised, patches are assessed and deployed through planned or emergency work with testing and recovery precautions, and exceptions require documented mitigating controls and review. Customers patch application components they control; Corefinity maintains its own platform and integration components and may intervene under Terms 12.3. No universal patch deadline is promised.
-
Incident handling. Corefinity maintains preparation, identification, containment, investigation, recovery and post-incident review procedures, trained escalation responsibilities, incident records and evidence preservation, recovery validation, and annual testing/review of its incident plan. It communicates and assists as section 5 requires. Payment-industry reports are handled under the applicable obligations separately from customer notification.
-
Application protection and safe change. Platform deployment checks include malware checks of uploaded releases, rehearsal and rollback capabilities. A web application firewall is provided through the Control Panel's per-site firewall (IP and country rules), HTTP authentication and SSH access control, login and API rate limits on current runtimes, and support for Cloudflare's WAF on domains the Customer connects through its own Cloudflare account, which the Customer configures. It is a mitigation, not a guarantee against all application vulnerabilities or a transfer of the Customer's application obligations.
-
Assurance and payment security. Corefinity holds ISO 27001 and ISO 9001 certificates for website hosting and infrastructure services, certificate references 7290297 and 9438700, issued by ISO Accelerator and recorded as valid to 30 November 2027. This is not a claim of UKAS accreditation. A management-system certificate does not certify any Customer Site or application, and the hosting does not by itself make a Customer's payment processing PCI DSS compliant; a PCI DSS commitment applies only where a signed agreement or Order states it, within its stated scope.
-
Retention and disposal. Data is returned or erased under section 8, with controlled access during retrieval, secure disposal, documented legal exceptions and confirmation on request. Processor copies in tickets and supplier systems are included. Deletion covers live, snapshot, disaster-recovery and supplier storage; any later date must be agreed explicitly.
-
Assessment and assistance. Corefinity reviews the effectiveness of these measures, provides proportionate assurance and audit cooperation under section 9 and assists with individual requests and risk assessments. Customer security testing requires prior written permission and an agreed scope under the AUP; permission is not a waiver of confidentiality or other customers' security.
Annex III: Sub-processors and locations
The Customer authorises these Sub-processors for Customer Personal Data. Corefinity adds or replaces one only after the 30 days' notice in section 4.2.
| Sub-processor | Purpose and duration | Locations | Transfer safeguard |
|---|---|---|---|
| Google Cloud (Google) | Compute, storage, network and Kubernetes for Sites and Environments, snapshots and disaster-recovery copies; for the Services, the Retrieval Period and erasure under section 8 | The Region the Customer selects: London (UK), Ashburn (Virginia, US), Eemshaven (Netherlands) or Sydney (Australia) | Google's Cloud Data Processing Addendum, including the EU SCCs and UK Addendum where a Restricted Transfer occurs; adequacy where it applies |
| Mailgun (Mailgun Technologies, Inc., a Sinch company) | Sending outbound email from Sites through verified sending domains, with Mailgun's delivery logs; for the Services | United States | Mailgun's data processing agreement, including standard contractual clauses for Restricted Transfers |
Stripe and GoCardless process payment and account data for Corefinity's own purposes, described in the Privacy Policy; they do not receive Customer Content.
Changes from the Bonterms text
This is a modified adaptation of Bonterms DPA v2.0 (Attachment Version), not the unaltered standard form. Corefinity's changes, including those made in its November 2026 review, are listed below.
- Recast the attachment as an electronically incorporated online DPA, preserving existing signed agreements, actual role allocation, a completed Order record and an immutable accepted version. Replaced DPA Details/Key Terms with Annexes I–III.
- Used Corefinity service definitions, UK spelling and plain language; clarified mixed support data, agency processor chains, instructions through authorised APIs/MCP and law-required processing. Added immediate unlawful-instruction notice and continuing confidentiality.
- Removed automatic affiliate authorisation. Added a public supplier/location/transfer list (Annex III), email and Panel notice 30 days before additions or replacements, meaningful objection resolution before processing, affected-service termination and refund, and SCC-required contract-copy access. Preserved full responsibility for Sub-processors.
- Replaced the standard 48-hour figure with the existing Corefinity position: prompt notice without undue delay. Added phased incident details, assistance, availability breaches and separation from PCI acquirer reporting. Added risk-based shared security and sensitive-data controls.
- Clarified assistance costs, unlawful disclosures, individual requests and regulatory cooperation; statutory duties cannot be frustrated by fees or a tools-only response.
- Replaced generic deletion with aligned cancellation, transition, return-or-delete choice and retrieval, mandatory EU minimums, separate erasure elections, full-copy deletion and narrow lawful retention. Removed blanket backup/log exceptions and invented expiry dates.
- Expanded audit access to Customer or mandated auditor, preserved mandatory and incident-driven assessments, appropriate control findings and regulator disclosure, and avoided absolute annual/facility restrictions.
- Added Region and authorised-location descriptions without assuming every backup or support copy stays there. Reworked transfer definitions, mechanism suitability, SCC module/authority choices, UK Addendum precedence, DUAA assessment and separately executed supplier safeguards. Chose Netherlands SCC law/courts; did not assign a regulator arbitrarily.
- Kept US terms, including CCPA no-sale/no-sharing/no-combining obligations, monitoring and remediation, and comparable state processor assistance and assessments.
- Replaced the liability terms with a cross-reference to the Terms' mutual 12-month fee cap and the applicable signed agreement; preserved SCC inter-party and third-party rights, and distinguished signed agreements. Added change control, representative and notice provisions.
- Replaced Bonterms' generic processing/security descriptions with Corefinity particulars: verified product features, the actual 2026 DPA commitments and accurately scoped patching, vulnerability and incident policies, limited to facts Corefinity has verified. No customer identity or internal response contacts were reproduced.
- Added this attribution and change record; removed any implication that Corefinity itself is US DPF-certified or that missing supplier/technical annexes existed in the prior DPA.
Adapted from the Bonterms Data Protection Addendum, Version 2.0 (Attachment Version), © 2026 Bonterms, Inc., used under CC BY 4.0. Corefinity has modified the text; Bonterms did not review and does not endorse this document.