Yaziio logoYaziio

Privacy Policy

Last updated: 4 October 2026

Yaziio is an AI-assisted messaging and sales application that aims to reply to comments and direct messages received by Instagram professional accounts, and it is under development. This policy explains what data we will process once the service goes live and why, and what rights you have. See also our GDPR Privacy Notice and the KVKK Notice.

Data controller: Tolga Vuranel ("Yaziio", "we"). Contact: [email protected].

Status of the service: Yaziio is in limited/private access and under development. The Meta app is not live yet, automatic replies are switched off and every reply waits for human approval before it is sent; no live user data flows. The compliance features (stopping with DUR, consent records, person deletion/anonymisation, a 180-day retention limit, encrypted token storage) are implemented in the software and covered by tests; what this page describes will apply this way once the service goes live. Working today: the webhook receiver that accepts Meta notifications after signature verification, this site and a management dashboard open only to an authorised user. Sending automatic replies and AI processing are planned. For now the only target channel is Instagram; connections for YouTube, LinkedIn, X and TikTok are being prepared.

1. What data we will process

Today the data processed is the notifications Meta sends to our webhook address (a raw event record that, depending on the notification type, may contain a user ID or comment/message text) and the internal task records created from them; because the Meta app is not live, no live user data flows. Once the service goes live, the following data will be processed.

Account owner (the person using Yaziio):

People who comment on or message the account:

We do not aim to collect sensitive data. If someone shares such information in a message, it is stored only as part of the conversation.

2. Why we plan to use it

The following purposes will apply once the service goes live; today only incoming notifications are stored.

We do not use data to build advertising profiles and we do not sell it.

3. AI processing (planned)

Once reply generation goes live, some messages will be sent to Anthropic's AI model (Claude) to draft a reply and to determine the topic of a message. Because no live user messages flow today, no real user message is sent to an AI model; for now every reply also goes through human approval before it is sent. See the AI Disclosure page.

4. Who we will share data with

Your data is not sold. It is not shared with other third parties unless legally required.

5. Retention

Message and comment content is kept for 180 days and then deleted: a daily automatic job replaces message and comment text that has reached 180 days with "[deleted]" (the record is left only with an identity digest and timestamps, and the raw copy of an incoming message is also cleared). AI call records are also 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. Limit: raw webhook notifications from Meta and internal task, approval-queue, sending and capability-call records are outside this clean-up and outside person deletion; they may still contain personal data (for example a user ID or fragments of text) and are assessed separately on a deletion request. Consent records and the DUR record are kept as legal evidence with a digest that does not directly identify the person (details: KVKK Notice). The access token is kept until the account connection is removed; the deletion period after removal will be set separately. You may ask us to delete data earlier, see by email.

6. Security

Working today: notifications from Meta are verified with X-Hub-Signature-256 signature validation (requests with an invalid signature are rejected); the site is served over HTTPS with security headers; the management dashboard is not open to the public internet and is reachable only over a private network and with a password. Implemented in the software, applies once the service goes live: access tokens for the YouTube, LinkedIn, X and TikTok connections are stored in the database with field encryption (Fernet) and nothing is written if the encryption key is missing; the Instagram access token is not in the database but in the server's secret configuration; audit records never contain a token value.

7. Stopping messages: write DUR

If you do not want to receive messages from Yaziio, just write DUR (Turkish for "stop") in the Instagram DM; STOP, İPTAL, "bana yazma" and "abonelikten çık" work the same way. The whole message must be the command; sentences such as "I want to cancel my registration" count as a support topic, not as a stop command. Once the service goes live it works like this (the compliance desk is implemented in the software and covered by tests; there is no live message flow yet):

8. Your rights and deletion requests

You have the right to access, correct, delete your data, to object to processing, and to know who it was shared with. To request deletion, follow the steps on the Data Deletion page or write to [email protected]. Once account connection goes live, you will also be able to remove Yaziio's access to your Instagram account at any time under Settings > Apps and websites.

9. Children

The service is not directed to anyone under 13. If we learn that we hold data of a child under this age, we delete it.

10. Changes

We may update this policy. Material changes will be announced on this page and the date above will change.