Last updated: June 7, 2026
Privacy Policy
This Privacy Policy explains how Threads Stock Monitor handles information. The application is a limited-access internal tool operated by authorized app operators, app roles, and testers.
1. Application Overview
Threads Stock Monitor is a local automation tool used to search selected public Threads keywords or topic tags, save matching public posts, and optionally create private summaries or notifications. The tool does not provide public user registration, user profiles, advertising, or public analytics. Access is limited to authorized accounts that have permission to operate or test the app.
2. Information Processed
The application may process the following information when configured by an authorized operator:
- Threads account information returned by the Threads API, such as account ID and username.
- Threads OAuth access tokens and related app credentials used to call the Threads API.
- Public Threads post data returned by the API, such as post ID, username, text, permalink, timestamp, topic tag, and raw API response data.
- Configured search terms, schedule settings, local logs, SQLite records, JSON output files, and AI analysis results.
- Optional notification payloads sent to a configured Discord webhook or other notification adapter.
3. How Information Is Used
Information is used only to operate the internal monitoring workflow, including:
- Authenticating with the Threads API.
- Searching public Threads content that matches configured keywords or tags.
- Deduplicating and storing search results locally.
- Generating private summaries, daily reports, or realtime analysis when AI analysis is enabled.
- Sending optional notifications to channels configured by an authorized operator.
- Maintaining operational logs and troubleshooting the application.
4. Local Storage and Retention
By default, data is stored on the operator's local machine in configuration files, a SQLite database, JSON output files, and log files. The application does not operate a central cloud database for public users. Data remains until an authorized operator deletes it, changes retention settings, or removes the application files.
5. Third-Party Services
The application may interact with third-party services selected and configured by an authorized operator:
- Meta Threads API, to authenticate and retrieve public Threads data.
- An OpenAI-compatible AI provider, if AI analysis is enabled, to summarize selected post content.
- Discord, if webhook notifications are enabled, to deliver summaries or alerts.
These third-party services process information according to their own privacy policies and terms. Authorized operators should review those policies before enabling integrations.
6. Sharing and Sale of Information
The application does not sell personal information. It does not share information with advertisers or data brokers. Information is shared only as needed to use the configured third-party integrations described above or when required by law.
7. Security
Access tokens and API keys should be kept in local environment files or other secure secret storage controlled by the operator. Authorized operators are responsible for protecting the local machine, rotating credentials if they are exposed, and disabling integrations that are no longer needed.
8. Children's Privacy
The application is not directed to children and is not intended to knowingly collect information from anyone under the age required by applicable law.
9. Data Requests and Deletion
Because this is a limited-access local application without public user accounts, there is no public account portal. Authorized users may request deletion of locally stored account tokens, configuration records, logs, JSON outputs, and database records by contacting the app operator through the account, developer profile, or submission channel where this application is registered.
Public Threads post data may also be removed from the local application storage when required by platform policy, applicable law, or an authorized deletion request.
10. Changes
This policy may be updated from time to time. The updated version will be posted on this page with a revised "Last updated" date.
11. Contact
For privacy questions, contact the app operator through the account, developer profile, or submission channel where this application is registered.