AIM SHIELD Emergency
Coordinated vulnerability disclosure

AIM SHIELD disclosure policy

If you have found a security flaw in something of ours, this is how to tell us, what we promise and what we ask of you. You have safe harbour if you act in good faith.

Report a flaw

In brief

  • Write to us at seguridad@aim-shield.ai. Contact and policy also in security.txt.
  • We acknowledge receipt within 5 working days and, within 10 calendar days, we tell you whether we accept it as valid.
  • We ask for 90 days from your first report to fix it before you make it public.
  • If it is already being exploited, we fix it as a priority and notify the authorities within 24 hours, as the Cyber Resilience Act requires.
  • We will not take legal action against anyone who investigates in good faith under this policy.

Introduction

AIM SHIELD is grateful when researchers and the general public help us improve our security. If you think you have found a vulnerability, a privacy problem, exposed data or another security flaw in anything of ours, we want to know. This policy explains how to tell us, what we expect of you and what you can expect from us.

What is included

This policy covers the digital systems that are ours, that we operate or that we maintain:

  • The website www.aim-shield.ai and its services, Check's public API, the browser extension and AIM SHIELD's add-ons.

What is not ours is out of scope: a flaw you find in another company's system must be reported to that company or to the relevant authority.

What is excluded

  • Systems or equipment that do not belong to those taking part in this policy.
  • Social engineering attacks on people on our team or among our customers.
  • Tests that overload the service (denial of service), mass sending of messages or physical attacks.
  • Automated reports with no proof that the flaw exists, or about settings with no real effect on security.

What we commit to doing

If you work with us under this policy, you can expect us to:

  • Reply to you with an acknowledgement of receipt within 5 working days at most and work with you to understand and validate your report.
  • Within 10 calendar days we tell you whether we accept the flaw as valid and how we will handle it.
  • Keep you informed of progress until it is fixed.
  • We will fix the flaws discovered within a reasonable time, within our means: anything being actively exploited, as soon as possible.
  • Credit you in the security advisory if you wish (and not, if you prefer us not to).
  • Let us extend the safe harbour below to your research related to this policy.

What we ask of you

To take part in good faith, we ask that you:

  • You follow this policy and any other agreement that applies. If there is a contradiction, this policy prevails.
  • Tell us about the flaw as soon as you discover it.
  • Do not violate other people's privacy, do not disrupt our systems, do not destroy data and do not harm other users' experience.
  • You use only the official channels to talk to us about the flaw.
  • Give us a reasonable period, of at least 90 days from your first report, to fix it before making it public. If we fix it sooner, we can agree to publish sooner. If it is being actively exploited, we can agree a shorter period.
  • Test only the systems included and respect those that are excluded.
  • If the flaw gives you access to data by accident, access only the minimum needed to demonstrate it and, if you come across user data (personal, health, card or confidential data), stop and send us the report immediately.
  • Test only with your own accounts or with the express permission of their owner.
  • Do not try to extort us.

Official channels

Tell us about a security flaw by email at seguridad@aim-shield.ai, with as much information as you can: the more detail, the sooner we can classify and fix it. It helps if it includes what you found, where, the steps to reproduce it and what impact you think it has.

Coordinated disclosure

We work with whoever alerts us to agree when and how the flaw is made public. By default, we publish a security advisory when there is already a fix or, at the latest, 90 days after your first notice, whichever comes first. If the flaw is in a component belonging to another person or company, we also tell whoever maintains it.

Safe harbour

If you carry out research under this policy, we consider your research to be:

  • Authorised with regard to the rules against unauthorised access to systems, and we will not start or support legal action against you for accidental, good-faith breaches of this policy.
  • Authorised with regard to the rules against circumventing technical protection measures, and we will not make a claim for it.
  • Exempt from the restrictions in our terms of use that would prevent the research, which we lift in a limited way.
  • Legitimate, useful for the security of the internet and done in good faith.

You are still obliged to comply with the law. If a third party takes legal action against you and you have complied with this policy, we will make it known that you acted in line with it. If you doubt that your research fits this policy, write to us through an official channel before continuing.

This safe harbour only covers claims that depend on AIM SHIELD: it does not bind third parties or the authorities.

Frequently asked questions

Is there a financial reward?

We do not have a rewards programme. We will acknowledge your work in the security notice if you wish.

What happens if the flaw is already being exploited?

We fix it as a priority and, if the product falls within the Cyber Resilience Act, we notify the authorities within 24 hours and warn those who use it. Write to us as soon as possible.

Where can I see the flaws that have already been fixed?

In the security notices: /seguridad/avisos, also in CSAF 2.0 and with the VEX of the components.

Where this policy comes from

This policy is based on the disclose.io template, in the public domain (CC0 1.0), translated and adapted into Spanish. It is not legal advice: if you use it for your company, have your adviser review it.

Are you a manufacturer and want your own policy? There is a template in the kit for small manufacturers. Last reviewed: 2026-11-02.