Skip to content

Australia · Global delivery14:30–17:30 AESTAUD

Engineering for Australian companies.

The Privacy Act reforms and the Notifiable Data Breaches scheme have made supplier security a board-level question for Australian companies. We hold an audited information security management system, ISO 27001:2022, with a certificate number you can verify.

Working with Australia

Hours, money,
and paperwork.

The three things that decide whether a cross-border engagement works. Everything here is specific to Australia.

Time overlap

14:30–17:30 AEST

AEST is four and a half hours ahead of IST, so our day opens at your 14:30. That gives three hours of overlap at the end of your afternoon and none in your morning. During daylight saving in New South Wales, Victoria, Tasmania and the ACT (October to April), the window narrows to 15:30–17:30 AEDT unless it is extended. This is the narrowest window of any market we serve. Standups, reviews and demos are scheduled inside it; everything else runs on written reporting and formal change control so work does not sit blocked overnight. Where a project needs more, we extend the window by shifting the assigned engineers and name that in the engagement.

Currency and tax

AUD

Quoted and invoiced in Australian dollars, which keeps the currency risk with us. Nothing Indian is added to the invoice: exported services attract no tax at source. As a non-resident supplier we do not charge Australian GST; a GST-registered business accounts for it under the reverse charge.

Data protection

Governing law
Privacy Act 1988 and the Australian Privacy Principles
Authority
Office of the Australian Information Commissioner (OAIC)
Our role
Processor, on your instructions

Named sub-processors, written consent before any addition.

We process on your instructions under a data processing agreement, with APP 8 cross-border disclosure obligations addressed contractually and every sub-processor named. Our incident process supports your obligations under the Notifiable Data Breaches scheme: assessment within the statutory window, written notification, and a post-incident review. Australian data residency is available and fixed at contract where required.

City by city

Local hours and
local rules.

The shared working window in local time, and any rule that applies in a city on top of the national ones.

  • Sydney

    New South Wales

    14:30–17:30 AEST, 15:30–17:30 AEDT

    AEST, AEDT in summer

    Health information in New South Wales is also covered by the Health Records and Information Privacy Act 2002.

  • Melbourne

    Victoria

    14:30–17:30 AEST, 15:30–17:30 AEDT

    AEST, AEDT in summer

    Health information in Victoria is also covered by the Health Records Act 2001.

  • Brisbane

    Queensland

    14:30–17:30 AEST

    AEST all year

    Queensland has no daylight saving, so the window stays at three hours all year.

  • Adelaide

    South Australia

    14:00–17:30 ACST, 15:00–17:30 ACDT

    ACST, ACDT in summer

    South Australia is half an hour behind Sydney, so the window is half an hour longer.

  • Perth

    Western Australia

    12:30–17:30 AWST

    AWST all year

    Western Australia has no daylight saving and is closest to India, so Perth has the widest window of any Australian city: five hours.

  • Canberra

    Australian Capital Territory

    14:30–17:30 AEST, 15:30–17:30 AEDT

    AEST, AEDT in summer

    Commonwealth agencies apply the Protective Security Policy Framework to suppliers that handle government information.

  • Gold Coast

    Queensland

    14:30–17:30 AEST

    AEST all year

    National rules apply, with no city-specific additions.

  • Hobart

    Tasmania

    14:30–17:30 AEST, 15:30–17:30 AEDT

    AEST, AEDT in summer

    National rules apply, with no city-specific additions.

What your procurement will ask

Answered
before you ask.

The questions procurement teams in Australia typically ask, with our answers. Where we do not hold something, the answer says so.

APP 8 cross-border disclosure

Addressed contractually. We accept obligations equivalent to the Australian Privacy Principles in the DPA, so your disclosure to us does not leave you carrying an unmanaged risk.

Notifiable data breach support

Our incident process is built to feed yours: assessment, written notification with scope and categories affected, and a post-incident review. We maintain an internal breach register.

ISO 27001 certificate for supplier onboarding

Certificate 25-07-21156763, issued by Anglia Compliance Group in the UK, verifiable by number without contacting us. We include it in the onboarding pack.

Australian data residency

Available. Both major cloud providers operate Australian regions; residency is written into the agreement and reflected in the architecture from the start.

  • ISO 9001:2015 Quality Management System: certified company. Certificate 706564/2026/R, issued by Robust Certifications Pvt. Ltd.QUALITY MANAGEMENTCERTIFIED COMPANYISO9001:2015
  • ISO 27001:2022 Information Security Management System: certified company. Certificate 25-07-21156763, issued by Anglia Compliance Group.INFORMATION SECURITYCERTIFIED COMPANYISO27001:2022
  • ISO 20000-1:2018 IT Service Management System: certified company. Certificate 25-07-21156764, issued by Anglia Compliance Group.IT SERVICE MANAGEMENTCERTIFIED COMPANYISO20000-1:2018

Certificate numbers, accreditation status and the verification route are published on our trust page. Check them without asking us.

Work we take on in Australia

Common problems
we build for.

Common work for teams in Australia. If one of these is yours, send us a brief.

Replacing a departed development shop

A product built by an agency that has moved on, with no documentation and no one who can safely change it. Audit first, written assessment of what is load-bearing, then restructuring.

Field and operations software

Mining, construction, logistics and utilities work where the interface has to survive a phone, a glove and no signal. Offline-first is treated as an architectural decision from the start.

Team extension at a sustainable cost

Australian engineering salaries make a five-person team expensive. Named engineers inside your repository on a monthly allocation, with a three month minimum and no recruitment fee.

Why we suit teams in Australia

  • ISO 27001 with a verifiable certificate number, which the post-reform Privacy Act environment has made a standard requirement.
  • Three hours of overlap in your afternoon, 14:30 to 17:30 AEST. The engagement is built around written reporting and formal change control, so progress does not depend on catching someone live.
  • Product refinement is a defined practice, starting with a codebase audit of software someone else built.
Where we are not the right answer

The overlap is the weakest of any market we serve: three hours, 14:30 to 17:30 AEST, and nothing in your morning. If your team needs live collaboration through your morning, an Australian or South-East Asian supplier will serve you better and we will say so on the first call. We have no Australian entity and are not on any Commonwealth procurement panel.

Australia · Questions

Asked from
Australia.

General questions about pricing, process, IP and security are answered on the FAQ page.

How do you handle the time difference with Australia?
We overlap with your working day for three hours, 14:30 to 17:30 AEST. AEST is four and a half hours ahead of India, so our working day opens mid-afternoon in yours and your morning falls entirely outside it. Standups, reviews and demos are scheduled inside the window; the rest runs on weekly written reporting and formal change control. Where a project genuinely needs more, we shift the assigned engineers and name the extended window in the engagement. If you need live collaboration through your morning, a closer supplier fits better and we will say so.
Do you meet Australian Privacy Act obligations?
Yes, our data processing agreement commits us to obligations equivalent to the Australian Privacy Principles. We process personal data only on your instructions, the agreement addresses APP 8 cross-border disclosure, and every sub-processor is named. Our incident process supports your Notifiable Data Breaches obligations with assessment inside the statutory window, written notification and a post-incident review. Australian data residency is available and fixed at contract.
Can you take over a product another agency built?
Yes, taking over a product another agency built is a defined practice for us. It begins with a codebase audit and a written assessment of what is load-bearing and what has to be replaced, before any rewrite is recommended. It suits a product that works, has no documentation, and cannot safely be changed.

Other markets

Where else
we work.

Working hours, currency and data protection, covered for every market we serve.

Working with Australia.

Contracted in AUD, governed by Privacy Act 1988 and the Australian Privacy Principles, delivered inside the 14:30–17:30 AEST overlap window.

Cognimit Technologies LLP · Monday to Friday, 10:00–18:00 IST · IST (UTC+5:30)