StackRadar Publisher
Privacy Policy
Effective and last updated: 30 October 2026
This policy describes the StackRadar Publisher app and its repository-link automation for @thestackradar. The app is operated by the owner of that account. It publishes StackRadar videos and can send a single private reply when you comment a reel’s stated keyword.
Information the app processes
- For the connected StackRadar account: account and Page identifiers, profile name, authorized access credentials, and information needed to publish and track its videos.
- For comments on mapped StackRadar reels: comment text, comment identifier, timestamp, and commenter identifier or username when Meta makes them available. Text is checked for the reel’s keyword; the automation does not store the raw comment text or username in its reply database.
- For duplicate prevention and delivery: comment and reel identifiers, a one-way hash derived from the commenter identifier or username, the repository URL, outgoing reply text, delivery status, timestamps, and Meta’s message identifier. The hash is a pseudonymous identifier, not a promise of anonymity.
- Our hosting and network services may process routine technical information, such as IP addresses and request details, to deliver and protect the website.
Why it is used
Information is used to operate the connected StackRadar account, identify an explicit keyword request, send the correct reel’s repository link, avoid duplicate replies, and diagnose failures. The comment-link automation does not read your inbox, send follow-up messages, or hide or delete comments. Comment text is not sent to the video script’s generative-AI service by this automation.
Private replies and choice
Commenting the reel’s exact stated keyword requests its link. Matching is case-insensitive and accepts surrounding punctuation or emoji. Other comments are ignored. The bot sends at most one private reply per person per reel. A reply may appear in Message Requests. You do not need to comment a keyword to watch videos, and can avoid future automated replies by not making further keyword requests.
Services and disclosure
The app uses Meta’s Instagram/Facebook APIs and existing hosting and network services to deliver its features. Relevant identifiers and outgoing reply text are transmitted to Meta to send the requested reply. The app has no feature that sells comment data or shares it with advertisers. Meta independently handles information under its own policies; this policy does not replace those policies.
Storage, security and retention
Access credentials and delivery records are stored in restricted server files and databases, separate from the public website. Records are retained for operation, duplicate prevention and troubleshooting. There is currently no automatic time-based purge of reply records. Deletion can be requested using the instructions below. Restricted backups may retain older copies until they are replaced or removed. No system can guarantee absolute security.
Access, correction and deletion requests
Contact the account owner through Instagram at @thestackradar with “Privacy request” and the relevant reel/comment link. Requests are reviewed manually; the bot does not need inbox-read permission for the owner to receive them. We may ask you to verify control of the commenting account. Do not send passwords, authentication codes or access tokens.
See data-deletion instructions for the process and its limits. Deleting a public Instagram comment does not itself remove the app’s already-stored delivery record.
Changes
Updates will be published on this page with a revised date. Material changes to what the automation does should be reflected here before they are enabled.