blueAPACHE Australia

Summary

blueAPACHE Australia is one of three regional entries listed under Procurement in blueAPACHE's main navigation, alongside blueAPACHE UK and blueAPACHE USA. blueAPACHE has published the page but has not published any detail on it — when mirrored it carried its heading and nothing else.

Rather than invent an Australian operation blueAPACHE has not described, this page records that gap and then assembles what blueAPACHE does publish about operating in Australia: the three offices, how support works, where data is held, and the Australian-specific commercial and regulatory terms — consumer guarantees, APRA obligations and Privacy Act breach notification — that sit in the published General Terms and appear almost nowhere else on the site.

What the origin page publishes

Nothing beyond the heading "blueAPACHE Australia". The origin page's title tag is empty, it has no meta description, and it has no body text. Everything else on it is site-wide furniture: the main navigation, the standard "Ready to Outpace Change?" call to action, the support block and the footer.

No regional scope, office location, product range, pricing, service description or region-specific contact detail is published on it.

blueAPACHE's Australian offices

Australia is blueAPACHE's home market. The company was founded in Melbourne in 1998 and registered with ASIC on 30 July that year, and Melbourne remains the head office.

Office Address Number
Melbourne (head office) Level 21, 242 Exhibition Street, Melbourne VIC 3000 1800 248 749
Sydney Level 7, 219 Castlereagh Street, Sydney NSW 2000 1800 248 749
Brisbane Level 2, 16 Marie Street, Milton QLD 4064 1800 248 749

Other numbers:

The Sydney and Brisbane presence dates from blueAPACHE's 2016 expansion beyond Victoria; all three offices moved to larger premises during 2017.

How Australian clients are supported

blueAPACHE publishes a follow-the-sun support model with in-house teams available around the clock, and delivery teams across Australia, the United Kingdom and the United States.

For an Australian client the significance runs the opposite way to an overseas one: overnight coverage is not an Australian night shift, and it is not outsourced — it moves to staffed offices in other time zones during their business day. The qualifier blueAPACHE uses is in-house, which is a materially different proposition from around-the-clock cover provided by subcontracted staff.

The Service Centre and Network Operations Centre operate alongside priority monitoring and emergency support running 24 hours a day, 7 days a week. Business-day operational support does not run on gazetted national public holidays.

Where Australian data is held

This is the question Australian buyers ask first, and it needs both halves of the answer.

What blueAPACHE's data sovereignty statement says. Customer data is stored and processed within Australian-based data centres, remains subject to Australian legal jurisdiction, and is governed by controls intended to minimise — not eliminate — exposure to foreign access. Administrative access is controlled through role-based permissions, multi-factor authentication and audit logging. The statement says cross-border transfers do not occur by default and are enabled only where contractually agreed, supported by encryption, contractual safeguards and vendor risk assessments. blueAPACHE states this approach aligns with the Australian Privacy Act, ISO 27001 and industry regulatory requirements.

What the General Terms say. Clause 18.3 records a standing consent from the customer for blueAPACHE to transfer Personal Information to the United States, any EU Member State, the United Kingdom, any country where blueAPACHE or its contractors are currently providing the Services from, and any other country set out in blueAPACHE's privacy policy — where it is necessary or convenient for blueAPACHE to meet its obligations.

Those two positions are not the same. One describes cross-border transfer as off by default and enabled case by case; the other records a consent given in advance, in the general terms, covering an open-ended list of countries. blueAPACHE's own knowledge base flags this and says the two should be reconciled before either is quoted. An Australian organisation with a genuine data-residency requirement should get the position for its specific services confirmed in writing rather than relying on either statement alone.

Three further gaps in the published statement are worth knowing: it does not name specific data centre operators, facilities or Australian locations; it does not distinguish between emPOWER services that may run on different underlying infrastructure; and it does not address support or administrative access performed from outside Australia.

blueAPACHE holds ISO/IEC 27001:2022 certification — certificate 202507-118, issued by Sensiba Australia Pty Ltd, valid 1 August 2025 to 1 August 2028.

Australian Consumer Law: the warranty against defects

Clause 11 of the General Terms sets out the mandatory Australian Consumer Law warranty for customers entitled to statutory guarantees. The warranty provider is blueAPACHE Pty Ltd. The claim windows differ by what was bought:

What was supplied Notice window Remedy
Hardware Within 30 days of purchase blueAPACHE diagnoses at its cost and, if confirmed, remedies, repairs or replaces — possibly with a refurbished part or a different model of substantially similar or better features — returning it at its cost within 30 days
Perpetual software licences Within 12 months of the first day of the licence Remedy, or replacement with the latest version of substantially similar or better features, at blueAPACHE's cost
Services under Schedules 3–11 Within the Service Period Re-performance or remedy; failing that, a refund of fees for the defective service for the month in which the defect occurred. Major defects may trigger termination and prepaid fee refunds
Subscription services Within the subscription period As for managed services
Professional, transition or disengagement services Within 30 days of the service being provided Re-performance or remedy; failing that, a refund of fees for the defective service

Where possible, a service claim should include a screenshot or the error message.

What the warranty excludes: defects caused by fair wear and tear, misuse, failure to maintain environmental conditions, technology failures in connected systems, data entry issues, customer breaches, maintenance by third parties, or use contrary to manufacturer or blueAPACHE instructions.

blueAPACHE reproduces the statutory notice required by Regulation 90 confirming that goods and services come with guarantees that cannot be excluded, and that customers are entitled to cancel service contracts or obtain refunds for major failures, or to have minor failures rectified within a reasonable time. Nothing in the contract displaces those statutory rights.

If you are an APRA-regulated entity

Clause 10 applies additional obligations where the customer is APRA regulated and the Services constitute a material business activity under Prudential Standard CPS 231 (outsourcing). Separately, blueAPACHE states framework alignment with CPS 234 (information security) in its brochures — the two standards do different jobs and both are relevant to a regulated buyer.

What the customer warrants (clause 10.1): that it has complied with all APRA requirements in choosing and appointing blueAPACHE and entering the agreement; that it will comply with its ongoing obligations for review, monitoring, renewal, change management, risk management including contingency plans, resourcing and governance; and that it will notify blueAPACHE if APRA varies CPS 231 or introduces a further applicable standard — at which point the parties will endeavour to agree an adjustment, and blueAPACHE is entitled to charge for any additional costs.

APRA direct access. On receiving an APRA Request — for information, documents, records, on-site visits or anything else contemplated by the applicable prudential standards — blueAPACHE will promptly notify the customer with details, comply insofar as the request is within APRA's statutory authority, and not disclose or advertise that APRA is conducting or has conducted an audit, except as needed to coordinate with other APRA-regulated customers.

Business continuity plans (clause 10.4). Where the customer requires a BCP under clause 15, it must be in a form the customer reasonably requires and must include, at minimum: the activities needed to minimise interruption from disruption to either party's operations; how blueAPACHE's plan integrates with the customer's own; the triggering event types; each party's roles and responsibilities; and the activities, processes and procedures for preventing loss or damage to Customer Data or assets and restoring the Services in a disaster.

Testing cadence and who pays. blueAPACHE must test the BCP at least every six months, or when the customer reasonably requests, and provide results within seven days of the test ending. The customer bears the cost at Time and Materials Rates or blueAPACHE's then-current rates.

Privacy Act obligations and the 24-hour breach clock

Clause 18 imposes mutual Privacy Act obligations. Each party must comply with the Privacy Act 1988 (Cth) "as though it were bound by" it — which applies the Privacy Act standard contractually even to a party that would not otherwise be an APP entity.

Personal Information may be collected, used and disclosed only for performing the agreement and the administrative tasks associated with it (invoicing, payment, contract management, risk management, insurance, renewals, delivery, maintenance and support), and disclosed only to personnel to the minimum extent necessary, as required by law, or with prior written consent.

The notification requirement is tight. Where there is an eligible data breach involving Personal Information, the party that suffered it must notify the other immediately, and in any event within 24 hours of discovery, with everything required for the Office of the Australian Information Commissioner and affected individuals. The clock runs from discovery — not from confirmation, assessment or triage. The breaching party must also co-operate with investigation or audit, and must not disclose the breach to any third party, including the Information Commissioner, without the other party's prior written approval, unless the non-breaching party fails to make a lawfully required notification.

Under clause 18.6 the customer warrants it has obtained express informed consent from each individual whose Personal Information blueAPACHE will process, including for overseas transfer — and warrants that it will not provide blueAPACHE with, or ask it to process, personal data subject to the GDPR.

Governing law

The Service Agreement is governed by the laws in force in the State of Victoria, with both parties submitting to the exclusive jurisdiction of the Victorian courts and courts competent to hear appeals from them. For an Australian customer outside Victoria, that means disputes are heard in Victoria regardless of where you are.

What is available in Australia

blueAPACHE delivers through the emPOWER portfolio under a single operating model: Managed Services, Security, Cloud, Connectivity, Collaboration, Procurement, the Microsoft Practice, and Consulting and Advisory. The core network reaches more than 165 data centre locations across Australia, New Zealand, the United States, the United Kingdom and Singapore.

blueAPACHE does not publish price lists.

Turning an Australian enquiry into a defined order

Start with the service, sites, users and required operating hours. The office list and emPOWER portfolio do not establish identical support for every service. For a combined purchase, request responsibilities across managed services, connectivity, cloud and collaboration. Keep data-location, audit and industry requirements explicit in the agreement. Published terms provide a baseline; the customer’s Service Order and Schedules determine the arrangement purchased.

Confidential information and access

Clause 16 provides mutual confidentiality protection. It covers information marked confidential, information identified orally and confirmed in writing within 30 days, and information that should reasonably be understood to be confidential. Customer Data, Customer Records and Customer Software are included; blueAPACHE’s agreement and fees are also confidential. Permitted disclosures include appropriately bound personnel on a need-to-know basis and specified professional advisers, with other exceptions in the clause. Identify who may receive operational reports, configuration details and commercial information. Access to information to deliver the service is not a general permission to circulate it.

Evidence available during the engagement

The General Terms provide standard monthly performance reports within five Business Days of month end and a formal service review every six months. Performance Records must be kept through the term and for seven years afterwards. The customer audit provisions allow access to relevant Records, premises for audit purposes and personnel interviews, with five Business Days’ notice normally or one Business Day where a regulator requires the audit. This records obligation is not a seven-year backup-retention promise for customer workloads. Agree additional report formats and audit-cost arrangements before depending on them; the general audit clause does not clearly allocate every audit cost.

Checking charges and preserving an invoice dispute

The General Terms require payment of the invoiced amount by its due date even while an amount is disputed. The customer has 60 Business Days from the invoice date to notify an error in writing, with its calculation and evidence. A dispute about blueAPACHE’s subsequent determination requires a Dispute Notice within 10 Business Days. Missing the required windows can waive the right to correction, subject to the fraud exception. Overdue amounts attract the published margin of four per cent over the RBA Cash Rate, calculated daily. Reconcile ordered quantities, approved changes and billed usage promptly; do not wait for a periodic service review to raise a billing error.

Escalating a contractual dispute

A support escalation and a formal contractual dispute are different processes. Clause 26 begins with a Dispute Notice giving adequate particulars. Representatives meet within three Business Days; unresolved matters then move through the clause’s senior-representative referral and meeting stages before court proceedings. Urgent equitable relief and disputes over whether the agreement was validly terminated are exceptions. Keep incident records, service measurements, approvals and correspondence together so the disputed obligation and requested outcome can be identified. Raising a ticket does not necessarily satisfy a formal notice requirement; use the agreement’s notice process for contractual disputes.

How liability differs from service performance

Clause 19 separates performance obligations from financial liability. The general cap per claim is the greater of the fees paid in the preceding three months or $25,000, with exclusions and specific categories governed separately. Confidentiality, information security, privacy and the IP indemnity have a $1 million per-event and $2 million aggregate cap. Data-loss liability depends on whether blueAPACHE had, and breached, a contracted backup or disaster recovery obligation; the relevant measure is restoration cost to the applicable recovery point, not the value of every business consequence. Read these provisions alongside the negotiated Service Order and Schedule; an availability statement does not describe the liability regime.

Sources and scope

The contractual detail above summarises the published General Terms and Conditions v3.6, using the KB documents on confidentiality; reporting review and audit rights; late payment and invoice disputes; dispute resolution; liability and indemnity. The customer’s Service Order, Schedules and agreed variations determine the specific engagement. See the terms and conditions guide and Service Agreement.

Frequently asked questions

Where are blueAPACHE's Australian offices?

Melbourne (head office) at Level 21, 242 Exhibition Street, Melbourne VIC 3000; Sydney at Level 7, 219 Castlereagh Street, Sydney NSW 2000; and Brisbane at Level 2, 16 Marie Street, Milton QLD 4064. All three publish 1800 248 749.

Which number should I call?

1800 248 749 for sales and the offices, 1300 135 548 for support within Australia, and +61 3 8696 9369 from overseas. Existing managed services customers can also use support@blueapache.com or the emPOWER client portal.

Is my data held in Australia?

blueAPACHE's data sovereignty statement says customer data is stored and processed in Australian-based data centres under Australian jurisdiction. But clause 18.3 of the General Terms records a standing consent to transfer Personal Information to the US, EU, UK and other countries. The two positions do not align, and blueAPACHE's own material says they should be reconciled — so confirm the position for your specific services in writing.

Does the data sovereignty statement cover overseas support access?

No. It does not address support or administrative access performed from outside Australia, does not name specific data centres or locations, and does not distinguish between emPOWER services that may run on different infrastructure.

What Australian Consumer Law rights do I have?

The statutory guarantees that cannot be excluded. Clause 11 sets out blueAPACHE's warranty against defects with notice windows of 30 days for hardware, 12 months for perpetual software licences, the Service Period for managed services, and 30 days for professional, transition or disengagement services.

What does the warranty not cover?

Fair wear and tear, misuse, failure to maintain environmental conditions, failures in connected third-party systems, data entry issues, customer breaches, maintenance by third parties, and use contrary to manufacturer or blueAPACHE instructions.

I am an APRA-regulated entity. What changes?

Clause 10 adds obligations where the Services are a material business activity under CPS 231. You warrant that you met APRA's requirements in appointing blueAPACHE and will meet your ongoing governance obligations; blueAPACHE undertakes to comply with APRA Requests and to notify you of them.

Who pays for business continuity plan testing?

The customer, at Time and Materials Rates or blueAPACHE's then-current rates. Testing must happen at least every six months, with results provided within seven days of the test ending.

How quickly must a data breach be reported?

Within 24 hours of discovery — not of confirmation or assessment — with all the information required for the OAIC and affected individuals.

Can I tell the Information Commissioner about a breach myself?

Not without the other party's prior written approval, unless they have failed to make a notification the law requires and you are legally obliged to make it.

Which law governs the agreement?

Victorian law, with exclusive jurisdiction in the Victorian courts — including for customers in other Australian states.

Is blueAPACHE certified to ISO 27001?

Yes. Certificate 202507-118, issued by Sensiba Australia Pty Ltd, valid 1 August 2025 to 1 August 2028.

Related

Source

https://www.blueapache.com/services/blueapache-australia — carried no body content beyond its heading when mirrored; checked 14 September 2026 and re-checked 23 September 2026.

Office addresses and phone numbers are from blueAPACHE's published contact page. The follow-the-sun model and the 165+ data centre figure are published on blueAPACHE's contact and about pages. Clause references are to blueAPACHE's published General Terms and Conditions v3.6. The data sovereignty position is blueAPACHE's published statement; the tension with clause 18.3 is flagged in blueAPACHE's own reference material and is reported here rather than resolved.

Knowledge Base

Images on This Page