GDPR Privacy Notice
Regulation (EU) 2016/679 · Last updated: 4 October 2026
This notice is for people in the European Economic Area, the United Kingdom and Switzerland whose personal data is processed through Yaziio, for example when they comment on or send a message to an Instagram account that uses Yaziio.
Data controller: Tolga Vuranel ("Yaziio", "we"). Contact: [email protected].
1. Data we will process (once the service is live)
Instagram-scoped user ID and username; comment and message content, timestamps and interactions (such as button taps); replies sent by Yaziio; conversation state and tags; and, for account owners, the connected account's ID and an access token (stored protected). Today, the notifications Meta sends to our webhook are received and stored as raw event records and internal task records.
2. Purposes and legal bases (Art. 6), once the service is live
- Replying to your comment or message and routing it to the right answer: performance of a request you made / steps prior to entering a contract (Art. 6(1)(b)) and our legitimate interest in running a responsive service (Art. 6(1)(f)),
- Security, abuse prevention and debugging: legitimate interests (Art. 6(1)(f)),
- Anonymous content-idea analysis (themes only, no personal data): legitimate interests (Art. 6(1)(f)),
- Legal obligations: Art. 6(1)(c).
Where consent is needed, we ask for it and you can withdraw it at any time.
3. Recipients and international transfers
Once the service is live: Meta Platforms (Instagram) to send and receive messages (today we only receive notifications from Meta); Anthropic (AI model provider, United States) to generate replies and classify messages (planned; because no live user data flows, no live data is sent to Anthropic today); and infrastructure providers needed to operate the service. Transfers outside the EEA/UK rely on appropriate safeguards such as Standard Contractual Clauses or an adequacy mechanism, where required.
4. Retention
Message and comment content: kept for 180 days, then deleted (a daily automatic job replaces the text with "[deleted]"; AI call records are cleared at 180 days, the email contact log at 365 days). This is implemented in the software and covered by tests and will apply once the service goes live; it has not yet run on live user data. Raw webhook notifications and internal task, approval-queue and sending records are outside this clean-up; they are assessed separately on an erasure request. Access tokens: until the connection is removed.
Consent records, anonymisation and scope of erasure
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.
5. Automated processing
Once reply generation is live, replies may be drafted by an AI model. We do not take decisions that produce legal or similarly significant effects solely by automated means. You can ask for a human at any time, and conversations that cannot be answered reliably are handed to a human. See the AI Disclosure.
6. Your rights (Arts. 15–22)
You have the right of access, rectification, erasure, restriction, data portability and objection, and the right not to be subject to solely automated decisions with significant effects. To exercise them, write to [email protected] with your Instagram username; we respond within one month. You may also lodge a complaint with your local supervisory authority. See Data Deletion.
7. Stopping messages
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.
8. EU/UK representative and DPO
We are not required to appoint a Data Protection Officer. Questions may be sent to the contact address above.