How Qm4-hermes handles data

This policy covers the Qm4-hermes Threads integration operated by @parkq for the operator’s own account management and public-content research. It also covers this static information website.

Data accessed and purposes

Depending on granted permissions and Meta approval, the integration accesses the operator’s Threads user ID, username, profile details, posts, media references, timestamps, replies, mentions, account/post insights and API limits. It can access public profiles and public posts returned by Meta’s profile-discovery and keyword-search APIs. Public content is used to examine posting patterns, compare topics and inform the operator’s account planning. The integration does not provide access to other users’ private accounts or private messages.

Publishing and management actions use the operator’s supplied text, media URLs, target post IDs, reply settings, location information or linked-account options as applicable. Access tokens authorize API operations. Only the operator’s authorized accounts are used for publishing and management.

Storage and retention

The integration runs on the operator’s device. Credentials are stored in the macOS login Keychain and a local environment file restricted to the local user. They are not included in this website. API outputs, research exports, prompts, reports and conversation history may be retained in local files or by the operator’s configured assistant client. This is not a zero-retention service.

If scheduling is used, scheduled post text, media URLs, options and status are stored in a local schedule file; completed or cancelled entries can remain until removed. Local research files and schedules are kept until the operator deletes them or no longer needs them. Credentials remain until revoked, replaced, expired or removed. Provider-controlled records follow those providers’ retention terms and settings.

Data recipients and AI processing

API requests and authorized content actions are sent to Meta. When the operator uses an AI assistant with this integration, selected API results, public posts, prompts and drafts may be sent to the configured AI/assistant provider for analysis or drafting, and may be stored in that provider’s conversation history or logs under its policies and settings. Data sent to these providers may be processed outside the operator’s country. The operator does not sell data or operate a third-party customer data service.

This website

This website serves static app information and does not contain a login, token-entry form, analytics script or advertising tracker. Cloudflare hosts it and may process IP addresses, request metadata and security logs to deliver and protect the site. See Cloudflare’s privacy policy. Meta data is not embedded in this website.

Security and control

Requests to Meta use HTTPS. The operator limits local credential-file access and must not share credentials in public reports. The operator can revoke app access from Threads settings. Revoking access stops future authorized API use but does not automatically erase previous exports, scheduled items or assistant history.

Access, correction and deletion requests

Contact the operator by email at pouch.cordons_0p@icloud.com. Describe the request and provide the relevant public username or post URL where possible. Do not send tokens, passwords or identity documents. The operator may request proportionate proof that a request concerns your data. See the data deletion instructions for local and provider-specific cleanup.

Changes

This page will be updated when the app’s data handling changes. The date below identifies the current version.