Yaziio logoYaziio

KVKK Notice

Law No. 6698 on the Protection of Personal Data (KVKK), Art. 10 · Last updated: 4 October 2026

This is the English version of Yaziio's Turkish KVKK information notice (KVKK Aydınlatma Metni). It is written for people whose personal data is processed through Yaziio (people who comment on or message an Instagram account, and account owners who use Yaziio). Yaziio is in limited access and under development: the Meta app is not live, automatic replies are switched off and every reply waits for human approval; the processing described below will apply once the service goes live (the compliance features are implemented in the software). Today notifications from Meta (raw event records) and the internal task records created from them are processed.

1. Data controller

Tolga Vuranel. Contact: [email protected]

2. Personal data to be processed (once the service is live)

3. Purposes of processing (once the service is live)

Replying to comments and messages, routing messages by topic, showing conversation history to the account owner, handling course/event/product requests, ensuring the security and continuity of the service and preventing abuse.

4. Legal basis

Your personal data is processed under KVKK Art. 5/2 on the grounds that (c) it is directly related to the establishment or performance of a contract (replying at your request), (f) it is necessary for the legitimate interests of the data controller, provided it does not harm your fundamental rights and freedoms, and (ç) it is necessary to comply with a legal obligation. For processing that requires explicit consent, your consent will be requested separately.

5. Transfers

Once the service is live, your data may be transferred to Meta Platforms (Instagram) to receive and send messages (today we only receive notifications from Meta), to Anthropic to generate replies and classify messages (planned; because no live user data flows, no live data is transferred to Anthropic today) and to infrastructure providers so the service runs securely. Anthropic's servers may be located abroad (United States); this transfer will be made under KVKK Art. 9, with the safeguards required by the legislation.

6. Method of collection

Once the service is live, data will be collected automatically through Instagram's official application programming interface (API), within the authorization the account owner gives Yaziio. Today only the notifications Meta sends to our webhook address are received.

7. Retention period

Message and comment content is kept for 180 days and then deleted: a daily automatic job replaces text that has reached 180 days with "[deleted]" (the record is left only with an identity digest and timestamps, and the raw copy of the message is also cleared); AI call records are cleared at 180 days and the email contact log at 365 days. This automatic deletion is implemented in the software and covered by tests; it will apply once the service goes live and has not yet run on live user data. The limits of its scope are stated below. Where a legal retention obligation exists, data is kept for the relevant period.

Consent records, anonymisation and scope of deletion

Consent records. Consent and refusal records (including DUR) are append-only; they cannot be altered or deleted because they are kept as legal evidence. Even after a deletion request, these records refer to the person only through a digest (hash) reference that does not directly show their identity. Replying to a comment or message on Instagram does not need a separate consent record; marketing DMs and email require explicit consent.

Anonymisation method. When a deletion request is approved, the person's name and username are replaced with "[deleted]", their note and Instagram user ID are removed; channel identities are replaced with an irreversible random digest (if you write again from the same account you are treated as a new person); message and comment text becomes "[deleted]" and the raw copy of the message is cleared; the content of AI call records linked to the person becomes "[deleted]". Record rows remain for statistics and de-duplication and do not identify the person. If the person had stopped messages with DUR, only a digest that does not directly identify them is kept so that the DUR decision stays in force. The process is carried out with human approval and a deletion document showing how many records changed is kept.

What is out of scope. Raw webhook notifications from Meta (event records), internal task records, the approval queue, the sending queue and the payload data in capability-call records, as well as the human queue, are outside the automatic 180-day clean-up and outside person deletion; these records may still contain personal data (for example a user ID or fragments of message text). On a deletion request these records are assessed separately; an automatic clean-up that also covers them has not been implemented yet.

8. Your rights under KVKK Art. 11

9. How to apply

You can send your requests to [email protected], stating your Instagram username and your request. Depending on its nature, your request is concluded within 30 days at the latest; requests are tracked in the management dashboard against a 30-day deadline. If you are not satisfied with the outcome, your right to complain to the Personal Data Protection Board is reserved. For deletion, see the Data Deletion page.

If you do not want messages, just write DUR in the DM (STOP and İPTAL also work): once the service goes live you are silenced on every channel and get one confirmation message. DUR does not replace a deletion request. Details: Data Deletion.