Email is among the most common carriers of personal data. Customer names, phone numbers, delivery addresses, a CV from a hiring round: everything lands in the mailbox and stays there for years. If your company's mailboxes sit on servers in another country, Turkey's data protection law (KVKK) has a name for that: a transfer of personal data abroad.
This article explains in plain language what the rules on KVKK cross-border data transfer mean when you choose an email service. We run email infrastructure; we are not lawyers. Our aim is to help you ask the right questions, so please confirm your decisions with your own legal counsel.
Short answer: If your mailboxes are stored on servers abroad, that will often count as transferring personal data abroad under Article 9 of the KVKK. Since the amendments that took effect in 2024, an adequacy decision or an appropriate safeguard such as a standard contract is required, and a standard contract is expected to be notified to the Authority within five business days of signing. A provider that stores data in Turkey shortens this chain but does not remove every obligation.
Why email can count as a personal-data transfer
Personal data is any information relating to an identified or identifiable natural person. An address like jane.doe@company.com.tr, the sender's name, the subject line and everything in the body can fall under that definition. If the server holding this data is abroad, storing it there, or making it accessible from there, needs a transfer analysis.
We often hear: "but my company is only buying a service." Buying a service does not take you out of the picture. You are the data controller, so choosing the provider is your responsibility. The detail, meaning who transfers to whom and in what capacity, depends on the facts, and that is where counsel comes in.
What the 2024 amendments changed
Law No. 7499 rewrote Article 9 of the KVKK, and the new regime took effect on 1 June 2024. Explicit consent, which used to sit at the centre of the old system, is no longer the main route. The new structure has three tiers:
- Adequacy decision. If the Board decides that a country, sector or international organisation offers adequate protection, transfer is permitted.
- Appropriate safeguards. Without an adequacy decision, a transfer can proceed if safeguards such as a standard contract or binding corporate rules are in place.
- Incidental transfers. If neither applies, limited and specific situations allow occasional, non-repetitive transfers.
The Authority explains how the tiers work on its cross-border transfer page. Treat that page as the primary source, since the text may be updated.
Safeguards: standard contracts and binding corporate rules
For a small business using a foreign cloud email service, the option you meet most often is the standard contract. It is a ready-made text published by the Board and expected to be used without changes. You sign it with the provider.
Binding corporate rules are internal rules adopted by multinational groups for transfers within the group, subject to Board approval. It is rare for a small company to use them directly; if your provider has such a framework, it is worth asking.
One more point: a provider saying "we are compliant" does not end your own obligation. Ask which safeguard they offer, and ask for the document.
Notification duty and timing
If you rely on a standard contract, you must notify the Authority within five business days of all signatures being completed. According to the Authority's announcement, notice can be given in person, through a registered electronic mail (KEP) address or through the Standard Contract Notification Module. Both parties should write their signing dates on the contract text so the Authority can check whether the deadline was met. For the current procedure, see the announcement on the Standard Contract Notification Module.
Failing to notify can lead to an administrative fine. Amounts are revised every year, so we do not quote figures here; look at the Authority's official announcements for the current number.
How in-country storage changes the picture
If your mailboxes are stored in data centres in Turkey, the question of transfer abroad through storage usually does not arise, and you do not have to run the standard-contract notification process for that. That does not finish the job: as controller you still owe notice to data subjects, security measures and retention and deletion rules. And the other side of a conversation may well be abroad, which is a separate analysis.
For the operational side of localisation, such as access, support and customer contracts, see email that keeps data in Turkey. With Postanex, data is stored encrypted in data centres in Turkey on KVKK-compliant infrastructure.
Practical questions for your compliance review
Ask your email provider, in writing:
- In which country and data centre are mailboxes and backups stored?
- From which countries can support staff or third parties access the data?
- If data leaves Turkey, which safeguard is used, and can you see the document?
- Who are the sub-processors, and will you be told when they change?
- When you leave, how quickly and in what form is your data returned or deleted?
Then compare the answers with your own data-controller registry entry, privacy notices and internal inventory. Our related guides may help: email retention periods, KVKK breach notification and, for companies with EU ties, NIS2 and GDPR duties.
This article is for general information only and is not legal advice.
Frequently asked questions
Is it illegal to keep email on servers abroad?
No. But you must meet the conditions of Article 9: an adequacy decision or appropriate safeguards. Which route applies to you depends on the facts, so settle it with your counsel.
Is explicit consent still enough?
After the 2024 amendments, explicit consent is no longer the general route for transfers abroad. Regular transfers need an adequacy decision or appropriate safeguards. Consent now matters mainly in limited, incidental situations.
Who notifies the Authority about a standard contract?
Read the Authority's announcement together with Article 9. In general, the party carrying out the transfer, as controller or processor, is responsible for notification. We suggest stating in the contract which party will notify.
If my data is stored in Turkey, do I have nothing to do?
The transfer burden eases, but the rest of KVKK still applies: notice, security measures, retention and deletion. For correspondence whose other party is abroad, run a separate assessment.
- KVKK
- data transfer
- standard contract
- business email
- personal data