Yaziio logoYaziio

Data Deletion Instructions

Last updated: 4 October 2026

If you want the data Yaziio processes about you to be deleted, follow the steps below.

1. Send a deletion request

Email [email protected] with the subject "Data deletion request" and include:

2. What happens next

3. If you are an account owner (you use Yaziio)

Once account connection goes live, you will be able to remove Yaziio in Instagram under Settings > Apps and websites. Once access is removed no new data is received; send the request above to have existing data deleted as well.

4. Automatic deletion (180 days)

Message and comment text is deleted automatically after 180 days even without a request (a daily job replaces the text with "[deleted]"). This job is implemented in the software and covered by tests; it will apply once the service goes live and has not yet run on live data. The limits are stated in section 6.

5. 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):

6. Scope of deletion, anonymisation and consent records

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.

More information: Privacy Policy · GDPR Notice