🇬🇧 English 🇷🇴 Română 🇪🇸 Español soon 🇫🇷 Français soon 🇩🇪 Deutsch soon
e
Back

In force since 28 October 2026 · version 1

Security Policy and Vulnerability Reporting

How to report a security vulnerability in einvestitii.ro, what we do with the report and the good-faith research rules.

This document also exists in Romanian. For Professionals, the Romanian version prevails if the language versions differ; for Consumers, unclear clauses are interpreted in their favour. Română

We care about the security of your account and your data. If you have found a vulnerability on einvestitii.ro, please tell us first, so that we can fix it before others exploit it.

1. How to report

  • Write to us at zmentaro@gmail.com. This address is also published in security.txt, in line with RFC 9116.
  • Describe the issue, the affected address (URL), the steps to reproduce it and the possible impact. A screenshot or a minimal example helps.
  • Write in Romanian or English.

2. What we do

  • We confirm receipt within 5 business days at most.
  • We keep you informed about our analysis and the fix.
  • If you wish, we thank you publicly once the issue is fixed. We do not currently have a monetary reward programme.

3. What we ask of you

  • Test only with your own accounts and do not access, change or delete other people's data. If you come across personal data, stop and tell us.
  • Do not attempt denial-of-service (DoS) attacks, social engineering, phishing or physical attacks.
  • Do not run automated scanners that put load on the server.
  • Keep the issue confidential until we fix it, or for no more than 90 days from your report, unless we agree otherwise.

4. Good faith

If you follow the rules above and act in good faith, we consider your research authorised, we will not file a complaint against you over it, and we will work with you to understand and fix the issue. However, we cannot waive the rights of third parties and we cannot guarantee the decisions of the authorities.

5. What is not a vulnerability

Reports that only say a header is missing, with no demonstrated impact; issues in old or unsupported browsers; unfiltered automated reports; and attacks that require physical access to the victim's device.

Document versions

The date from which each version applies and what changed.

  • Version 1 in force