Remove access and request deletion
These instructions apply to the Qm4-hermes Threads integration operated by @parkq.
1. Revoke future access
In Threads, open Settings → Website permissions → Active, select Qm4-hermes and choose Remove. This revokes the app connection. It does not delete existing Threads posts, previously exported files or assistant history.
2. Request deletion of retained app data
Email pouch.cordons_0p@icloud.com with the subject “Qm4-hermes data deletion.” Include your public username and any relevant post URLs, and specify whether you want all associated retained app data removed or only particular records. Never include access tokens, passwords or identity documents.
The operator will review the request, seek proportionate verification when needed, identify applicable retained local records, delete records within the operator’s control that are covered by the request, and reply with the outcome or explain any remaining limitation. This website does not collect deletion requests through a form.
3. Operator’s local cleanup
- Revoke the app grant and remove its token from the macOS login Keychain and the local environment file.
- Cancel pending scheduled items before stopping the integration, and remove the local schedule file or affected entries.
- Remove relevant saved API responses, exports, analysis reports and local assistant histories.
- Review backups or synced copies separately; deleting an active file may not immediately remove historical backup copies.
4. Data held by Meta or assistant providers
App-data deletion does not automatically delete original Threads posts. Account owners must manage those posts through Threads or separately authorize the operator to perform supported actions. For conversation history or other records held by an AI/assistant provider, use that provider’s deletion controls or contact process. The operator can delete records under their control but cannot guarantee deletion of records controlled solely by another provider.