1. Responsible disclosure of vulnerabilities
Design Chama, a single-member private company, accepts responsible reports of potential vulnerabilities affecting https://www.chama.gr. We aim to investigate and address issues safely while protecting visitors and their data.
2. Scope and limits of testing
This policy covers www.chama.gr and systems the company is legally authorised to manage. It gives no general permission to scan, access or exploit systems and does not extend to the infrastructure of Framer, Google or other third parties. If you are unsure whether a test is within scope or lawful, request written clarification first.
3. Reporting channels
Email your report to security@chama.gr. The alternative contact address is info@chama.gr. Preferred languages are Greek and English.
The published contact details are available in security.txt, in the format specified by RFC 9116. The file includes a link to a PGP key. Before sending encrypted or particularly sensitive information, verify the key’s availability, validity and fingerprint through an independent, verified channel. If you cannot verify it, send only a non-sensitive description first and request a secure way to exchange information.
4. What to include in your report
Describe the affected URL or component, the issue, the conditions under which it occurs and the minimum safe steps to reproduce it. Include the date, the browser and version where relevant, the potential impact and your contact details for follow-up. You may attach de-identified screenshots or other minimal technical evidence.
Keep passwords, access tokens, complete user files and third-party data out of your report. Avoid obtaining additional access to demonstrate impact. If you inadvertently encounter third-party data, stop immediately, leave the data uncopied and undisclosed, and report the issue using only the information necessary.
5. Prohibited actions
Prohibited actions include exploiting vulnerabilities, gaining unauthorised access, extracting or keeping third-party data, modifying or deleting data, installing malicious code and maintaining access. Denial of service, placing undue load on infrastructure, large-scale automated testing, social engineering, phishing and testing third-party services without their permission are also prohibited.
6. Handling and response times
We aim to acknowledge receipt within 72 hours and complete an initial assessment within seven business days. These are service targets. Resolution depends on severity, reproducibility and any reliance on third parties. If you receive no reply, use the alternative email address.
We assess reports according to risk and may ask for clarification. Coordinate any public disclosure with us to allow a reasonable time for remediation. Keep personal data and details that could enable active exploitation out of any public disclosure.
7. Good faith and safe reporting
The company will not take legal action solely because of a good-faith report that complies with this policy and applicable law, causes no harm and involves neither unauthorised access nor retention of third-party data. The statement binds the company alone. It confers no legal immunity and does not bind third parties or authorities. The company offers no financial reward or bug bounty programme.
8. Data protection and confidentiality
We use contact details and the minimum technical information in the report for investigation, communication, remediation and security records. Access is limited to the people responsible and, where necessary and on a lawful basis, the relevant technical provider or competent authority. Retention must be limited to the time needed for investigation, remediation and any legal obligations or claims. See our Privacy Policy for your rights and contact details.
9. References and updates
This policy and security.txt confer neither a security certification nor permission to test. For the file format and its scope, see RFC 9116. We review this policy when reporting channels or procedures change.
Last updated 16 October 2026

