Gå til hovedindholdet
KungoraKungora

Vulnerability Disclosure Policy

Version 1.0.0, gældende fra 8. oktober 2026

Dette dokument findes endnu ikke på dansk. Den engelske tekst gælder.

1. Purpose

The security of Kungora matters to us and to the organisations, journalists and others who use the service. If you find a vulnerability, we want you to tell us, so that we can fix it before anyone exploits it. This policy describes how to report, what you may and may not do, and what you can expect from us.

2. How to report

2.1 Contact

Send your report to security@kungora.com. You can write in Swedish or English. Our contact details and encryption key are also in https://kungora.com/.well-known/security.txt.

2.2 Encryption

Please use our public encryption key for sensitive information. [To be completed: the key’s fingerprint and address.]

2.3 What the report should contain

  1. A description of the vulnerability and where it is, for example the address and parameter.
  2. Steps to reproduce it.
  3. The impact you believe it has.
  4. How we can reach you, if you want us to.

3. Scope

3.1 In scope

  1. kungora.com and its subdomains, including the sign-in and the account for organisations and journalists.
  2. Newsrooms on subdomains we provide.
  3. Our API, feeds and widgets.
  4. Email sent from the service, for example how unsubscribing and links work.

3.2 Out of scope

  1. Organisations’ own domains and servers, beyond how our service responds on them.
  2. Services of our suppliers, for example Hetzner and Amazon Web Services. Report those to the supplier.
  3. Attacks aimed at overloading the service.
  4. Social engineering of our staff or customers, and physical attacks.
  5. Reports based only on automated tools without demonstrated impact, for example about missing HTTP response headers that lead to no concrete risk.

4. Rules for testing

When looking for vulnerabilities you must

  1. only use accounts you created yourself, or that the owner has explicitly allowed you to use;
  2. not access, change or delete others’ data beyond what is needed to demonstrate the vulnerability, and stop and report as soon as you have accessed such data;
  3. not take out or keep others’ data, and delete everything you accessed once the report is done;
  4. not disrupt the service, for example by sending large numbers of requests, emails or notices;
  5. not publish content that reaches anyone but yourself, and not send email to anyone but yourself through the service; and
  6. not tell others about the vulnerability until it is fixed or we have agreed otherwise.

5. Our safe harbour commitment

If you follow this policy in good faith, we will not report you to the police or take legal action against you for your testing, and we consider the testing authorised under our terms. If a third party takes action against you for something covered by this policy, we will confirm that you acted in accordance with it. We cannot give permission on behalf of others, for example for organisations’ own domains or our suppliers’ services, and we cannot bind the authorities.

6. What you can expect from us

  1. We confirm receipt of your report within three working days.
  2. We make a first assessment and tell you our conclusion within ten working days.
  3. We keep you informed about the progress of the fix.
  4. We fix serious vulnerabilities as fast as we can and others within a reasonable time, normally within 90 days.
  5. Once the vulnerability is fixed, we can decide together whether and when it will be described publicly.

7. Recognition

We do not currently run a reward programme. If you wish, we will name you on a list of people who have helped us improve our security.

8. security.txt

Our file https://kungora.com/.well-known/security.txt follows RFC 9116 and gives the contact address, the encryption key, a reference to this policy, preferred languages (Swedish and English) and when the file expires.

9. Changes

We may change this policy. The version in force when you tested applies to your testing.