Corefinity Acceptable Use Policy
Version 1.2. Last updated 16 November 2026. Effective date: 17 November 2026.
This policy is part of our Terms of Service. It binds the Customer for its use and authorised Users and Clients and covers every Site and Environment on the Services. It does not make a non-party Client a direct contracting party merely by being published. Existing signed agreements retain the priority stated in Terms section 1.2. If you break this policy, we may remove content, suspend a Site, Environment or account, or end the Agreement, as section 9 explains. You will always be told why and how to appeal, unless the law forbids it.
1. About this policy
1.1 Who we are. We are Core Finity Limited, company number 10212438 (England and Wales), trading as Corefinity, registered office Unit D1 Joseph's Well, Hanover Walk, Leeds LS3 1AB, VAT number GB245191217. "We", "us" and "Corefinity" mean this company. "You" and "the Customer" mean the business that places an Order and accepts the Terms.
1.2 Words with a set meaning. Capitalised words mean what the Terms say they mean. The ones that matter most here are: Users, the people the Customer lets use its account (owners, members, custom roles, API and MCP tokens); Clients, the Customer's own customers whose Sites it hosts on the Services (agencies); Customer Content, everything the Customer, its Users or its Clients put on or generate through the Services: files, code, databases, media, logs, emails sent through the Services; Services, CoreCluster, CoreStack, Add-ons, Migration Services, Support, the Control Panel (including the API and MCP Server), and any sales-led services on an Order Form; Control Panel, the Corefinity control panel at manage.corefinity.com, including its API and MCP Server; Site and Environment, a website or application and its production, staging or development copies; Region, London, Ashburn (Virginia), Eemshaven (Netherlands) or Sydney, on Google Cloud, fixed when the cluster or site is created.
1.3 Where this policy sits. The Agreement is the Order, the Terms, this policy, the Data Processing Agreement (DPA) and the Service Level Agreement (SLA). If this policy conflicts with the Terms, the Terms win. The DPA governs personal data in Customer Content. The Privacy Policy covers Account Data, which is data about you, your Users and your billing.
1.4 Who it binds. You must ensure your authorised Users and Clients comply, including during a Trial, and include appropriate equivalent obligations in your client contracts. Their statutory rights and our own duties are unaffected.
1.5 You answer for your Users and Clients. A breach by a User or a Client is a breach by you. You must give your Clients rules at least as strict as this policy, including the repeat-infringer policy in 8.11, and make sure they follow them. Where a Client's Site breaks this policy, we may act against that Site under section 9 and we will tell you.
1.6 We host; we do not publish. We store and serve Customer Content on your instructions. We do not edit it, endorse it or check it before it goes live (3.5). We act when we learn of a problem, as sections 8 and 9 describe.
1.7 How to contact us about abuse. Report abuse or illegal content to abuse@corefinity.com. US copyright notices go to our copyright agent (8.8). Legal requests from courts and authorities go to legal@corefinity.com (section 10). We answer in English.
2. Rules that flow down
2.1 Google Cloud. The Services run on Google Cloud. You must not use the Services for anything the Google Cloud Platform Acceptable Use Policy prohibits, and you must not let your Users or Clients do so. It is at https://cloud.google.com/terms/aup. The version in force when you place your Order applies to your use of the cloud services. We notify you of relevant material changes under section 11; an unseen future page does not silently amend your contract. Urgent mandatory restrictions follow the proportionate process below.
2.2 Mailgun. Email sent from your Sites leaves through Mailgun (Sinch). Mailgun's Acceptable Use Policy at https://www.mailgun.com/legal/aup/ applies to that email in addition to section 6. The version in force when you place your Order applies, and we give notice of relevant material changes under section 11. Necessary supplier restrictions may require proportionate action, explained to you; they do not waive our responsibilities.
2.3 The law. You must comply with the laws applicable to you and the relevant activity, taking account of where you and your Clients operate and offer services. That includes data protection, consumer protection, advertising, e-commerce, gambling, financial services, export control and sanctions law.
2.4 Your own online service. A user-to-user, search, marketplace or other online service may have duties under the Online Safety Act 2023, EU Digital Services Act or other local law. Applicability and exemptions depend on its activities; a comments feature does not by itself settle that question. You assess and meet duties imposed on your service. We remain responsible for duties imposed on us as host and do not contract them away.
2.5 Your Clients' obligations. Your Clients must follow this policy and the laws that apply to them. You must be able to reach each Client quickly and to act on its Site when we ask you to.
3. Prohibited content
3.1 You must not store on, publish through, link from or distribute through the Services any content that:
(a) is child sexual abuse material, or sexualises children in any way; (b) is terrorist content, or incites, glorifies or gives instructions for terrorism or violence; (c) threatens, incites or promotes violence against a person or group; (d) is hate speech that is unlawful in England and Wales or in the country where it is served; (e) is fraudulent, or is used for phishing, pharming, identity theft, pyramid schemes or other scams; (f) sells or promotes counterfeit goods, or goods or services that are unlawful to sell; (g) offers gambling without the licence the law requires where it is offered; (h) infringes copyright, trade marks, database rights, patents or other intellectual property; (i) is malware, an exploit kit, a command-and-control endpoint, or code designed to damage, take over or spy on a system; (j) breaches another person's privacy, data-protection or confidentiality rights, including personal data you have no lawful basis to process, and intimate images shared without consent; (k) is defamatory, or otherwise unlawful in England and Wales or in the country where it is served.
3.2 You must not host content you have no right to host. That includes content whose licence forbids it, content leaked or taken without permission, and content a court has ordered to be taken down.
3.3 Lawful age-restricted content may be hosted, but you must apply the age checks and labelling the law requires in each country where you serve it, and you must tell us by ticket if we ask.
3.4 If a supplier requires a restriction under its applicable terms, we assess its grounds, seek a proportionate response and tell you the actual contractual or legal basis and appeal route. Mere reputational concern is not an unrestricted power to remove lawful content.
3.5 We do not pre-screen content. We do not undertake general editorial monitoring or approval of all Customer Content. Targeted security checks, authorised support and investigation of notices are different and may involve reviewing relevant data. We act on notices (section 8), on what our automated checks flag (3.6), on orders from a court or authority, and on what our staff come across while supporting you.
3.6 Automated checks. Automated checks, such as malware checks of uploaded releases, capacity measurement, login and API rate limits and email-quality signals, may flag issues. Automated protective controls may block harmful traffic or contain an immediate incident. Human staff review contested content and account decisions; our notice identifies any automation used in detection or decision-making. We do not claim every protective action is manual or that security checks never inspect content.
4. Prohibited conduct
4.1 You must not, and must not let anyone else, use the Services to:
(a) send spam: unsolicited bulk email or messages of any kind, by any channel, from any Site or Environment, or host a Site advertised by spam; (b) run an open mail relay, open proxy, open resolver or any service that lets third parties send traffic through your Site anonymously; (c) distribute malware, or host files, scripts or pages used in an attack on anyone; (d) mine or stake cryptocurrency, or run proof-of-work or similar compute-heavy jobs that are not part of serving your Site; (e) carry out or take part in a denial-of-service attack, or any attack on anyone's system, network or data; (f) scan, probe, fingerprint or test the security of any system you do not own or control, including the Control Panel, the platform, Google Cloud and other customers' Sites, except as section 5 allows; (g) try to gain access to any account, Site, Environment, data or system you are not authorised to use, or to help anyone else do so; (h) circumvent, disable or interfere with capacity measurement, security controls, two-factor sign-in, isolation between Sites, rate limits or any other control on the Services; (i) interfere with another customer's Site, Environment or data, or with the platform, the Control Panel or our monitoring; (j) breach sanctions or export controls applicable to the activity, or provide a service prohibited by those laws; (k) share one User's login or two-factor device between people, or let a person use the Services without being a User, a Client or a Client's end user; (l) resell, rent, lend or give access to the Services or to your capacity to anyone, except that agencies may host, manage and resell hosting of Sites for their Clients under section 10 of the Terms; (m) run services that are not web hosting, including public VPNs, Tor exit nodes or relays, bulk file sharing or storage, media streaming or download sites, game servers, IRC and chat relays, backup or archive storage for other systems, or mass crawling, unless we agree in writing by ticket; (n) scrape, crawl or mass-download other sites in a way that breaks their terms, the law or their robots rules; (o) impersonate us, our staff, Google, Mailgun or any other person, or forge headers, sender details or origin information; (p) use the Services in a way that gets our IP addresses, sending domains or infrastructure blocklisted; (q) use automated tools, scripts, bots or AI agents in a way that breaches this policy, or let them act beyond what you are entitled to do.
4.2 Tokens, API and AI agents. Give each credential only necessary scopes, keep it secure, revoke it if compromised and review available activity records. You are responsible for your authorised tools and instructions, subject to the Terms. This does not make you liable for our own faulty access controls or implementation, or exclude our responsibility for negligent deletion. We do not promise complete agent-by-name logging unless the implemented record supports that claim.
4.3 Keep your applications patched. You maintain application components you control; we maintain our managed platform and integration components. Terms 12.3 governs critical-vulnerability notices and protective intervention. You must keep them updated and remove software with known vulnerabilities. A Site that is compromised because it was left unpatched is treated as a security risk under 9.5.
5. Security testing of your own Sites
5.1 You may test the security of your own Sites, including vulnerability scans and penetration tests, if you:
(a) obtain our prior written permission by ticket, specifying the Sites, dates, source IP addresses, methods and responsible person; we assess requests reasonably for safety and scope; (b) test only Sites and Environments that belong to you or to a Client who has agreed in writing; (c) stay within the capacity of your package, so that other customers are not affected; (d) never test the Control Panel, its API or MCP Server, the platform, our monitoring, Google Cloud, Mailgun, other customers or any third party; (e) do not use the test to exfiltrate, alter or destroy data you do not own, and stop at once if you reach anything that is not yours; (f) protect other customers' data and genuine security secrets and promptly share findings affecting the platform. This does not prohibit a lawful regulatory report or agreed responsible disclosure.
5.2 Load testing. You may run load or stress tests only with our written agreement by ticket, which may set a time window, a request rate and a target. Unagreed tests may be stopped if they create a material risk; legitimate ordinary traffic is not deemed an attack merely because it is generated by you.
5.3 If you find a flaw in our platform or Control Panel, tell us by ticket at once. Do not exploit it or access data that is not yours. Coordinate a reasonable responsible-disclosure period with us; this is not an indefinite ban on lawful disclosure or reporting to an authority.
5.4 We may stop a test that affects other customers or the platform, and we may suspend a Site that is being tested in breach of this section.
6. Email sending
6.1 How email works on the Services. Email is send-only. Each production Site sends through a Mailgun sending domain that you verify with your own DNS records (a Magento 2 Site may have up to five). We do not provide mailboxes, and we do not receive email for you. By default, staging and development Environments catch outgoing mail for testing and do not deliver it.
6.2 What you may send. Transactional and account email (order confirmations, receipts, password resets, notifications your users asked for), and marketing email to recipients who have given clear, explicit and provable consent to receive it. Marketing email must comply with the law where each recipient is, including the UK's PECR, the EU's ePrivacy rules and the US CAN-SPAM Act.
6.3 You must not:
(a) send to a list you bought, rented, scraped or otherwise did not build from your own consents; (b) send marketing email to anyone who has not opted in, or who has unsubscribed; (c) omit a working unsubscribe link from marketing email, or fail to honour an unsubscribe without undue delay; (d) use a misleading sender name, subject line, "From" or "Reply-To" address, or forge headers; (e) send from a sending domain you do not control or have not verified; (f) use a Site as a relay for mail generated elsewhere.
6.4 Keep proof of consent for every marketing address, including when and how it was collected, and show it to us if we ask because of a complaint.
6.5 Link to your privacy policy from your marketing email, and tell recipients who you are.
6.6 Sending quality. Mailgun reports bounce, spam-complaint, unsubscribe and block rates. We apply its disclosed acceptable-use requirements and explain the relevant threshold or harmful pattern when requesting remediation. We do not insert a different, unverified numerical limit here. Where no urgent harm exists we give a reasonable opportunity to correct the cause before restricting sending.
6.7 Suspension of sending. We may suspend sending for a domain or a Site without notice if it harms deliverability for other customers, breaches 6.3 or Mailgun's policy, or gets our sending infrastructure blocklisted. We give the statement of reasons required by section 9.6, with the reason and what to fix, and restore sending once it is fixed. Repeated problems may lead to the loss of email for that Site. Sending through Mailgun is also subject to Mailgun's own suspension rights, which we cannot override.
7. Fair use and resources
7.1 Capacity is measured, not reserved. Your package sets the cores, memory and disk you may use. On CoreCluster, CPU and memory use is measured as the 95th percentile of five-minute peaks over 24 hours, rechecked every 10 minutes, against your package. At 75% the Control Panel asks you to upgrade. At 90% new Sites and Environments are refused, while existing Sites keep running. Upgrades are self-serve and apply at once.
7.2 CoreStack. A CoreStack Site runs on shared pools. Your package sets the capacity you may use for that Site and its staging Environment; it is not a promise of dedicated hardware or of resources set aside for you alone.
7.3 Dedicated containers per Site. Each Site runs in its own dedicated containers, in its own namespace, and shares the cluster's nodes with your other Sites (CoreCluster) or with other customers' Sites (CoreStack). There is no traffic autoscaling: a Site that outgrows its size needs a larger size or package.
7.4 Use that degrades other customers. If a Site uses capacity in a way that slows or destabilises other customers or the platform, whether or not it is within your package, we may ask you to reduce the load or upgrade within a stated time. If you do not, or if the effect is severe, we may throttle or suspend the Site. We give notice first where practicable; where a Site threatens the platform, we may act at once and tell you straight after (9.5).
7.5 Bandwidth. We do not charge separately for bandwidth today. Traffic must be that of a normal website or application. Bulk downloads, media streaming, file distribution and similar patterns are not web hosting (4.1(m)) and need our written agreement. Any new bandwidth or data-transfer charge follows Terms section 8, including fresh agreement where required and no charge prohibited on switching under section 16.
7.6 Disk, snapshots and logs. Your package sets your disk, snapshot allowance (twice your disk) and log allowance. Logs follow their configured retention, with a standard service retention of 90 days, subject to the DPA's deletion duties. If you reach an allowance, the Control Panel tells you, and you must upgrade or reduce use. Snapshots and logs are for your Sites on the Services, not for storing other data.
7.7 These rules apply during a Trial as they do afterwards.
8. Reporting abuse, illegal content and copyright (notice and action)
8.1 How to report. Anyone may report content or conduct on the Services that they believe is illegal or breaks this policy, by email to abuse@corefinity.com or by post to our registered office (1.1). The mailbox is read by people, not only by automated tools. You do not need to be a Corefinity customer, or to be in any particular country, to report.
8.2 What a notice must contain. So that we can act, a notice must include:
(a) an explanation of why you believe the content is illegal (or breaks this policy), with enough detail for us to understand the claim without a detailed legal review; (b) the exact URL or URLs of the content, and any other information needed to identify it; (c) your name and email address, unless the content involves child sexual abuse, in which case you may stay anonymous; (d) a statement that you believe in good faith that the information in the notice is accurate and complete.
8.3 What we do with a notice. We:
(a) confirm receipt without undue delay if you gave us an email address; (b) handle the notice without undue delay and in a timely, diligent, non-arbitrary and objective way, treating threats to life or safety and child sexual abuse material first; (c) may ask you for more information, and may ask the Customer to respond within a stated time where the position is not clear; (d) decide whether to remove or disable access to the content, to require the Customer to change it, or to take no action; (e) tell you our decision and the reasons without undue delay, including whether automated tools were used, and how to challenge it; (f) tell the Customer, with a statement of reasons (9.6), if we take action.
8.4 Telling the Customer who reported. We tell the Customer who sent a notice only where that is needed to deal with it (for example a copyright or trade mark claim, where the Customer may want to contact the rights holder), and never where it would be unsafe for you or unlawful.
8.5 Not every notice leads to removal. We weigh the rights of the person reporting and of the Customer, including freedom of expression. Where the content is lawful and within this policy, we take no action and tell you why. If facts remain uncertain, we request clarification and weigh the seriousness, urgency, evidence and affected rights before any proportionate interim restriction. An appeal does not justify arbitrary removal.
8.6 UK: how the hosting defence works. We are a host under regulation 19 of the Electronic Commerce (EC Directive) Regulations 2002. We have no general duty to monitor. Once we have actual knowledge of unlawful content, we act expeditiously to remove it or disable access to it. A sufficiently precise and substantiated notice may establish knowledge or awareness; formal completeness does not automatically prove illegality. For DSA Article 16, we assess whether a diligent host can identify illegality without a detailed legal examination. The applicable UK and EU tests retain their own requirements.
8.7 Threats to life or safety. Where DSA Article 18 applies and information raises a suspicion of a criminal offence threatening life or safety, we promptly inform the relevant EU Member State's law-enforcement or judicial authority and provide relevant information. If we cannot identify that Member State with reasonable certainty, we inform the authority where our EU representative is established or Europol, or both. We also make any other legally required reports, including to relevant UK authorities. A report only to UK police is not a substitute for that EU duty.
8.8 US copyright: our copyright agent. Send notices of claimed copyright infringement under 17 U.S.C. 512(c) to our copyright agent: Copyright Agent, Core Finity Limited, Unit D1 Joseph's Well, Hanover Walk, Leeds LS3 1AB, United Kingdom; email legal@corefinity.com, subject “Copyright notice”; telephone +44 800 464 7255. We add our US Copyright Office designation number here once it is registered. A copyright notice sent only to abuse@corefinity.com is handled under 8.2 and 8.3 and passed to the copyright agent.
8.9 A valid DMCA notice must be in writing and include:
(a) a physical or electronic signature of a person authorised to act for the owner of the copyright said to be infringed; (b) identification of the copyrighted work claimed to have been infringed, or a representative list if the notice covers several works on one Site; (c) identification of the material claimed to be infringing, with the exact URL or enough information for us to find it; (d) your address, telephone number and email address; (e) a statement that you believe in good faith that the use is not authorised by the copyright owner, its agent or the law; (f) a statement, under penalty of perjury, that the information in the notice is accurate and that you are authorised to act for the copyright owner.
8.10 What we do with a DMCA notice. On a compliant notice we act expeditiously to remove or disable the identified material, notify the Customer and provide the notice as appropriate. For an incomplete notice containing the essential identification and contact information, we make reasonable efforts to contact the sender to obtain the missing elements, as section 512(c)(3)(B) requires. The Customer may send a counter-notice to the copyright agent in 8.8, which must include: (a) the Customer's physical or electronic signature; (b) identification of the material removed and where it appeared before removal; (c) a statement under penalty of perjury that the Customer believes in good faith that the material was removed by mistake or misidentification; (d) the Customer's name, address and telephone number, consent to the jurisdiction of the US federal district court for that address (or, for an address outside the US, any district in which Corefinity may be found), and agreement to accept service of process from the person who sent the notice or their agent. We send the counter-notice to the person who sent the notice, telling them we will restore the material in 10 US working days. We restore it not less than 10 and not more than 14 US working days after we receive the counter-notice, unless our agent receives notice that the original complainant has filed an action seeking a court order restraining the Customer from infringing in relation to that material. US working days, excluding US federal holidays, apply to this statutory timetable, not the English Business Day definition in the Terms.
8.11 Repeat infringers. We end the accounts of Customers who repeatedly infringe copyright or other intellectual property, in appropriate circumstances, and we may end a Client's Site or Environment for the same reason. We assess reliable evidence, notice history, counter-notices and court outcomes; an unchallenged allegation is not automatically conclusive infringement. We accommodate and do not interfere with standard technical measures within 17 U.S.C. 512(i). You must pass this policy to your Clients and apply it to them.
8.12 Misuse of the process. Sending a notice or counter-notice you know to be false is itself a breach of this policy and may be unlawful (for example under 17 U.S.C. 512(f), which makes the sender liable for damages). We may seek clarification or use proportionate measures against process abuse after warning and individual assessment. We do not adopt a blanket refusal to consider credible new reports, or assume the DSA online-platform rules automatically apply to every hosting service.
8.13 Other complaints. Trade mark, defamation, privacy and data-protection complaints follow 8.1 to 8.5. Where the complaint is really between the complainant and the Customer, we may ask them to resolve it directly and act only if the law requires us to.
9. How we enforce
9.1 Investigation. We may examine relevant content, configuration and logs, preserve proportionate evidence and ask for an explanation where necessary to assess a suspected breach. Processing remains subject to the DPA and Privacy Policy. Qualified staff supervise content/account decisions and appeals. Necessary automated security controls may operate immediately; section 3.6 and the actual decision notice explain their role.
9.2 What we may do. Depending on the breach, we may:
(a) warn you; (b) require you to fix the problem within a stated time; (c) remove, or disable access to, specific content, files or URLs; (d) suspend outgoing email for a domain or Site (6.7); (e) throttle a Site (7.4); (f) suspend a Site or Environment (it goes offline; its data is kept); (g) suspend the account (every Site goes offline; data is kept); (h) end the Agreement, or your right to use part of the Services, for a serious or repeated breach, under the Terms (sections 13 and 15); (i) report the matter to the authorities, and preserve or disclose evidence as section 10 allows.
9.3 Proportion. We act in proportion to the breach and prefer the least disruptive step that fixes it. For a first breach that is not serious, we warn you and set a time to fix it. We take account of how serious and how widespread the breach is, whether it is deliberate, the harm to others, your history, and the rights of everyone affected, including your Clients' users and freedom of expression.
9.4 Fixing it yourself. Where we ask you to fix something, you must tell us by ticket when it is done. If you fix it in time, we take no further action unless the breach recurs.
9.5 Immediate action. We may act at once without a prior warning where necessary, while providing the decision notice required by 9.6, where:
(a) the content is seriously harmful, including child sexual abuse material, terrorist content or a threat to life or safety; (b) a Site or account is a security risk to other customers, the platform or third parties, for example a compromised Site, an open relay, malware, an attack or spam in progress; (c) a binding lawful order or applicable supplier restriction requires proportionate action; (d) the breach is a repeat of one we have already warned you about; (e) a Site threatens the stability of the platform (7.4).
9.6 Statement of reasons. Whenever we remove or disable access to content, throttle or suspend a Site, Environment or account, or end the Agreement, because content is illegal or because of a breach of this policy, we send the account owners a statement of reasons at the latest when the restriction takes effect, where electronic contact details are known. Urgency alone is not a DSA Article 17 exception. The statement says:
(a) what we did, which content or Site it affects, and for how long and where it applies; (b) the facts and circumstances we relied on; (c) whether a notice (section 8), an order from an authority, our own checks or a report from a provider triggered it, and, only where strictly necessary, who sent the notice; (d) whether automated tools were used to detect or decide it; (e) for illegal content, the law relied on and why the content breaks it; for a breach of this policy, the clause relied on and why the content or conduct breaks it; (f) what you must do to put it right, if anything; (g) how to appeal (9.7), and that you may also go to court.
The statement is written in plain language. Any omission or redaction must have a lawful basis. DSA Article 17 does not apply to deceptive high-volume commercial content or Article 9 orders, which have their own notice rules; we do not create a wider exemption merely on our own view that disclosure is inconvenient. Where email fails we use another known electronic contact where available.
9.7 Appeal. You may appeal any decision under 9.2 or section 8 by emailing abuse@corefinity.com within six months of notification of the decision, with the reference, what you disagree with and any evidence. A person who did not take the original decision reviews it, where our size allows, and we answer with reasons without undue delay. If we got it wrong, we reverse the action and restore the content or Site. If the appeal is refused, we say why. Where statutory online-platform dispute-settlement or regulator-complaint rights apply, those routes remain available and our decision notice identifies them. Appealing does not stop you going to court, and nothing in this policy limits your rights under the law that cannot be excluded. People who sent a notice may use the same route to challenge a decision not to act.
9.8 Single point of contact. For users of the Services and for the authorities of the UK, the EU and its member states, our point of contact for this policy is abuse@corefinity.com. It is staffed by people, not only automated tools. We communicate in English. Contact options include access to a person and are not exclusively automated.
9.9 EU legal representative. Our legal representative under DSA Article 13 is Prighter, through its Irish entity Prighter Privacy IRE Ltd, Dublin, Ireland. It also acts as our GDPR representative; that is a separate role. Until our representative's dedicated address is listed here, contact it through legal@corefinity.com, marked “EU representative”, and we pass your message to it promptly.
9.10 Your Clients. When we act against a Client's Site, we send the statement of reasons to you. You must pass it on to the Client at once, together with the appeal route, and you may appeal on the Client's behalf.
9.11 Fees during a suspension. Fees continue during any suspension caused by your breach or by a breach by your Users or Clients. We restore a suspended Site or account within one Business Day of the breach being fixed, unless the Agreement has been ended. Ending the Agreement for breach follows the Terms (sections 13 and 15), including the Retrieval Period where it applies.
9.12 Records. We keep proportionate notice, decision and appeal records for two years, then delete or anonymise them unless a specific legal obligation or claim requires longer. Evidence containing hosted personal data remains subject to the DPA; a general record policy is not permission to retain all removed content.
9.13 Our liability. Action we take in good faith under this policy is subject to the limits in the Terms (section 21). You manage your relationship with Clients; this does not transfer liability for our own wrongful action to you or remove your remedies. Fees and restoration are governed by Terms section 13, including remedies for wrongful restriction.
10. Law enforcement and legal requests
10.1 We disclose Customer Content or Account Data to a court, regulator, law-enforcement body or other authority only under a binding legal order or where the law requires us to. We do not give authorities routine or standing access to Customer Content.
10.2 We check every request. We check that it comes from a body with the power to make it, that it is addressed to the right entity, that it is specific and that it is not wider than the law allows. We may ask for it to be narrowed, and we may challenge it where we think it is unlawful or disproportionate.
10.3 We tell you. We tell the account owners about a request for your Customer Content or Account Data before we comply, where practicable, unless the law or the order forbids it, or another specific legal restriction prevents notice. We do not replace the DPA's or transfer clauses' notification duties with an unrestricted discretionary exception. Where we were forbidden at the time, we tell you once we may.
10.4 Emergencies. Where we believe in good faith that disclosure is needed to prevent a threat to someone's life or safety, we may disclose to the authorities without an order, where the law allows (8.7).
10.5 Where to send requests. Courts and authorities should send requests to legal@corefinity.com or to our registered office (1.1), in English, stating the legal basis, the data sought, the Site or account concerned, and a contact for questions. Requests about personal data on a Customer's Site are usually for the Customer, as controller, to answer; we direct them to the Customer unless the law requires us to act.
10.6 Preservation. We may preserve data on a valid preservation request for the period the law allows, and will tell you where 10.3 permits.
10.7 Requests from private parties. Solicitors, rights holders and other private parties should use section 8. We do not disclose a Customer's identity to a private party without a court order, except as 8.10 provides for DMCA counter-notices.
11. Changes to this policy
11.1 We may change this policy. For a material change, we give you at least 30 days' notice by email to the account owners and in the Control Panel, in line with the Terms (section 25). Material amendments require fresh acceptance as Terms section 25 provides. Posting, silence or continued use alone does not amend the contract. If you decline, the existing contract continues unless lawfully ended; you may end before a materially adverse change and receive any refund the Terms require.
11.2 We may make a change sooner where the law or a court requires it, or to deal with a security risk, and will tell you as soon as practicable.
11.3 Corrections, link updates, contact details and new legal references take effect when published, with the date at the top updated.
11.4 The version number and date at the top of this policy identify the version in force. Earlier versions are archived and available from legal@corefinity.com.