Privacy Policy

Last updated: 2 October 2026

This policy describes the current Hearkly prototype, operated by Denis Shumilov in Kyiv, Ukraine. Contact: [email protected].

What information is handled

• Connected Threads account ID, username and access token, used to identify the account and make authorized API requests. Hearkly does not ask for or store the account password.
• Post IDs, author usernames, text, links and publication times returned by Threads or supplied by the owner, used for keyword search, display, relevance assessment and drafting.
• Business context and keywords provided by the owner, AI scores, reasons and reply drafts, and the owner's edits and decisions.
• Telegram owner ID and bot configuration, used to restrict access to the owner and deliver results.
• Published reply IDs and operational logs, used to manage approved replies and diagnose errors.

Where information goes

Meta receives Threads API requests and approved reply text. Telegram receives messages, post text, assessments and drafts delivered to the owner's bot chat.

The current test uses OpenAI Codex signed in through the operator's ChatGPT subscription. Post text and business context supplied for an assessment are processed by OpenAI in the cloud. They are not analyzed entirely offline. OpenAI's terms, privacy policy and the account's data settings apply. Hearkly does not itself train AI models on Threads data; it does not guarantee a provider's training, retention or deletion settings.

The prototype's database, access token configuration and operational logs are stored on the operator's computer in Ukraine. This static information website does not host the bot database or token. Its hosting provider processes website requests and technical data under its own policy. The intended website host is Cloudflare Pages; no analytics, forms or tracking scripts are added to these pages.

Storage and deletion

Stored assessments and reply records remain in the local prototype database until the operator removes them. There is currently no automatic retention expiry. Tokens remain in local configuration until removed or replaced, or until they expire. Operational logs are retained locally until the operator removes them.

To request removal of your stored data, email [email protected] with your Threads username or the public post link. Requests are handled manually; see Data Deletion Instructions. Do not send passwords or access tokens.

Removing Hearkly in Threads revokes its access. It does not automatically erase the local database: this prototype has no automatic deauthorization or deletion callback. Contact the operator for local deletion. Telegram messages and posts already published on Threads must also be managed in those services; Hearkly cannot promise deletion of their copies.

Use and your choices

Hearkly uses information to provide its search and drafting workflow, manage owner-approved replies and troubleshoot the prototype. It does not sell post data or use it to build advertising profiles. A draft is a suggestion, not an automatic public message.

You can ask the operator about, correct or request deletion of information held by the prototype. You can stop using it and revoke Threads access at any time. Material changes to this workflow will be reflected in this policy before a public service is offered.