Privacy Policy
How StoryPeek handles viewing requests and support information.
Last updated: 2026-11-10
Viewing requests
You do not need to create an account or share an Instagram password to use the public viewer. We process the username, profile link, post link or Highlight link you submit to request public profile and media data from a third-party Actor through Apify. Apify and the Actor operator receive that request and may retain input, run metadata and output under their own policies.
Temporary data and media
The application keeps a bounded, in-memory result cache for up to two minutes to reduce duplicate requests. This cache is not a public search history or a permanent archive. Story media is loaded from Instagram or Meta CDN addresses, which receive normal browser request information such as your IP address. Application logs do not intentionally include query handles or provider credentials; hosting and security providers may process request metadata.
Support accounts
If you create an account for support, the site processes your account details, session information, and tickets to provide that service. Do not include passwords, session cookies, or API tokens in tickets. Public viewing does not require a support account.
Cookies and analytics
The site can store language, theme, session and preference cookies. Analytics, advertising and third-party support scripts are off unless configured by the operator. If enabled, the operator must review the applicable disclosure and consent settings before launch.
Requests and questions
Use the content and support page to ask about data held by StoryPeek or submit a review request. Requests about data held by Apify, an Actor operator, Instagram or Meta may also need to be directed to that provider. See Apify’s privacy policy.
TikTok media
TikTok queries send the public username to an Actor through Apify. To make returned files playable without TikTok login or special browser headers, this Actor can temporarily save media in Apify storage. Those files follow Apify’s retention rules, not the application’s two-minute in-memory cache. Opening media also sends normal browser request information to Apify or the source CDN. StoryPeek does not run scheduled collection or publish users’ viewing histories.