Legal
Security
If you have found a vulnerability in this site, here is how to report it, what you are authorised to do, and what you can expect.
Article 1Purpose
Updated
This policy establishes the channel for reporting a vulnerability of the Site to the Company, the scope and the limits of authorised security testing, the commitments the Company undertakes and the conditions of disclosure.
This policy creates no contractual or employment relationship between the Researcher and the Group, and confers no right to consideration, in accordance with article 14.
Article 2Definitions
Updated
For the purposes of this policy:
- the Researcher means any person who looks for, identifies or reports a vulnerability of the Site;
- the Vulnerability means a defect of the Site or of the systems that serve it which allows information or a function to be accessed without being authorised to do so, its operation to be altered, or its availability or its integrity to be affected;
- the Report means the communication of a Vulnerability with the content required by article 10;
- the Acknowledgement means the confirmation of receipt of the Report provided for in clause 11.1.
Article 3Reporting channel
Updated
The Report is submitted through the form published at the end of this page.
The channel referred to in clause 3.1 is also stated in the security.txt file of this domain, which is where to look first for whom to notify.
A Report submitted by another channel is dealt with all the same, and the time limits in article 11 run from its actual receipt.
Article 4Scope included
Updated
This policy covers calaaglobal.com and the services served from that domain.
Article 5Scope excluded
Updated
This policy does not cover id.calaaglobal.com, cal-1.com or store.calaaglobal.com, which have their own reporting channel.
This policy does not cover the third-party services involved in delivering the Site. A Vulnerability of a provider is a matter for whoever operates it and is to be reported to them.
If the Researcher is in doubt as to whether something falls within the scope of article 4, they give notice before testing, through the channel in article 3.
Article 6Authorisation of testing
Updated
The Company authorises the search for and the demonstration of a Vulnerability within the scope of article 4, always within the limits of article 7.
The authorisation is treated as granted from the moment the Researcher observes those limits, without any need to request it.
The authorisation is granted for the purposes of section 17(5) of the Computer Misuse Act 1990, so that access carried out within the limits of article 7 has the consent of the system owner.
So long as the limits of article 7 are observed, the Company will bring no civil action against the Researcher on account of the test or of the Report, and will not urge a third party to bring one.
The authorisation extends only to the systems within the scope of article 4. The Company cannot authorise testing on the systems of a third party under clause 5.2, and the authorisation in clause 6.1 does not bind whoever operates them.
Article 7Limits of the authorisation
Updated
The authorisation covers testing carried out on accounts and data belonging to the Researcher.
The authorisation does not cover access to the data of another person.
The authorisation does not cover degradation of the service, denial of service or automated mass sending.
The authorisation does not cover social engineering on the staff of the Group or on its suppliers.
The authorisation does not cover physical testing of a facility.
The authorisation does not cover use of the Vulnerability beyond what is necessary to demonstrate its existence and its effect, nor the modification, deletion or extraction of data not belonging to the Researcher.
Article 8Loss of the authorisation
Updated
A breach of any of the limits in article 7 deprives the authorisation of effect in respect of the infringing conduct, from the moment it occurs.
The loss of the authorisation does not affect the commitments in article 11 in respect of a Report already submitted, save in the case covered by article 15.
Article 9Encountering the data of a third party during a test
Updated
If personal data of another person appears during a test, the Researcher stops the test at that moment.
The Researcher does not copy, retain or disclose that data.
The Researcher records the fact in the Report, describing which category of data they had access to and to what extent, without reproducing the data.
Article 10Content of the Report
Updated
The Report states at least what this article lists. The absence of any of these elements does not prevent it from being dealt with, and the Company will ask the Researcher to complete it.
What has been found and at which exact address of the Site.
The minimum steps to reproduce it.
What the Vulnerability would allow a person acting in bad faith to do.
If it has been tested, with which browser and at what time, and whether the situation covered by article 9 arose during the test.
Article 11Commitments of the Group
Updated
The Company acknowledges receipt of the Report within three working days of its receipt.
The Company informs the Researcher, within ten working days of the acknowledgement of receipt, whether it accepts the finding as a Vulnerability and, where it does not, the reasons.
The Company keeps the Researcher informed of the progress of the fix while it is being processed.
The Company publicly credits the Researcher on the terms of article 13, if the Researcher so wishes.
Article 12Coordinated disclosure
Updated
The Researcher undertakes not to make the Vulnerability public during the ninety days following the Acknowledgement.
The Researcher notifies the Company before publishing, in order to coordinate the date.
The Researcher does not disclose what they may have seen belonging to another person during the test, in accordance with clause 9.2, not even once the time limit in clause 12.1 has elapsed.
Once the time limit in clause 12.1 has elapsed, publication of the Vulnerability does not breach this policy, without prejudice to clause 12.3.
Article 13Credit
Updated
The Company publicly credits the Researcher who so wishes, under the name or the pseudonym the Researcher indicates.
The credit is not published without the agreement of the Researcher.
Article 14No reward
Updated
This programme does not pay for the Report.
The only consideration it offers is the credit provided for in article 13, where the Researcher so wishes.
Article 15Inadmissible conduct
Updated
A Report made conditional on a payment, or accompanied by a threat to publish it or to disclose data, is not treated as a security Report.
In the case covered by clause 15.1, neither the authorisation in article 6 nor the commitments in article 11 apply.
Article 16Matters out of scope
Updated
The matters listed in this article are not processed as a Report.
The automated output of a scanner that does not explain why the finding matters on this Site.
The absence of a response header that affects neither the operation nor the security of this Site.
A defect already acknowledged in the accessibility statement in this same section.
A defect of a third-party service, which is a matter for whoever operates it, in accordance with clause 5.2.
Article 17Processing of the data of the Researcher
Updated
The data the Researcher provides in the Report are processed in order to deal with it, to inform them of its progress and, where appropriate, to publish the credit provided for in article 13.
The legal basis is the legitimate interest under article 6(1)(f) of the UK GDPR, consisting in maintaining the security of the Site, and consent under article 6(1)(a) for the publication of the credit.
The complete regime of the processing, including the rights of the Researcher and how to exercise them, is set out in the privacy notice in this same section.
The data in the Report are kept for twenty-four months from the closure of the Vulnerability, a period necessary to evidence its handling and to support the credit provided for in article 13. Once that period has elapsed they are deleted.
Article 18Personal data breaches
Updated
Where a Vulnerability has given rise to a breach of the security of personal data, the Company notifies it to the ICO and, where appropriate, communicates it to those affected, on the terms of article 15 of the privacy notice.
The Researcher is under no obligation to notify anything to the authority, and the Report submitted in accordance with article 3 discharges their duty to cooperate with the Company.
Article 19Relationship with the terms of use
Updated
Testing carried out within the limits of article 7 does not breach the prohibition in clause 11.1 of the terms of use.
Outside those limits, article 11 of the terms of use applies in full, without prejudice to such liability as may arise.
Article 20Modification and version in force
Updated
The version of this policy in force is the one published on this page, bearing the date stated on it.
A modification does not apply retrospectively to a test or a Report prior to its publication.
Report a vulnerability
The four required fields below are the four things this page asks you to describe. A report without steps and without impact cannot be checked, and that is why it cannot be sent.
