This text is under legal review and awaiting final approval.
The data controller's title and contact details appear here once entered.
Technical and Organisational Measures
Version 1.2 · Effective: 15 November 2026
This document summarises the technical and organisational measures Gemy applies to protect personal data, within the frame of Article 12 of KVKK and the Authority's Personal Data Security Guideline. There is no independent audit or certification (ISO 27001, SOC 2); what follows is based on an OWASP ASVS 5.0 Level 2 self-assessment and the product's automated tests. Some chapters of the self-assessment are met “partly” and the open work is written down.
Scope and verification
- The measures cover both this website and the product application; the product side is broader and is checked by automated tests in every release.
- An attacker-minded internal pre-assessment penetration test was carried out in October 2026: no critical findings; all high and medium findings were closed with regression tests. An independent penetration test is planned and its results will be recorded here.
- Code scanning, dependency audit, image scanning and cross-company isolation tests run in every release; a high finding stops the release.
Access control and tenant isolation
- In the product every company's data is marked with its company id in the database and row-level security is enforced; the company context is derived from the session, never from a client-supplied value.
- Permissions are role- and scope-based; the server decides which buttons appear, the interface only draws them.
- Support access requires the company admin's time-limited approval, covers only a configuration summary and is written to the audit trail.
- Signing in to the site admin panel requires two-step verification; the panel session ends after 12 hours.
Authentication and sessions
- Passwords are stored one-way (Argon2); PINs are salted and peppered with a server-side secret; repeated wrong attempts trigger an increasing lock.
- Two-step verification (TOTP) with backup codes for e-mail sign-in; passkeys for administrators.
- Sessions are limited by absolute and idle timeouts; a password reset closes all of the person's sessions.
Encryption and secrets
- Connections are encrypted with TLS; HSTS and a per-request nonce content security policy (CSP) are applied.
- Encrypted fields use AES-256-GCM with HKDF key derivation; the key rotation script covers every encrypted field.
- Secrets are read from the environment file and never logged; the production image contains no source code, test data or secrets.
- Critical approvals are kept in a linked evidence chain; later changes are detected.
Application and network security
- Every input is validated against a schema; database queries are parameterised; output is escaped.
- Request, body and rate limits are applied; a bot check runs on form submission.
- The database sits on an internal network closed to the internet; outgoing requests pass through a single client that blocks requests to internal addresses.
- Uploaded files are checked for content and extension with virus scanning switched on; files are reached only with a session and a permission check on every request.
Backup and continuity
- Backups are encrypted and their integrity list is signed.
- Restore drills run at regular intervals; continuous database archiving can be switched on at install.
Logging, monitoring and masking
- Status changes and critical operations are written to an append-only audit trail; nothing is deleted or updated.
- Personal data and secrets are masked in application logs; tokenised addresses and query strings are hidden in access logs.
- In text sent to AI, the names of people in the company, common first names, staff numbers (a numbers-only staff number only after the word “sicil”), e-mail addresses, phone numbers, Turkish ID numbers, IBANs and licence plates are hidden; a surname on its own, names that are not in the company and not common, and other personal details typed into free text (such as an address or a health condition) are not; special-category data is never sent.
Supply chain and releases
- Dependencies are installed from the lock file; high and critical vulnerabilities stop the release; newly published packages are not installed before a 24-hour wait.
- A software bill of materials (SBOM) is produced for every release; the release image is signed and verified before installation.
Incident response and breach notification
- A security.txt address is published for vulnerability reports; the target for critical findings is a first response within 24 hours and a fix or workaround within 72 hours.
- If a personal data breach is detected, as controller we notify the Personal Data Protection Board and the affected people within 72 hours at the latest; where we act as processor in the product, the affected customer is informed without delay and supported in its own 72-hour notification.
Organisational measures
- Access to personal data is limited to job need; staff are bound by confidentiality obligations and data protection rules.
- Written agreements are in place with processor providers; the list of sub-processors is stated in the documents.
- Retention and deletion periods follow a written policy and are rule-based in the product (Personal Data Protection and Processing Policy).
- The measures and this document are reviewed at least once a year.
This document contains no sample or fictional personal data.