Australia: Reviving Lapsed Development Applications and Development Approvals under the Sustainable Planning Act (QLD)


It is no secret that the provisions of the Sustainable Planning Act 2009 (Qld) (SPA) can be confusing and complex. There have been many occasions where a misunderstanding of how the provisions operate, or indeed an absence of knowledge about certain sections, has led to development applications lapsing part way through the Integrated Development Assessment System (IDAS) process. Even more frustrating for developers and landowners is the situation where a development proposal is being pursued, with significant time and money being expended on the development, only to find out that the development approval has lapsed due to the expiration of the relevant period (formerly known as the "currency period").

The lapsing provisions within the SPA, both for development applications and development approvals, are a necessary evil. Without such provisions, opportunities may exist to prolong the assessment of development applications for many years, outliving planning instruments and strategic direction, or for a development approval to attach to land and remain dormant for a long time prior to being acted upon. The lapsing provisions are imperative to ensure that:

  1. the applicant for a development application undertakes the required actions within the IDAS process in a timely and efficient way, in order to minimise unnecessary delays; and
  2. development approvals are acted upon shortly after the proposed development has been assessed against the current planning instruments.

However, the provisions can often lead to confusion. If certain actions are not taken within strict timeframes, the development application or development approval can come to an abrupt end, with the only recourse being to re-lodge a new development application (or apply to the Planning and Environment Court for an excusal).

However, the SPA contains provisions within the IDAS process which allow an applicant to revive a development application that has lapsed, but there is only a narrow window of opportunity to exercise those provisions. Traditionally the Planning and Environment Court's excusal power has been used to cure many deficiencies in development applications and approvals, and this power has unarguably been expanded upon commencement of the SPA. Such expansion of the excusal power has seen the Court breathe new life into development approvals that have lapsed, despite the wording of the sections themselves not venturing that far.

This paper will identify the lapsing provisions in the SPA for development applications and development approvals, and set out the available processes to revive applications and approvals that have lapsed. In providing a number of case examples, this paper seeks to identify how the Court's excusal power has expanded and what discretionary factors are relevant when applying to the Court to revive a lapsed development application or development approval.

Lapsing of Development Applications

Under the SPA, there are five situations in which a development application can lapse in the IDAS process, as follows:

  1. failing to take action to make the application a "properly made application";1
  2. failing to give material to the referral agencies;2
  3. failing to respond to an information request;3
  4. failing to commence public notification; and4
  5. failing to provide a notice of compliance to the assessment manager after completion of public notification.5

Each of the requirements listed above has timing provisions, requiring the applicant to take the necessary action within a defined period. If such action is not taken within time, the SPA makes it clear that the development application lapses.

Under the repealed Integrated Planning Act 1997 (Qld) (IPA), if an applicant was faced with the consequences of a lapsed development application, it's only recourse was to lodge a fresh development application and commence the IDAS process from the start, or commence proceedings in the Planning and Environment Court seeking an excusal as part of the Court's discretion. However, the SPA has introduced a new process that allows a lapsed development application to be revived and continue through the IDAS process, without the need to apply to the Court.

IDAS Revival of Lapsed Development Applications

The 'IDAS revival process' under the SPA applies to each of the lapsing situations set out above, except for the failure to take action to make the development application a "properly made application". While the lapsing provisions are necessary, this needs to be balanced against minimising accidental lapses due to minor administrative oversights. Accordingly, the SPA allows for a development application to be 'revived' within a reasonable timeframe.

In all IDAS revival situations, the process is the same. It involves two steps:

  1. Step 1 – if a development application has lapsed, the applicant has five business days after lapsing to give the assessment manager written notice that the applicant seeks to revive the lapsed application; and
  2. Step 2 – the applicant must take the necessary action within a further defined period.

In relation to Step 2, the further period within which the application must act is usually five business days. However, the time to commence public notification after providing written notice under Step 1 is ten business days. Also, the time to take the required actions as part of Step 2 may be a different period as agreed between the applicant and the assessment manager.

If the IDAS revival process is followed, the development application is taken not to have lapsed and it will continue through the IDAS process.

While this process allows an applicant to revive a lapsed development application without having to go to Court, it should be noted that the time periods in which the revival steps must be taken are quite tight. It might be thought that if a timing period is accidentally missed by an applicant who is not made aware of the lapsing, then a five business day period in which to give notice seeking to revive the lapsed application is a very short period that could pass by without the applicant noticing. This, however, is the balancing exercise that was obviously undertaken by the legislature in weighing up the need to ensure efficient pursuit of development application whilst also allowing a degree of flexibility to cure accidental lapses.

If a development application lapses and the IDAS revival process is not followed, then the applicant has recourse to the Planning and Environment Court, which is discussed below.

Lapsing of Development Approvals

Section 341 of the SPA identifies when a development approval lapses if the development is not started within a certain time known as the "relevant period" (previously known as the "currency period"). A development approval itself may state a different relevant period to the default ones stated in section 341. If the approval does not expressly set out a different relevant period, then:

  1. to the extent a development approval is for a material change of use (MCU), the approval lapses if the first change of use does not start within four years of the approval taking effect;6
  2. to the extent a development approval is for reconfiguring a lot (ROL), the approval lapses if the plan for the reconfiguration is not given to the local government within two years (if operational works are not required) or four years (if operational works are required);7 and
  3. to the extent a development approval is for development other than an MCU or ROL, the approval lapses if the development does not substantially start within two years.8

It should also be noted that section 341 provides a mechanism whereby the beginning of the relevant periods for approvals for MCU and ROL will 'roll forward' in some circumstances to align with the beginning of any "related approval". This will obviously affect the time to start the first change of use (for an MCU approval) or give the plan for the reconfiguration to the local government (for an ROL approval). Additionally, a relevant period for a development approval can be extended, but such a request must be made before the development approval lapses.9

Confusion with Approvals for Material Change of Use

The concept of "material change of use" is one that has caused some confusion amongst inexperienced developers, particularly with respect to the lapsing provisions in section 341. The term was introduced into Queensland planning law with the IPA, and has continued through the SPA.

The important question to consider when examining whether or not an approval for MCU has lapsed is whether or not the "change of use" has occurred within the relevant period. If the change of use has not occurred, then the approval lapses.

It is not sufficient to start, or even substantially complete, construction of the buildings and structures associated with the use. This was made clear by the Court of Appeal in McDonald v Douglas Shire Council.10 There, a planning consent under predecessor legislation had been granted for a recreational resort and convention centre. Construction work had commenced, but the use of the land as a resort had not commenced within the requisite four years. The Chief Justice observed:

"I do not consider that "the erection of a building" should be regarded as the subject of the approval. Any erection of buildings was simply a step towards fulfilment of the purpose of the approval, which was use of the land as a resort. That use was the real "subject of the approval", not the erection of buildings taken alone. ... In my view the use of land as a resort, being the subject of the approval, not having commenced within the prescribed period, the consent must be taken to have lapsed.11"

A relatively recent example of the confusion surrounding the commencement of use is Flamingo Enterprises Pty Ltd v Sunshine Coast Regional Council12, which was a decision under the now repealed IPA. That case involved a multi-unit residential development for which an MCU approval had been obtained in February 2005. After commencement of construction, Flamingo Enterprises lodged a second MCU application for an additional two multiple unit dwellings, an extension of the gross floor area for the restaurant, and other incidental changes. A second MCU approval for those aspects was granted in March 2009. The building was largely complete, but was not functioning or occupied, when the currency period for the first MCU approval expired in February 2009. Accordingly, the Council refused to approve a building format plan for the development, as the use had not commenced and no extension had been granted to the currency period of the first MCU approval.

Flamingo Enterprises accepted that the currency period had ended, but argued that because the development was "substantially started" within the four year period, the first MCU approval had not lapsed. Accordingly, Flamingo Enterprises applied to the Court for a declaration that the MCU approval had not lapsed, or alternatively, that the first MCU approval did not lapse until the second MCU approval lapsed.

Judge Wilson SC disagreed with Flamingo Enterprises. The Court held that the primary determinant was the actual change of use, rather than the steps taken in accordance with the development approval including, for example, building work required to make the change of use. Flamingo Enterprises failed to establish that the approved change of use had occurred before the expiration of the currency period, which had not been extended. Accordingly, the carrying out of the MCU would constitute a development offence (in the nature of carrying out assessable development without an effective development permit).

The outcome in the Flamingo Enterprises case may seem unfortunate, however it is for this very reason that the SPA (and previously the IPA) contains a provision allowing a developer to apply to extend the relevant period (or currency period) for a development approval. Failing such an extension, the development approval lapses, and a developer's only recourse is to either re-lodge a development application seeking a new development approval, or apply to the Court for appropriate declarations and orders seeking to revive the lapsed development approval.

Excusal Power of the Planning and Environment Court

Given the difficulties associated with the complex and often arbitrary provisions of the SPA and its predecessor legislation, it is no surprise that applicants, local governments and referral agencies often make mistakes. The consequences for such mistakes can be dire, leading to substantial cost and time delays for the developer. For this reason, the Planning and Environment Court has long had the jurisdiction to excuse mistakes and errors, and deal with such mistakes "in the way the court considers appropriate".

The previous excusal power in section 4.1.5A of the IPA had from time to time been generously construed by the Court to forgive or repair non-compliance with the IPA's provisions. Before its repeal, section 4.1.5A of the IPA provided as follows:

"4.1.5A How court may deal with matters involving substantial compliance

  1. Subsection (2) applies if in a proceeding before the court, the court:
    1. finds a requirement of this Act, or another Act in its application to this Act, has not been complied with, or has not been fully complied with; but
    2. is satisfied the non-compliance, or partial compliance, has not substantially restricted the opportunity for a person to exercise the rights conferred on the person by this or the other Act.
  2. The court may deal with the matter in the way the court considers appropriate."

On its face, allowing the Court to "deal with the matter in the way the court considers appropriate", conferred a very broad discretion on the Court to address a situation where a development application or development approval lapses. However, towards the end of the IPA's life, the Court of Appeal read down the provision, and much emphasis was placed on whether or not there was "a requirement" of the IPA which had not been complied with.13This was precisely the situation in the Flamingo Enterprises case, where an order was sought from the Court excusing the non-compliance with the requirements of the IPA. In line with the Court of Appeal authority, the Court found that it was not a "requirement" under the IPA for a person with an MCU approval to request an extension to the currency period, as that was something entirely within Flamingo Enterprises' own discretion.

Under the IPA, the Court had the power to revive a development application that had lapsed, usually ordering that the development application be remitted back to a certain point in the IDAS process.14 Applying to the Court to revive a lapsed development application was often successful if the applicant could point to "a requirement" of the IPA that had not been complied with, and if all parties to the proceedings supported the exercise of discretion. However, generally, the Court's power under the IPA did not extend to reviving lapsed development approvals. This was because the IPA did not make it "a requirement" to act on a development approval, as the Court held in Flamingo Enterprises.

Upon the commencement of the SPA, the excusal power in section 440 became unquestionably broader in its application than its predecessor section 4.1.5A of the IPA. Section 440 provides as follows:

"440 How court may deal with matters involving noncompliance

  1. Subsection (2) applies if the court finds a provision of this Act, or another Act in its application to this Act, has not been complied with, or has not been fully complied with.
  2. The court may deal with the matter in the way the court considers appropriate.
  3. To remove any doubt, it is declared that this section applies in relation to a development application that has lapsed or is not a properly made application."

It is important to recognise that the words "a requirement" under section 4.1.5A of the IPA have been replaced with "a provision" in section 440 of the SPA. In this regard, the Explanatory Notes to the Sustainable Planning Bill 2009 clarifies the change as follows:

"The purpose of this clause is to ensure a person's rights to hearings are not compromised on the basis of technicalities concerning processes. The term "provision" is intended to be interpreted broadly and is not limited to circumstances where there is a positive obligation to take a particular action."

It is also important to note that subsection 440(3) states that "this section applies in relation to a development application that has lapsed" (emphasis added). "Development application" is a defined term in the SPA, and is quite separate to "development approval" which is also a defined term. Regardless, the Court has recently held that it has the jurisdiction under the SPA to excuse both lapsed development applications and lapsed development approvals.

Reviving a Lapsed Development Approval

The Planning and Environment Court has exercised its powers under section 440 consistent with a broad interpretation of section 440, and has revived a number of lapsed development approvals since the SPA commenced.15 The non-compliance that can be pointed to in such cases is either:

  1. the failure to complete the development approved (i.e. start the use under an MCU approval, or provide the plan for the reconfiguration to the local government under an ROL approval); or
  2. the failure to seek an extension of time prior to the lapsing.

It must be recognised that the Court's power to excuse non-compliance is discretionary. That is, the Court will only revive a lapsed development approval if it considers it appropriate to do so, having regard to all the facts and circumstances of the case.

Accordingly, an application to the Court to revive a lapsed development approval must be supported by reasons sufficient enough to persuade the Court to exercise its discretion in favour of the applicant and excuse the non-compliance. Where an applicant can provide adequate explanation for the non-compliance that resulted in the approval lapsing, and where there is no opposition to the application, the Court has generally exercised its discretion to excuse the non-compliance and revive the lapsed approval.

An example of such a case is the matter of Devy v Logan City Council.16 Devy held an ROL approval which lapsed in August 2009. Both Devy and the Council continued to act as if the approval was still in effect, and indeed the works required under the approval were completed only two months after the date of lapsing. Devy applied to the Court and sought an order excusing the non-compliance. The Council supported the exercises of discretion, and in exercising such discretion to revive the lapsed approval, Judge Rackemann said:

"...the circumstances set out in the affidavit reveal that it was simply a case of an honest mistake which is to be corrected within a reasonable time and in circumstances where the Council has no opposition to the orders being made. In those circumstances, I am prepared to exercise my discretion to make the relevant orders."17

In the matter of La Spina Trabucco Enterprises Pty Ltd v Moreton Bay Regional Council,18 the applicant was a builder that was not experienced in development and was not familiar with the lapsing provisions in the SPA. It had purchased land with the benefit of an MCU approval for multi-unit dwellings which it intended to construct. La Spina Trabucco Enterprises had spent considerable time and money engaging architects, engaging engineers, obtaining other approvals to allow the development to proceed, promoting the sales of the units through a website, registering a community titles scheme, and so on. It was the applicant's mistaken belief that it was only necessary to pay the infrastructure contributions within the relevant period in order to preserve the development approval, and the use was not commenced (nor was construction even commenced) when the approval lapsed. In the circumstances, and taking into account the Council's support, Judge Dorney QC exercised the Court's discretion to revive the lapsed approval.

As stated above, the Court's power to excuse non-compliance and revive a lapsed approval is discretionary. From the cases considered by the Court, there appears to be a number of matters that are relevant to the exercise of discretion, including:

  1. the assessment manager's support for, or opposition to, the revival of the development approval;
  2. the explanation for the non-compliance;
  3. the time and cost that has been expended on pursuing the development approved in the approval;
  4. whether it is in the public interest for a new development application to be made;
  5. if a new development application has to be made, the inevitable delays and additional expense that would be incurred; and
  6. whether the interests of other persons not party to the proceeding might be affected.

In relation to this last point, it is noted that the jurisdictional requirement under section 4.1.5A of the IPA (that the Court be satisfied that the opportunity for a person to exercise rights has not been substantially restricted) has been removed from section 440 of the SPA. Nonetheless, such a consideration is still a factor relevant to the exercise of discretion under the SPA.

7.8 In reviewing these cases, it is clear that the legislature's intention to expand the ambit of the Court's excusal power has been reflected in the Court reviving lapsed development approvals. This is especially so where section 440 only refers to "a development application that has lapsed", and the Court is prepared to interpret the provision broadly enough to encompass development approvals that have lapsed. It would be interesting to see the outcome if the Flamingo Enterprises cases was considered under the excusal power in section 440 of the SPA, as opposed to the more restrictive section 4.1.5A of the repealed IPA.


The lapsing provisions in the SPA, both for development applications and development approvals, are necessary. However, they often lead to confusion not only for developers but also for assessment managers.

The SPA recognises that there may be minor administrative oversights in the IDAS process, which can now be 'cured' by notifying the assessment manager of the applicant's intention to revive the application and then taking the necessary action to continue the IDAS process. This 'IDAS revival process' means that the development application is taken not to have lapsed.

However, there is only a short five business day period within which the IDAS revival process can be used. Outside this period, the only options to revive a lapsed development are to make an application to the Planning and Environment Court, or to lodge a fresh development application.

The Court has long had the power to revive a lapsed development application, often sending the application back to a certain point in the IDAS process. However, upon commencement of the new excusal power in section 440 of the SPA, the Court has interpreted the provision very broadly and held that it has the power to excuse a lapsed development approval, despite the wording of the section expressly referring to "a development application that has lapsed".

The expanded power comes with a sigh of relief from the development industry. Not only are the lapsing triggers in the SPA (and previously the IPA) often confusing, but they were previously coupled with an excusal power in section 4.1.5A of the IPA that could only be enlivened where "a requirement" of the IPA could be identified.

Under the SPA, the Court has the discretion to revive both lapsed development applications and development approvals. However, as the power is discretionary, it will require the provision of a reasonable explanation for the non-compliance, and it is important that there be no opposition to the application.


1Section 266
2Section 273
3Section 279
4Section 302
5Section 302
6Section 341(1)(a)
7Section 341(2)(a)&(b)
8Section 341(3)(a)
9Section 383
10(2003) 126 LGERA 96
11At 100
12[2010] QPELR 207
13See for example Fawkes Pty Ltd v Gold Coast City Council [2008] 1 Qd R 1, and Barro Group Pty Ltd v Redland Shire Council & Ors (2009) 169 LGERA 326
14See for example National Properties Group v Toowoomba City Council & Anor [2008] QPELR 40, Muir & Anor v Logan City Council & Ors [2008] QPELR 552, and Walker & Ors v Logan City Council [2010] QPELR 490
15See for example Tremellen & Tremellen v Southern Downs
Regional Council & Ors [2011] QPELR 56, Wallace & Anor v Logan City Council [2010] QPEC 66, and Larrell Pty Ltd v Brisbane City Council [2011] QPEC 113
16[2011] QPELR 112
17At 113
18Unreported, Appeal No. BD3167 of 2011, 22 September 2011

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

Some comments from our readers…
“The articles are extremely timely and highly applicable”
“I often find critical information not available elsewhere”
“As in-house counsel, Mondaq’s service is of great value”

Mondaq Advice Centre (MACs)
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.