At DiesRent, we welcome security vulnerabilities in our systems being reported to us responsibly, that is, without being disclosed publicly before they are fixed and without harming our users. This policy explains which systems are in scope, how to make a report, the rules to follow during testing, and our commitments. Our security contact details are also available in machine-readable form in the /.well-known/security.txt file.
1. Scope
- the sales website on the rentacarscripti.com domain; the sign-up, login, password reset, cart and payment steps;
- the customer panel (/panel), the design tool (/olustur) and the on-site APIs they use;
- the license verification API of the sold software and the design synchronization (sync) APIs used with “Publish to my site”;
- the demo sites and demo admin panels hosted on our website;
- the latest version of the sold car rental software that can be downloaded from the customer panel, and the installation wizard. We ask that you verify vulnerabilities in the software on your own licensed installation or in a local test environment.
2. Out of scope
- Our customers’ own installations: Do not test the websites, servers, hosting services or domains of companies that use our software. Report configuration or hosting issues directly to the site owner. If you believe the problem stems from the software’s code, you are welcome to report it to us; however, do not carry out verification on a site that belongs to someone else.
- Denial of service (DoS/DDoS), load and volumetric testing, heavy automated requests or brute-force attempts;
- attempts targeting our employees, customers or business partners through social engineering (phishing, fake calls, etc.);
- attempts to gain physical access to offices, devices or data centers;
- sending unsolicited messages (spam) via forms or other channels;
- reports based solely on a missing “best practice” without demonstrating a concrete exploitation scenario and its impact (e.g. the absence of a particular HTTP security header or an SPF/DMARC record, visible version information, framing protection on pages without sensitive actions, login/logout CSRF);
- automated scanner output without a proof of concept (PoC) and verification;
- issues that only affect your own account (such as self-XSS) or that require outdated browsers and plugins;
- prompt attempts against the AI assistant in the design tool that only affect its text response and have no effect beyond design operations;
- vulnerabilities in the own systems of third-party services (PayTR, Cryptomus, Google, Anthropic, hosting and email providers): report these to the relevant provider. Issues caused by our incorrect integration of these services are in scope.
3. How to report
Send your reports by email to diesrent@diesweb.com.tr. Do not share security vulnerabilities on social media, forums or public support channels. Include as much of the following as possible in your report:
- the type of vulnerability and a short description;
- the affected address (URL), endpoint or parameter; if it concerns the software, the version number and environment details (PHP, database and web server versions);
- step-by-step instructions to reproduce the vulnerability;
- a proof of concept: sample requests and responses, a screenshot or a short video;
- the potential impact: which data or functions can be accessed, and with which privileges;
- your suggested fix, if any, and the name under which you would like to be credited in the acknowledgments.
Do not include passwords, secret keys or personal data belonging to third parties in the report; if such information is needed to demonstrate the vulnerability, mask it. If you would like to send sensitive details in encrypted form, write to us first; we will agree on a suitable method together.
4. Testing rules
- Use only accounts, designs and records that you have created yourself. If needed to test privilege separation, open a second test account of your own; do not try to access other users’ accounts, data or sessions.
- Perform the minimum action needed to prove the vulnerability. Do not download, copy, modify or delete data; showing that access is possible with a single record is sufficient.
- If you notice that you have accessed personal data, payment information or confidential information, stop testing immediately, do not keep this data, do not share it with anyone and report the situation to us right away.
- Do not perform tests that disrupt or slow down the service or affect other users; if you use automated tools, keep the request rate low.
- Do not test the payment steps with fake cards or cards belonging to others, with chargeback requests, or by targeting the systems of payment institutions. If you want to examine the payment flow, contact us first.
- Do not use a vulnerability you find to gain persistence in systems, escalate privileges or move on to other systems; chaining may only be done to the extent necessary to demonstrate impact. Do not leave backdoors or permanent changes, and delete the test content you created when you are done.
- Do not share the vulnerability with third parties until it has been fixed and without our agreement. We ask that you wait 90 days from the date of the report before public disclosure and coordinate the timing of disclosure with us. For vulnerabilities in the sold software, we may ask for a reasonable additional period after the fixed version is released so that license holders can apply the update; if the fix will take longer than 90 days, we will explain why and try to agree on a new date with you.
5. Our commitments
- We aim to confirm receipt of your report within 1 business day.
- We review and verify the report and determine its severity; we share the assessment result and our planned resolution with you.
- We keep you informed of progress during the fix and let you know when the fix is released; if you wish, we ask you to verify the fix.
- With your permission, we thank you by name or pseudonym in the release notes; if you prefer, your report remains anonymous.
- We process the personal data you provide as part of the report only to evaluate the report and communicate with you (see KVKK Privacy Notice).
DiesRent does not run a paid bug bounty program; no money or other material reward is promised in return for reports. Requesting payment in return for a report, or making non-disclosure of a vulnerability conditional on a fee, is not considered good-faith research under this policy.
6. Our approach to good-faith research
We consider security research conducted in good faith and in accordance with this policy to be an authorized activity with respect to our in-scope systems. As long as you comply with this policy:
- we will not take legal action or file a complaint against you because of your research;
- if a third party initiates action against you because of your research, we will confirm in writing, at your request, that your research was conducted in accordance with this policy;
- we will not close your account solely because of research activity that complies with this policy.
This approach applies to the extent permitted by law. Investigations and prosecutions concerning the cybercrimes set out in Art. 243–245 of Turkish Penal Code No. 5237 may not depend on a complaint in every case; the actions of public authorities and the exercise of their own rights by third parties (e.g. payment institutions, service providers, our customers) are not within our control. This policy does not bind third parties and grants no permission for out-of-scope systems. If you are unsure whether an action complies with this policy, consult us by writing to diesrent@diesweb.com.tr before you begin.
7. Fixes and coordinated disclosure
We prioritize verified vulnerabilities by severity, and develop and test the fix. Fixes to the sales website, customer panel and APIs are applied directly to our systems. Fixes to the sold software are released as a new version in the customer panel; the release notes state that it contains a security fix, and license holders are advised to apply the update. Since applying the update is at the license holder’s discretion, for serious vulnerabilities we aim to also inform license holders by email. The timing and content of the public disclosure (affected and fixed versions, acknowledgments) are determined in coordination with you.
If a report shows that personal data has been obtained by unauthorized persons, we will additionally fulfill our notification obligations under Art. 12 of Law No. 6698 on the Protection of Personal Data (“KVKK”).
8. Contact and changes
- Security reports: diesrent@diesweb.com.tr
- Machine-readable security contact file: /.well-known/security.txt
- Non-security matters: diesrent@diesweb.com.tr or the contact form
We update this policy when necessary; the current text is published on this page, and the text in force on the date of your report applies. For our general security approach, see the Information Security Policy page.
You can reach us at diesrent@diesweb.com.tr or via the contact form.