
Data privacy compliance: KVKK, GDPR and U.S. state laws in one plan
If your company serves customers in the U.S., Turkiye or the EU, the same customer data can fall under three sets of privacy rules.
01
Is this the right route?
One customer file can fall under three privacy systems. The GDPR reaches non-EU companies that offer goods or services to people in the EU (Art. 3(2)). KVKK covers anyone who processes personal data (Art. 2), and a transfer abroad on the Board's standard contract must be notified to the Authority within 5 business days of signing (Art. 9(5)). In Texas, a covered company answers consumer requests within 45 days.
Who it's for Companies formed in Turkiye that sell in the U.S., U.S. companies with Turkish or European customers or staff, and Turkish groups that set up a U.S. subsidiary.
Key requirements
- EU: the GDPR reaches non-EU companies that target or monitor people in the EU (Art. 3(2))
- Turkiye: a transfer abroad needs adequacy, an appropriate safeguard or a narrow exception (KVKK Art. 9)
- Texas: privacy notice, consumer requests and processor contracts (Bus. & Com. Code ch. 541)
- Breach: notice to the EU supervisory authority within 72 hours where feasible, unless a risk to people is unlikely (GDPR Art. 33)
02
How it works
We list the data you collect, from whom and in which countries (a data inventory).
We decide which country's rules apply to each group of data.
We map where the data goes and which transfer tool fits each flow: an adequacy decision, the KVKK standard contract, the EU–U.S. Data Privacy Framework or standard contractual clauses.
We draft the privacy notice, the KVKK notice (aydinlatma metni), consent texts where they are needed, data processing agreements, and templates for answering customer requests.
Where needed, we help with VERBIS registration and with appointing a data controller representative, together with collaborating independent counsel in Turkiye. We do not act as the representative ourselves.
We write a breach response plan: whom you tell, and by when, in the EU, in Turkiye and in the U.S. states where you have customers.
Typical times
- Breach notice to the EU supervisory authorityWithout undue delay and, where feasible, within 72 hours of becoming aware [1]
- Breach notice to Turkiye's Personal Data Protection Board72 hours from becoming aware; a late notice gives the reasons for the delay [6]
- Breach notice to the Texas Attorney General (250 or more Texas residents)As soon as practicable and not later than 30 days after determining the breach [8]
- Breach notice to affected people in TexasNot later than 60 days after determining the breach [8]
- Notice of a signed KVKK standard contract to the Authority5 business days from the last signature [3]
- Texas: time to cure after the Attorney General's written notice30 days [7]
03
Data privacy compliance: questions people ask
do i need a separate privacy policy for turkish customers
One text written for U.S. law is usually not enough. KVKK lists what the notice must say at collection (Art. 10), the GDPR has its own list (Arts. 13 and 14), and Texas requires a clear, accessible privacy notice (541.102). A single document can work if it has a section that meets each law.
can i transfer employee data from turkey to us servers
Yes, if a KVKK Art. 9 route applies. Unless an adequacy decision covers the destination, one route is the Board's standard contract, used without changes and notified to the Authority within 5 business days of signing (Art. 9(5)). Binding corporate rules and a short list of occasional exceptions are the other routes.
does kvkk apply to a us company
It can. KVKK applies to the natural and legal persons who process personal data (Art. 2). The registry rules cover controllers not resident in Turkiye: they register through a representative before they start processing (Registry Regulation, Art. 5(1)(b)). Exemptions from registration depend on criteria the Board sets (Art. 16(2)).
do us state privacy laws apply to a small company
It depends on the state. Texas excludes small businesses as the SBA defines them, but they still need consent before selling sensitive data (541.002, 541.107). Virginia and New Jersey count consumers: at least 100,000 a year, or 25,000 if the company gets revenue from selling personal data (Virginia: over 50 percent of gross revenue; New Jersey: any revenue or a discount). KVKK or the GDPR can still apply to your Turkish or EU customers.
a customer asked us to delete their data what do we do
First find which law covers the request: the GDPR gives one month, KVKK 30 days and Texas 45 days. Data you must keep by law, such as tax records, may stay: the GDPR erasure right does not apply where processing is needed to meet a legal obligation (Art. 17(3)(b)). Give that reason in your answer.
what do we do in the first 72 hours of a data breach
Record the facts, the effects and the steps taken. Under the GDPR, notify the supervisory authority within 72 hours where feasible, unless the breach is unlikely to result in a risk to people's rights (Art. 33(1)); the Turkish Board expects notice within 72 hours of awareness (Decision 2019/10). U.S. state rules differ: Texas sets 60 days for affected people and 30 days for the Attorney General when 250 or more residents are affected.
does my us company need the eu us data privacy framework
It is one option, not a duty. The EU adequacy decision covers U.S. organisations on the Data Privacy Framework List kept by the U.S. Department of Commerce (Decision (EU) 2023/1795, Art. 1); the EU General Court upheld the decision on 3 September 2025, and an appeal to the Court of Justice followed. Without the Framework, an EU exporter can use standard contractual clauses (GDPR Art. 46(2)(c)).
04
Discuss your matter with our team
We map your data, decide which rules apply, draft notices and contracts, set up transfers and request handling, and write a breach response plan. U.S.-law work is done by our U.S.-licensed attorneys; filings in Turkiye such as VERBIS go through collaborating independent counsel in Turkiye. We make no promise about how a regulator will view your program.
Documents to prepare
- A list of the data you collect, from whom, and where it is stored.
- Your current privacy policy, cookie notice and consent texts.
- Contracts with software, hosting and other vendors that handle personal data.
- The countries the data is sent to, including group companies.
- Company documents, and any existing VERBIS record in Turkiye.
- Customer and staff numbers by state and country, to test the thresholds.
- Any log of security incidents and earlier breach notices.
Common reasons for refusal or delay
- Changing the KVKK standard contract: the Board's text must be used as published (Transfer Regulation, Art. 14(3)).
- Missing the 5-business-day notice of a signed standard contract (KVKK Art. 9(5)); it carries an administrative fine (Art. 18(1)(d)).
- Relying on the EU–U.S. Data Privacy Framework when the U.S. recipient is not on the Commerce Department's list (Decision (EU) 2023/1795, Art. 1).
- Treating staff data as outside every law: the Texas and New Jersey laws exclude people acting in an employment role, but KVKK applies to every natural person whose data is processed (KVKK Art. 2).
- Assuming the Texas law ignores small businesses: they still need consent before selling sensitive data (541.107).
- Writing a breach plan after the breach: the 72-hour periods in the EU and Turkiye start when you become aware.
When this is not the right route
- A request about your own personal data: see personal data rights.
- Acting as your EU representative (GDPR Art. 27) or your data controller representative in Turkiye: we do not take these roles.
- Sector rules for health or financial data, and investigations by regulators: this page does not cover them.
- Lawsuits over a breach: this page covers planning and notices, not litigation.
- Forming the company or drafting commercial terms: see company formation and contracts.
Full details
Who this is for
- E-commerce, software and consulting companies with customers in more than one of the U.S., Turkiye and the EU.
- U.S. companies that collect data from customers or staff in Turkiye.
- Turkish companies that form a U.S. subsidiary and move customer or staff data to U.S. systems.
- Companies that need data processing agreements with vendors, software providers or clients.
- Companies that want a breach response plan before an incident happens.
Key requirements
- Which law applies in the EU: the GDPR covers a controller or processor outside the EU when it offers goods or services to people in the Union, whether or not they pay, or monitors their behaviour there (Art. 3(2)). Such a controller designates a representative in writing in a member state where those people are (Art. 27(1) and (3)). This does not apply to a public authority or body, or to processing that is occasional, does not include large-scale processing of special categories of data or criminal-conviction data, and is unlikely to result in a risk to people's rights and freedoms (Art. 27(2)).
- Which law applies in Turkiye: KVKK applies to the natural persons whose data is processed and to the natural and legal persons who process it, by automated means or as part of a filing system (Art. 2).
- Which law applies in U.S. states: the Texas law covers a person that conducts business in Texas or produces products or services consumed by Texas residents, processes or sells personal data, and is not a small business as the U.S. Small Business Administration defines it (Tex. Bus. & Com. Code 541.002(a)). The law does not apply to, among others, state agencies, nonprofit organizations, institutions of higher education, financial institutions subject to the Gramm-Leach-Bliley Act, and HIPAA covered entities (541.002(b)). A small business still needs prior consent before it sells sensitive data (541.107). Virginia covers companies that handle data of at least 100,000 consumers in a year, or 25,000 with over 50 percent of gross revenue from selling personal data (Va. Code 59.1-576(A)). New Jersey uses 100,000 consumers, or 25,000 with revenue or a discount from selling personal data (P.L.2023, c.266, sec. 2).
- Privacy notices: KVKK requires the controller to tell people, when it collects their data, who it is, why it processes the data, to whom and why it may transfer it, how and on what legal ground it collects it, and their Art. 11 rights (Art. 10). The GDPR sets its own list (Arts. 13 and 14). Texas requires a reasonably accessible and clear notice that names the data categories, the purposes, the third parties and how to make and appeal a request (541.102(a)).
- Transfers out of Turkiye: since the 2024 amendment, data may go abroad on an adequacy decision; without one, on an appropriate safeguard such as the standard contract announced by the Board, binding corporate rules or a written undertaking approved by the Board; or on a short list of occasional exceptions (KVKK Art. 9(1), (4) and (6)). The adequacy and safeguard routes also need one of the processing conditions in Arts. 5 or 6 (Art. 9(1) and (4)). A signed standard contract is notified to the Authority within 5 business days (Art. 9(5)), and its text must be used without changes (Transfer Regulation of 10 July 2024, Art. 14(3)). Failing to notify carries an administrative fine (Art. 18(1)(d)).
- Transfers from the EU to the U.S.: the EU adequacy decision of 10 July 2023 covers only U.S. organisations on the Data Privacy Framework List kept by the U.S. Department of Commerce (Decision (EU) 2023/1795, Art. 1). The EU General Court dismissed an action to annul the decision on 3 September 2025 (Case T-553/23), and the applicant appealed to the Court of Justice. Other transfers, or a fallback if the decision is annulled, can rely on standard contractual clauses adopted by the European Commission (GDPR Art. 46(2)(c)).
- VERBIS: data controllers register with the Data Controllers' Registry before they start processing, unless the Board grants an exemption on objective criteria (KVKK Art. 16(2)). A controller not resident in Turkiye registers through a data controller representative, which must be a legal person resident in Turkiye or a Turkish citizen (Registry Regulation, Arts. 4 and 5(1)(b)).
- Processor contracts: the GDPR requires a binding contract that sets out the subject matter, duration, nature and purpose of the processing, the type of personal data, the categories of data subjects and the obligations and rights of the controller, and that binds the processor to the duties listed in Art. 28(3)(a) to (h). The Texas law lists what a controller–processor contract must include, such as clear instructions, confidentiality, and deletion or return of the data when the service ends (541.104(b)).
- Requests from customers: Texas requires at least two secure and reliable ways to submit a request (541.055(a)). Virginia and New Jersey also set 45 days to answer, with one 45-day extension (Va. Code 59.1-577(B)(1); P.L.2023, c.266, sec. 4(a)).
- Assessments in Texas: a controller conducts and documents a data protection assessment of targeted advertising, a sale of personal data, risky profiling, processing of sensitive data and other processing with a heightened risk of harm (541.105(a)).
- Breach notices: under the GDPR, the controller notifies the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to people's rights and freedoms (Art. 33(1)). The Turkish Board reads KVKK's 'as soon as possible' (Art. 12(5)) as 72 hours from awareness, and expects every breach to be documented (Decision 2019/10 of 24 January 2019). In Texas, a business notifies the Attorney General within 30 days when 250 or more Texas residents are affected (521.053(i)), and the nationwide consumer reporting agencies when more than 10,000 persons are notified (521.053(h)).
- Enforcement in Texas: only the Attorney General enforces the privacy law (541.151). It first gives 30 days' written notice to cure (541.154); a violation after that period carries a civil penalty of up to $7,500 each (541.155(a)).
What to check with an attorney
- Which data you collect, from whom, and in which countries: a data inventory.
- Where the data goes: which country, which service provider and which transfer tool.
- Whether you meet the Texas, Virginia or New Jersey thresholds, and whether you sell personal data.
- Whether you need VERBIS registration in Turkiye, or an EU representative under GDPR Art. 27.
- Your current privacy notice, consent texts and vendor contracts.
- Who decides, and who sends the notices, in the first 72 hours of a breach.
Sources and review date
Sources reviewed 18 Nov 2026. Sources below.
Official sources:
- Regulation (EU) 2016/679 (GDPR): Arts. 3, 12, 13, 14, 17, 27, 28, 33 and 46
- Commission Implementing Decision (EU) 2023/1795 (EU–U.S. Data Privacy Framework), Art. 1
- Law No. 6698 on the Protection of Personal Data (KVKK), Arts. 2, 9, 10, 12, 16 and 18 (Turkish)
- Regulation on the Procedures and Principles for the Transfer of Personal Data Abroad (Official Gazette 32598, 10 July 2024), Art. 14 (Turkish)
- Regulation on the Data Controllers' Registry (Veri Sorumlulari Sicili Hakkinda Yonetmelik), Arts. 4 and 5 (Turkish)
- Personal Data Protection Board Decision 2019/10 of 24 January 2019 on personal data breach notification
- Tex. Bus. & Com. Code ch. 541 (Texas Data Privacy and Security Act): 541.002, 541.052, 541.055, 541.102, 541.104, 541.105, 541.107, 541.151 to 541.155
- Tex. Bus. & Com. Code 521.053: Notification required following breach of security
- Va. Code 59.1-576: Scope of the Consumer Data Protection Act
- Va. Code 59.1-577: Consumer rights and response time
- New Jersey P.L.2023, c.266 (N.J.S.A. 56:8-166.4 et seq.), sections 2 and 4
- General Court of the EU, judgment of 3 September 2025, Latombe v Commission, Case T-553/23 (ECLI:EU:T:2025:831)
- Appeal lodged on 31 October 2025 against the General Court judgment in Case T-553/23 (Official Journal C/2025/6610)
Customer data in more than one country?
Monday to Friday, 8:00 a.m. to 5:00 p.m. Eastern Time (ET). We reply in English, Turkish, Chinese, Russian, French, Arabic and more.
Notes
- These are legal deadlines, not predictions. The EU notice is not required when a breach is unlikely to result in a risk to people (GDPR Art. 33(1)). Breach notice rules differ from state to state. ↑