Data Deletion Instructions

Threads Monitor Bot
Last updated: August 7, 2026

This page explains how to request deletion of data associated with your use of Threads Monitor Bot, including Telegram chat settings and monitoring data stored by the App.

1. What we can delete

Upon a verified request, we delete or anonymize:

• Your Telegram chat monitoring settings
• The encrypted Threads access token, Threads account metadata, and chat binding
• Search phrases you added to the monitoring pool (when they are tied to your use of the App)
• Records of seen / notified post IDs related to your monitoring
• Related application logs that still contain your identifiers, where reasonably feasible

We cannot delete content that remains on Threads or Telegram themselves. To revoke Meta / Threads access granted to the App, use your Meta account settings (Apps and Websites / Business Integrations).

2. How to request deletion

1. Send an email to adigitalnyc@gmail.com with the subject line: Threads Monitor Bot Data Deletion Request
2. Include:
   • Your Telegram username and/or numeric Telegram user ID
   • The chat where you used the bot (private chat or group), if known
   • Optional: date range of use
3. We will verify the request (we may ask a short confirmation via Telegram or email) and delete the associated App data.
4. You will receive a confirmation when deletion is complete.

3. Processing time

We aim to complete deletion requests within 7 days, and sooner when possible. If additional verification is needed, we will contact you at the email address you used to submit the request.

4. Stop using the App without full deletion

You can also:

• In Telegram, send /monitor off to stop notifications
• Remove phrases with /remove
• Block or delete the bot chat in Telegram
• Revoke the App’s Threads permissions in your Meta account settings
• If you are the bot administrator, send /disconnect_threads in a private chat

5. Meta / Facebook data deletion callback

If Meta sends a platform data-deletion callback for a user who authorized the App, the App verifies Meta’s signed request, removes the encrypted Threads credential and account/chat binding, and returns a confirmation code with a public completion-status URL. Operational monitoring data that is not keyed to the authorizing Threads user is handled through the verified email-request process above.

6. Contact

Privacy questions: adigitalnyc@gmail.com
Related policy: Privacy Policy