Cookie Policy

This is also available as a download in the Resources and Support section of our website.

Introduction.

At Beyond Encryption we are committed to protecting the data that we collect about all our users. The information as outlined in this policy aligns to the principles as set out in our Privacy Policy. This details on how and why we use cookies. By using our site and applications you agree that this policy applies.

You accept that we may make changes to our website and apps and we may make changes to this policy too. Any updates to our cookie policy will be available on our website and are effective immediately from the date published. You confirm your acceptance of any changes to this policy by continued usage of our website and applications (apps).

What are cookies?

Cookies are small files that contain a string of characters (text) that are downloaded to your device (e.g. computer or smartphone) browser from our website’s server when you use our site or apps. The cookie contains a unique identifier, but it does not contain personally identifiable information such as your name or your email address. The browser stores the cookie on your computer’s hard drive and sends this back to our site whenever you return this may be accessed next time you visit the site.

What is the function of cookies?

The Beyond Encryption website uses cookies to improve user experience by:

  • allowing an automated access to your previously stored account information and preferences to deliver a more personalised service.
  • providing customer and site analytics so that we can review and optimise the service based on for example usage patterns and audience size.
  • initiating security measures such as “time out” when you have been inactive on the site for a period of time.

What if you don’t want to accept the cookies that we use?

If you disable all cookies, then you will be unable to sign into your Mailock account. Although as with all websites, you can block or restrict the cookies set by our site, if you do so this, it is on the understanding that this will impact on the functionality and your access to our website. Blocking or restricting the cookies from our site will need to be performed on each browser and each device that you use to access our website.

If you would like to:

  • delete any cookies that are already on a device, you will need to locate the file or directory that the cookies are stored in.
  • block them. Click “Help” in the browser menu on the relevant device to find out how to do this.

Further information about deleting or controlling cookies is available at www.aboutcookies.org.

The different types of cookies that we use.

Session cookies These types of cookie only last for the duration of your visit and are deleted when you close your browser. As a result, these perform relatively simple tasks such as tracking how you move through our site, supporting website security, and recognising your device to ensure that the pages you view are displayed properly.
Persistent cookies These cookies will remain behind after the browser has been closed. They can be used to remember log in information (so that when you come back, it is easier and quicker for you to get in).
First and third-party cookies First party cookies are served by us and our site or app. All other cookies are third party cookies.

The cookies used by Beyond Encryption.

The following table sets out the cookies that we use on our website and apps and why we use them. If a cookie is stated to be a third-party cookie, please check the providers website for more information about it.

beyondencryption.com cookies

Cookie name Duration Description
_gid 24 hours Google Analytics cookies to track users as they navigate the website and help improve the websites usability.
_ga 2 years Google Analytics cookies to track users as they navigate the website and help improve the websites usability.
S Session user session cookie.

beyondencryption.com - third party cookies

Cookie name Third Party Duration Description
1P_JAR Google 30 days used for user tracking and ad targeting purposes.
NID Google 6 months generates a CAPTCHA image to help protect this website from “Spambots”.
ANID Google 11 years Google Advertising tracking cookie.
CONSENT Google 20 years refers to getting permission from our website visitors to collect personal data.
DV Google Session used to collect information about how visitors use our site which we use to make improvements. The cookies enable the collection of information in an anonymous form, including the number of visitors to the site, where visitors have come from and the pages, they visited.
Lang Syndication Session used to store language preferences.
ctm Atlassian 1 year contains a unique ID that references the current session on the website.
_CT_Data Atlassian 1 year counts the number of pageviews or visits of the anonymous visitor for the purpose of enabling the ClickTale software to track the number of pageviews or visits a visitor made on the website.
seg_xid_fd Atlassian 1 year a Segment Analytics generated cookie. The main purpose of this cookie is Performance.
seg_xid Atlassian 1 year a Segment Analytics generated cookie – as above.
_CT_RS_ Atlassian 1 month tracks a user’s behaviour on a webpage.
_gid Atlassian 1 day stores and updates unique value of any pages visited.
_atl_path Atlassian 10 years cross-domain user tracking.
_sio Atlassian 10 years a Segment Analytics generated cookie.
ajs_user_id Atlassian 1 year helps track visitor usage, events, target marketing, and can also measure application performance and stability.
ajs_group_id Atlassian 1 year track visitor usage and events within the website.
atlCohort Atlassian 10 years information about the client browser, the requested page and the server status.
OptanonConsent Atlassian 1 year stores information about the categories of cookies the site uses and whether visitors have given or withdrawn consent for the use of each category. This enables site owners to prevent cookies in each category, from being set in the user’s browser, when consent is not given. The cookie has a normal lifespan of one year, so that returning visitors to the site will have their preferences remembered. It contains no information that can identify the site visitor.
ajs_anonymous_id Atlassian 1 year counts how many people visit a certain site by tracking if you have visited before.
_ga Atlassian 2 years is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the site’s analytics reports.
optimizelyEndUserId Atlassian 6 months user identifier.
WRUIDAWS Atlassian 1 year tracks user’s behaviour on a web page.
bxp_gateway_request_id Atlassian 30 seconds info re the client browser, the requested page and the server status.
seg_xid_ts Atlassian 1 year a segment analytics generated cookie.
_gat Twitter 10 minutes limits the collection of data on high traffic sites.
_gid Twitter 1 day stores and updates a unique value for each page visited.
ct0 Twitter 4 hours used by Twitter in order to integrate functionality into our website in the form of Twitter feeds and follow buttons. The cookies are used for a variety of purposes including analytics.
external_referer Twitter 7 days helps to display tweets on the site, monitor referral links, used to identify those logged into Twitter and collect data related to the Twitter platform.
eu_cn Twitter 10 seconds helps to display tweets on the site, monitor referral links, used to identify those logged into Twitter and collect data related to the Twitter platform.
_twitter_sess Twitter Session lets website visitors use Twitter-related features from within the web page they are visiting.

Google Analytics

We use Google Analytics to provide us with non-personal site analytics which help us to improve our site. Google Analytics tracking uses cookies in order to provide meaningful reports about your visit and that of our other visitors to our site, but they do not connect personal data about you. Google Analytics sets or updates cookies only to collect data required for the reports. Additionally, Google Analytics only uses first-party cookies which means any cookies set by it cannot be altered. Further information on Google Analytics can be found at https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage.

besecuremail.com cookies

Cookie name Duration Description
.AspNet.Consent 1 year cookie consent.
ARRAffinity Session used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
BeyondEncryptionWebAntiForger
BeyondEncryptionWebsiteAuth
BeyondEncryptionWebsiteAuthC1
BeyondEncryptionWebsiteAuthC2
Session protects against cross-site request forgery attacks by assigning each user a unique identifier which can verify legitimate requests to this website.
ai_session 30 mins collects statistical usage and telemetry information for apps built on the Azure cloud platform. This is a unique anonymous session identifier cookie.
ai_user 1 year collects statistical usage and telemetry information for apps built on the Azure cloud platform. This is a unique user identifier cookie enabling counting of the number of users accessing the application over time.

besecuremail.com - third party cookies

Cookie name Third Party Duration Description
_ga Vimeo 2 years used to calculate visitor, session and campaign data for the site’s analytics reports.
player Vimeo 6 months generates a CAPTCHA image to help protect this website from “Spambots”.

All of the Atlassian cookies for beyondencryption.com are also on this site.

identity.beyondencryption.com cookies

Cookie name Duration Description
.AspNetCore.Antiforgery Session protects against cross-site request forgery attacks by assigning each user a unique identifier which can verify legitimate requests to this website.
.AspNetCore.Identity.Application Session used to keep you logged in to the website. It expires when you leave the website or if you check “Remember me” it will expire after 1 hour of inactivity. The server will always invalidate the cookie after 1 hour of inactivity, regardless of whether the web browser holds on to it.
.AspNetCore.Session Session uses a store maintained by the app to persist data across requests from a client. The session data is backed by a cache and considered ephemeral data - the site should continue to function without the session data.
ARRAffinity Session used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
idsrv.session Session used in determining whether the user has a valid session.

admin.beyondencryption.com cookies

Cookie name Duration Description
ARRAffinity Session used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
CompanyAdminAntiForgery
CompanyAdminAuth
CompanyAdminAuthC1
CompanyAdminAuthC2
CompanyAdminSession
Session protects against cross-site request forgery attacks by assigning each user a unique identifier which can verify legitimate requests to this website.

V3. This Policy was last updated June 2019.