Privacy Policy
AppsHook shares App Store deals. Content OS is the tool used to prepare and publish AppsHook content and respond to requests for app links on connected social accounts.
Social-platform data we process
For the connected AppsHook Instagram, Facebook and Threads accounts, the tool processes data provided by the platforms within the permissions granted to it:
- Account and content identifiers, public profile names, post links, captions and publication results.
- Instagram comment identifiers, usernames, media identifiers and timestamps for app-link requests.
- Messages sent to AppsHook, their text, platform-scoped sender identifiers and timestamps.
- Delivery identifiers and technical statuses used to prevent duplicate posts or replies and investigate failures.
Meta access tokens are stored separately as protected credentials. They are not included in public pages or replies. This tool does not request a visitor's Instagram password, payment-card details or App Store purchase history.
How this information is used
We use it to publish content to connected AppsHook accounts, identify the app or apps in a post, send a requested App Store link, ask for clarification when needed, and confirm delivery in a public reply. App Store information and pricing are obtained from Apple's public catalogue. Prices can change and vary by region.
Sending “APP” in a comment may trigger a private reply with the app links from that post and a public delivery confirmation. A request in Direct without clear context may receive a question about the app name. The original comment is not deleted.
Storage, retention and access
The automation runs on privately administered infrastructure. Access to its editor, credentials and delivery records is restricted to the operators of AppsHook.
- Completed or ignored request payloads and saved reply text are normally cleared from the automation inbox after 30 days. Event identifiers are retained to prevent replay.
- Unresolved delivery failures may be retained until reviewed. Technical logs and recovery backups may retain records separately from the active inbox.
- Automation execution history is limited to seven days or 1,000 saved runs, whichever limit is reached first.
Platform copies of posts, comments and conversations remain subject to the platform's own settings and retention. Deleting our automation's local copy does not delete a public comment or a conversation from your Meta account.
Website analytics
The AppsHook website uses Umami and Yandex Metrica to understand website usage. Page visits, browser/device information and referral information may be processed. Yandex Metrica uses cookies; where the consent control is shown, you can decline or change your choice using the Cookies control. See Yandex's privacy policy for its processing practices.
Third-party platforms
Meta and Apple process information under their own policies when you use their services or open an App Store link. Messages and replies are sent through the official platform interfaces. This policy describes AppsHook's automation, not the privacy practices of the apps featured in its posts.
Your requests and contact
For questions, access or deletion requests, contact @appshook on Instagram in Direct. Use the same account involved in the request so that we can verify which records belong to you. Do not send passwords, login codes or identity documents in Direct.
See data-deletion instructions for the request steps and the distinction between local automation records and platform data.