Your Privacy

CAPA - Centre for Aviation, as a subsidiary of Informa, respects the privacy rights of our users and is strongly committed to protecting your privacy online in compliance with Informa's privacy policy. For more specific detail on CAPA products, please see below.


CAPA Alerts

Data tracked by the CAPA Alerts app include the user's account ID (required to verify subscription access), as well as usage statistics - for example when the app was opened, how long it was in use for, the user's approximate location, time spent on each screen, and which articles were viewed. We use this data to track the performance of articles (overall and by region) and how widely used the app is in-general.

CAPA Events

The CAPA Events App makes use of the Bizzabo events platform. Bizzabo acts as a data processor for CAPA; you can find more information on what they do on our behalf in the Bizzabo privacy policy. The purpose of the app is to make it easier for users to see the upcoming agenda, speaker information and network with other users at the event. Users can view the profiles of other users and be notified when other users view their profile. These options can be disabled in the app settings. Data collected includes approximate location, time spent in-app, and profile views. This data is used to make the app more useful, and to give users a better experience at our events.

CAPA Website

CAPA makes use of cookies and similar technologies (particularly HTML5 local storage) to give you a better experience with this website. A cookie is a small text file that is stored within your browser, and passed back to the server every time a page is requested. This allows websites to differentiate between users, or serve different content depending on what values are in the cookie. HTML5 local storage is a way for websites to store small amounts of data in your browser that can only be read client-side, unless the site contains code to send data from local storage back to the server.

The CAPA website makes use of HTML5 local storage as a cache, so that it can quickly display Alerts settings, use your User ID, and remember your authentication token between browser sessions (ie. if you leave this site or close your browser and open it again, you won't need to log in again). If you are interested in what data we are storing in local storage for this site, you can get a live view of it by clicking here.

Data Collection

CAPA makes use of several technologies to collect data from you as you use the website. They are detailed below. The data collected by these tools is only directly viewable to CAPA and the companies hosting the analytics tools, however it may be disclosed in an anonymous, broad aggregate format in certain situations (ie. a potential advertising client would want to know how many views per month our website gets).

Google Analytics

CAPA uses the industry-standard Google Analytics platform to collect data related to how users are using the site. We use this data in an aggregated form in order to figure out overall site traffic, which types of content are performing well, how long users spend on the site, how long pages take to load, how various marketing campaigns have performed and so on. This data is anonymous, unless you are logged into the site. When logged into the website (and only when logged into the website), your User ID is transmitted to Google Analytics and your activity will be linked to that ID. CAPA can then potentially use that data to identify the product usage of individual users and companies. Agreeing to this tracking is part of the Terms of Service for CAPA Membership and other products.

Informa IIRIS

The IIRIS tracker is a service which helps our parent company (Informa) to track user behaviour across multichannel touchpoints.

It's used to:

  1. Track and understand user behavior across channels such as web, email and mobile.
  2. Understand how users interact with products on site.
  3. Collect, govern and model behavioural data.

Crash Data

The CAPA website is an extremely complex Javascript application, and like all computer applications, it has bugs. There are rare occasions where a data tool or other website feature will cause the website to break in your browser. When this happens, the screen will change to a page that indicates that the site has crashed, and will ask if you'd like to send a message stating what you were doing, for troubleshooting purposes. If you consent to automatic crash data collection, that page will still appear when something breaks, but relevant details will be automatically submitted to CAPA. You can still add a message if you wish (and please do, they're very helpful).

Data collected when a crash occurs:

  • URL - the web page address that the crash occurred on. This helps us quickly narrow the scope of possible crash causes.
  • Error Type - this is the type of the Javascript error, as reported by your browser. It will be something like "TypeError: Cannot read property 'years' of undefined."
  • Error Details - this will contain a list of components that the error occurred within. Due to minification, this list usually isn't helpful, but sometimes it has helped us quickly get to the bottom of where an error is occuring.
  • Browser Type - the web browser user-agent string. We use this to determine whether the bug only affects one brand/version of web browser.
  • Page History - this is a list of the previous pages of the CAPA website you were on in the current browser tab during the leadup to the crash occuring. Pages from outside the CAPA site are not included in this list. We use it to troubleshoot whether something on a previous page triggered a bug that caused a crash on the next page.
  • User ID - if you are logged into the CAPA website, your user ID will be transmitted. This helps us figure out whether it was a particular setting you had under your account that caused the crash.
  • Message - if you've included any message in the crash data submission, this would be it. Note that automatic crash data submission doesn't contain a message.

Crash data is very helpful for our development team when it comes to troubleshooting and fixing bugs with the site. Previously we've used it to solve crash bugs with the financial graphs, traffic graphs, route maps, the Alerts sidebar and many other things.

Last Updated: 09-May-2024