This policy explains the principles we at DiesRent have adopted and the measures we apply to protect the confidentiality, integrity and availability of the information we process and the software we provide. In our approach to information security, we are guided by the principles of the ISO/IEC 27001 standard.
1. Purpose
Our purpose is to protect the information of our customers, visitors and business partners against unauthorized access, alteration, loss and misuse, to ensure the continuity of our services, and to comply with the relevant legislation, in particular Law No. 6698 on the Protection of Personal Data (KVKK, Turkey’s data protection law). We assess risks in advance and apply measures in layers.
2. Scope
- the sales website and the design tool at rentacarscripti.com,
- the customer panel and the admin panel,
- the license server, license validation and package distribution infrastructure,
- connections established with payment, email, hosting and AI service providers,
- the security design and updates of the car rental script we sell,
- our employees, business partners and suppliers who access these systems.
The operation of websites running on our customers’ own servers — server security, backups, applying updates and the personal data processed on these websites — is the responsibility of the website owner; our customer is the data controller for these websites. When the customer’s server is accessed during the installation service, DiesRent acts as a data processor and applies the measures in this policy.
3. Core principles
- Confidentiality: Information is accessed only by persons and systems authorized as required by their work.
- Integrity: We ensure that information is accurate, complete and protected against unauthorized alteration; we verify critical data with signatures and hash values.
- Availability: We aim for services and data to be available to authorized users when needed.
- Least privilege and data minimization: We grant only the necessary privileges, process only the data needed for the purpose and do not keep it longer than necessary.
- Security by design: We address security at the software design stage and keep default settings on the secure side.
4. Technical and administrative measures
4.1 Encryption
- Communication between the website and your browser is encrypted with TLS (HTTPS); browsers are instructed to use only secure connections (HSTS).
- Secret keys belonging to payment and service providers, Turkish ID numbers provided for invoicing and hosting, FTP and database access details shared for the installation service are stored encrypted with AES-256-GCM. Turkish ID numbers are shown masked on screens; access details are deleted when the installation is completed.
- Passwords are stored as irreversible hashes (bcrypt/Argon2); for single-use tokens such as password resets, only the hash is kept in the database.
- License server responses and offline license codes are signed with RSA-SHA256. The script verifies the signature with the public key embedded in the package; a response whose signature cannot be verified is not accepted.
4.2 Authentication and access control
- Customer and administrator accounts are separated by role; only authorized administrator accounts can access the admin panel. Records are queried by owner; a user cannot access another user’s order, license or design records.
- Wrong password attempts are counted per account and per IP address; repeated attempts are progressively slowed down and limited.
- The session ID is renewed at login and other sessions are terminated when the password changes; session cookies are sent with the HttpOnly and SameSite attributes and, over a secure connection, the Secure attribute. Form and action requests are validated against cross-site request forgery (CSRF).
- The registration, login, password reset and contact forms are protected against automated (bot) submissions with a hidden honeypot field, a signed timestamp and rate limits, and additionally with Google reCAPTCHA when enabled.
- Access to systems is granted according to job requirements; access is removed for those whose duties have ended.
4.3 Application and server security
- Database queries are parameterized; user input is escaped appropriately for the output context (against SQL injection and XSS). A content security policy (CSP) and other security headers are sent to browsers.
- Uploaded images are validated and re-encoded on the server; scripts are not executed in the upload folder. Design data is passed through an allowlist of permitted values.
- Application folders, keys and logs are closed to web access; error details are not shown in the live environment. Rate limits are applied according to the type of operation.
4.4 License and package security
Personalized installation packages are stored encrypted with AES-256-GCM on the server; they are downloaded from the customer panel via a single-use, IP-bound link valid for 5 minutes and are watermarked with the license key. License validation requests are bound to the domain, the installation ID and a single-use value.
4.5 Payment security
Card details are entered with 3D Secure on PayTR’s secure payment page; DiesRent does not see or store the card number. Notifications from payment providers are accepted with signature verification; no license is created until the payment is verified. Payment transactions are recorded as an audit trail.
4.6 AI security
“Edit with AI” commands first pass through the AI Shield security filter. The AI works only with predefined design operations; it has no access to license, payment, password, server or customer data. Every proposed change is additionally validated on the server and applied in a reversible way. Only the request text and the design data are sent to the service provider.
4.7 Logging and monitoring
Important operations are written to the activity log and failed login attempts to the security records; records are deleted automatically at the end of their retention periods. Raw IP addresses are not stored in visit statistics; a short hash that cannot be linked across days is used.
4.8 Backup and continuity
- Designs are stored both in the browser and on the server, and a version history is kept. Before a new design is sent with “Publish to my site”, an automatic backup is taken on the customer’s website; the previous design can be restored with one click.
- Critical keys such as the license signing key are kept in an area closed to web access and are backed up securely.
- When the license server cannot be reached, customer websites continue to run with the signed offline license code; an outage on our server does not stop customer websites.
4.9 Retention and destruction
Personal data is retained for as long as required by the purpose of processing; records whose period has expired are erased, destroyed or anonymized by an automatic cleanup task that runs every day. Details: Personal Data Retention and Destruction Policy.
4.10 Secure development and the software we sell
- New code is developed according to written security rules and a checklist; automated security tests are run before releases. Dependencies are monitored and security updates are applied; the principle is to use sample data rather than real customer data in tests.
- The car rental script is developed with the same approach: parameterized queries, CSRF protection, a content security policy, a login brake, bot protection for forms, encrypted storage of sensitive information and keeping personal files encrypted outside publicly accessible folders. Security improvements are provided free of charge through updates.
5. Information security incident management
- Detection and assessment: Incidents are detected and recorded through system logs, automatic alerts and reports from users or researchers; the affected systems, data and persons are identified.
- Containment: The relevant access is closed, sessions are terminated, keys and passwords are changed; if necessary, the service is temporarily suspended.
- Remediation and recovery: The root cause is eliminated, systems are brought to a secure state and, where necessary, restored from backup.
- Notification: If personal data is obtained by others through unlawful means, this is notified under KVKK Art. 12/5 to the Personal Data Protection Board (Kişisel Verileri Koruma Kurulu) within the periods set out in the Board’s decisions, and at the latest within 72 hours, from the time the breach becomes known; and to the affected data subjects within the shortest reasonable time. Where we act as a data processor, we inform our customer, the data controller, without delay.
- Lessons learned: A post-incident review is carried out; measures and this policy are updated if necessary.
6. Supplier and service provider security
We select the providers from which we obtain hosting, payment, email delivery, AI and security services by taking into account their security practices, legal compliance and service continuity. We share with providers only the data the service requires, establish connections over encrypted channels and store access keys encrypted. Transfers abroad are made in accordance with KVKK Art. 9. Our active service providers:
| Service | Buyer | Purpose | Location |
|---|---|---|---|
| Hosting (server) service | Our server and data center provider | Hosting the website and its database | Data center named in the service agreement |
| Card payment | PayTR Ödeme ve Elektronik Para Kuruluşu A.Ş. (payment and e-money institution) | Taking card payments, 3D Secure verification, fraud prevention | Türkiye |
| Cryptocurrency payment | Cryptomus | Receiving and verifying crypto payments | Abroad |
| Sending email | Our hosting provider's email server | Delivering order, license, security and support emails | Data center named in the service agreement |
| Accounting and e-Archive invoicing | Financial advisor and e-Archive invoice service provider | Invoicing and statutory bookkeeping | Türkiye |
| Competent public authorities | Courts, public prosecutors, tax offices, the Personal Data Protection Authority (KVK Kurumu) and other competent authorities | Meeting legal requests and obligations | Türkiye |
7. Vulnerability reporting
If you have found a security vulnerability in our systems or software, you can report it to diesrent@diesweb.com.tr. The reporting rules and our approach to good-faith researchers are set out on the Responsible Disclosure Policy page, and machine-readable contact information is available at /.well-known/security.txt. Unauthorized access attempts outside the scope of that policy may constitute offenses under Art. 243–245 of Turkish Criminal Code No. 5237.
8. Continuous improvement
We regularly review this policy and our measures in light of new threats, lessons learned from incidents and changes in legislation, and remedy identified gaps by prioritizing them according to their risk level.
9. Responsibilities
- Management: approving the policy, providing the necessary resources and overseeing its implementation.
- Employees and business partners: complying with confidentiality obligations, protecting access credentials and reporting suspicious situations immediately; breaches are assessed under the relevant contractual provisions.
- Customers and users: using strong and unique passwords, not sharing account details, keeping the purchased script up to date, ensuring the security of their own servers and taking regular backups.
10. Effectiveness and contact
This policy takes effect on the date of publication; its current version is always on this page. For questions, you can write to diesrent@diesweb.com.tr; for applications concerning your personal data, to diesrent@diesweb.com.tr.
You can reach us at diesrent@diesweb.com.tr or via the contact form.