Turkey KEP System Records: What It Does and Doesn’t Prove

Updated 5 November 2026 · Standard formula, shown below

Turkey KEP System Records: What It Does and Doesn't Prove

This article explains what the Turkey KEP (KayÄ±tlÄ± Elektronik Posta, or Registered Electronic Mail) system records in its audit logs and, just as importantly, what those records do not prove in legal or practical terms. The KEP system stores verifiable metadata about the sending, delivery, and receipt of electronic messages, but it does not record the content of the message itself, nor does it prove that the recipient actually read or understood the message.

Background: What Is KEP?

KEP is Turkey’s legal equivalent of a notarized or registered physical letter, established under the Electronic Communications Law (Law No. 5809) and regulated by the Information and Communication Technologies Authority (BTK). Authorized service providers (KEP hizmet saÄŸlayÄ±cÄ±larÄ±) operate the system, which became operational in 2011. A KEP message is an email with enhanced security: it is digitally signed, time-stamped, and stored in a way that creates a legally binding record of the exchange.

The core idea is that when you send a KEP message, the system produces a receipt (iletim raporu) that proves the message left your account, was accepted by the provider, and was delivered to the recipient’s KEP mailbox. This receipt is the key legal artifact. It is not a simple email read receipt; it is a cryptographically signed document that can be presented in court.

How the KEP System Records Messages

When a user sends a KEP message, the system performs several steps, each of which is logged:

Authentication: The sender’s identity is verified using a qualified electronic certificate (Nitelikli Elektronik Sertifika) issued by a certified certificate authority.
Time-stamping: A trusted time-stamp is applied at the moment of sending, creating a precise chronological record.
Encryption and digital signing: The message content is encrypted and signed with the sender’s private key, ensuring integrity and non-repudiation.
Delivery tracking: The system tracks the message through its servers, recording when it is accepted, when it is delivered to the recipient’s mailbox, and when the recipient’s system sends back an acknowledgment.
Receipt generation: A delivery receipt (alÄ±ndÄ± raporu) is generated and sent back to the sender, containing the message ID, timestamps, and the status (delivered, not delivered, etc.).

All this metadata is stored in the KEP system’s audit log, which is retained for a legally mandated period (typically 10 years). The log entries are themselves digitally signed and time-stamped, making them tamper-evident.

What the Records Prove

The KEP records provide strong evidence for the following facts:

That a message was sent: The system proves that a specific KEP account (identified by its address and certificate) initiated a message at a specific date and time.
That the message was delivered: The delivery receipt proves that the message reached the recipient’s KEP mailbox. This is equivalent to a physical letter being placed in the recipient’s post office box, not necessarily handed to them personally.
That the message was not altered: The digital signature and hash ensure that the content, as stored, is exactly what was sent. Any modification would invalidate the signature.
That a specific recipient account exists: The system verifies that the recipient’s KEP address is valid and active at the time of sending.

In legal disputes, these records are often sufficient to shift the burden of proof. For example, if a company sends a termination notice via KEP and receives a delivery receipt, the company can argue that the notice was legally served, even if the recipient claims they never read it.

What the Records Do NOT Prove

There are several important limitations to what KEP logs can establish:

That the recipient read the message: KEP does not provide a ‘read receipt’ like some email systems. The delivery receipt only confirms that the message was placed in the recipient’s mailbox. The recipient may have deleted it without opening, or their email client may have auto-archived it.
That the recipient understood the message: The system cannot verify comprehension. A message in a foreign language, or one containing complex legal jargon, is still ‘delivered’ even if the recipient misinterprets it.
That the content is true or accurate: KEP only proves that a message was sent and delivered; it does not validate the factual claims inside the message. A false invoice or a fabricated contract sent via KEP is still a false document, just with a verifiable delivery trail.
That the sender was authorized to act: The system verifies that the sender’s certificate is valid, but it does not prove that the sender had the authority to represent a company or make a legal commitment. That is a separate question for the court.
That the message was read at a specific time: The timestamps refer to system events (send, delivery), not to human actions. There is no record of when (or if) a human opened the message.

Common Misconceptions and Mistakes

A frequent misconception is that KEP is like a ‘read receipt’ in Gmail or Outlook. It is not. The delivery receipt is generated by the KEP server, not by the recipient’s email client. Even if the recipient’s mailbox is full, or their account is inactive, the system will still record a delivery attempt and generate a receipt indicating ‘delivered’ if the message is accepted by the server.

Another common mistake is assuming that a KEP message is legally valid only if the recipient opens it. In Turkish law, the legal effect of a KEP message is tied to delivery, not to reading. This is similar to how a physical registered letter is considered served when it is delivered to the address, even if the addressee refuses to sign for it.

Users also sometimes confuse the KEP delivery receipt with the message content. The receipt is a separate document that contains only metadata (sender, recipient, timestamp, message ID, status). It does not contain the body of the message. To prove what was actually said, you must keep the original message file (the .eml or .kep format) along with the receipt.

How to Use KEP Records Effectively

To get the full legal benefit from KEP, follow these practices:

Always save the original message and the delivery receipt. The receipt alone proves delivery, but the message content proves what was said. Store both in a secure, accessible location.
Check the delivery status carefully. If the status is ‘delivered’ (teslim edildi), you have a strong case. If it is ‘not delivered’ (teslim edilmedi), you may need to use an alternative method of service.
Use KEP for time-sensitive notices. Contracts, termination notices, invoices, and legal warnings are ideal. The time-stamp is critical for deadlines.
Do not rely on KEP for informal communication. It is a formal channel; using it for casual messages is wasteful and may create unintended legal obligations.
Verify the recipient’s KEP address before sending. Sending to an incorrect address will result in a ‘delivery failed’ receipt, which is of little use.

Frequently Asked Questions

Does KEP prove that the recipient read my message?
No. KEP only proves that the message was delivered to the recipient’s KEP mailbox. It does not track whether the message was opened, read, or understood. The legal presumption is that delivery equals service, but not that the content was consumed.

Can I use a KEP delivery receipt as evidence in court?
Yes. The receipt is a legally recognized electronic document with a qualified electronic signature. It is admissible as evidence in Turkish courts and carries a presumption of authenticity, similar to a notarized document.

What happens if the recipient’s KEP mailbox is full?
The system will attempt delivery and generate a receipt. If the mailbox is full, the status will likely be ‘delivery failed’ (teslim edilemedi). In that case, the sender should use another method of service (e.g., a notary public) and keep the failed receipt as proof of the attempt.

Is a KEP message legally equivalent to a notarized letter?
In most cases, yes. KEP was designed to have the same legal weight as a notarized letter for the purpose of formal notifications. However, some specific legal procedures (e.g., certain court filings) may still require physical notarization. Always check the specific legal requirement.

How long are KEP records stored?
Service providers are required by regulation to retain KEP records for at least 10 years. This includes the message metadata, delivery receipts, and audit logs. Users are advised to keep their own copies as well, since the provider’s retention period may not cover all needs.

Can I delete a sent KEP message?
No. Once sent, a KEP message cannot be deleted or retracted by the sender. The system’s integrity relies on immutability. You can, however, send a follow-up message to correct or clarify the original.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.