Cookie Policy

Like many other websites, the Apogee Associates Limited website uses cookies. Cookies are small pieces of information that are stored on your computer or mobile device when you visit a website.

The following table outlines what cookies we use and what we use them for:

Cookie names Type of cookie First or Third party Can be blocked Session or Persistent Expiry Time Purpose

Essential or necessary cookies are enabled by default you can block all cookies but some of the functionality of this website may be lost or not display correctly. If you do not consent to these types of cookies, you must turn off cookies or refrain from using the site.

 

Managing Your Cookie Preferences

You can manage your cookie and privacy preferences on this website at anytime using the ‘Cookie Settings’ button or the ‘cog’ icon in the bottom left of your screen.

 

Other Ways of Managing Your Cookie Preferences

You can configure your Internet browser, by changing it’s options, to stop accepting cookies completely or to prompt you before accepting a cookie from the website you visit. If you do not accept cookies, however, you may not be able to use all portions of this website.

Please note that disabling these technologies may interfere with the performance and features of the website.

 

Most browsers also allow you to turn off cookies.

To do this, look at the ‘help’ menu on your browser. Switching off cookies should not overly impair your use of this website but it may not work 100% as intended. Most web browsers automatically accept cookies but, if you prefer, you can change your browser to prevent that or to notify you each time a cookie is set. You can also learn more about cookies by visiting www.allaboutcookies.org which includes additional useful information on cookies and how to block cookies using different types of browser. Please note however, that by blocking or deleting cookies used on our site you may not be able to take full advantage of our site if you do so.

This privacy policy can provide you with further details about how we use any personal information you give us, although not all information captured by using cookies will identify you.

We are continually striving to develop improved ways of managing your cookie preferences. As new technologies and solutions emerge, this cookies policy may be updated to reflect any such advances in technology and preference management tools.

 

5.1. WordPress.com – Jetpack by Automatic

Our website is powered by WordPress and we use Jetpack (plug-in) by Automatic for extra features (statistics and security) below are detailed the elements of Jetpack that we use which may use data and how that data is used. For a better understanding of how Jetpack uses your data, please refer to the Automattic Privacy Notice (Automattic owns and operates the Jetpack plugin), the Automattic Privacy Policy and our detailed What Data Does Jetpack Sync? support article.

Activity Log

This feature only records activities of a site’s registered users, and the retention duration of activity data will depend on the site’s plan and activity type.

Data Used: To deliver this functionality and record activities around site management, the following information is captured: user email address, user role, user login, user display name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com-connected site ID of the site on which the activity takes place, the site’s Jetpack version, and the timestamp of the activity. Some activities may also include the actor’s IP address (login attempts, for example) and user agent.

Activity Tracked: Login attempts/actions, post and page update and publish actions, comment/pingback submission and management actions, plugin and theme management actions, widget updates, user management actions, and the modification of other various site settings and options. Retention duration of activity data depends on the site’s plan and activity type. See the complete list of currently-recorded activities (along with retention information).

Data Synced (?): Successful and failed login attempts, which will include the actor’s IP address and user agent.


Protect

Data Used: In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.

Activity Tracked: Failed login attempts (these include IP address and user agent). We also set a cookie (jpp_math_pass) for 1 day to remember if/when a user has successfully completed a math captcha to prove that they’re a real human. Learn more about this cookie.

Data Synced (?): Failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information.


WordPress.com Stats

Data Used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Important: The site owner does not have access to any of this information via this feature. For example, a site owner can see that a specific post has 285 views, but he/she cannot see which specific users/accounts viewed that post. Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.

Activity Tracked: Post and page views, video plays (if videos are hosted by WordPress.com), outbound link clicks, referring URLs and search engine terms, and country. When this module is enabled, Jetpack also tracks performance on each page load that includes the Javascript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites in order to make sure that our plugin and code is not causing performance issues. This includes the tracking of page load times and resource loading duration (image files, Javascript files, CSS files, etc.). The site owner has the ability to force this feature to honor DNT settings of visitors. By default, DNT is currently not honored. (We have enabled this on our website).