StoryViewer Questions and Answers

A subscription service that monitors supported, publicly accessible TikTok Stories and regular posts and places successful captures in a private account archive.

Sign in with Google, choose a plan, and add public creators. Server workers check Story and Post feeds, download supported media, and grant captures to eligible monitoring periods.

Yes. They appear in separate tabs and share the service's provider request quota.

No. StoryViewer is independent and is not affiliated with or endorsed by TikTok.

You can request a public username, but access is not guaranteed. Private, restricted, unavailable, or unsupported feeds cannot be captured.

You can download Story media successfully captured for your account while archive access is active.

Yes. An active creator monitor checks regular posts as well as Stories.

Yes, when the provider supplies a supported public source. Video, JPEG, PNG, and WebP media are supported.

Supported slideshows are archived as individual images when the provider exposes downloadable image sources.

No. A Story that expired before StoryViewer captured it cannot be recovered automatically.

Only if StoryViewer archived the post before it became unavailable. Content removed before capture cannot be recovered.

A successful capture remains under current access and retention rules. This does not grant redistribution rights, and valid removal requests require review.

Yes. One monitored creator covers both feeds and counts once toward the plan limit.

The configured default is every 15 minutes. Shared limits, retries, pagination, or upstream backpressure can delay a check.

No. Timing, public visibility, provider availability, rate limits, supported formats, and network failures affect capture.

StoryViewer backfills posts still available through the public creator feed. Pagination shares the quota, so a large history appears gradually.

It begins when you activate monitoring for a creator. Each later stop and restart creates another recorded period.

Archive grants depend on each account's eligible monitoring periods and when a capture succeeds.

Yes. Account-specific grants are checked before listing or serving media, even when identical stored bytes are safely deduplicated.

A creator occupies its slot for 30 days. After the commitment expires, you may replace it; its historical grants and shared media remain preserved but are hidden unless that creator occupies an eligible slot again.

Granted captures currently have no automatic age-based expiry. StoryViewer retains them while needed to provide archive access, maintain recorded grants, resolve rights requests, or meet legal and security obligations.

Yes. Authenticated customers with archive access can download original files that were successfully captured.

The archive separates Stories and Posts and supports creator filtering, date ordering, grid or timeline layouts, and pagination.

An eligible customer receives one trial when Stripe creates the first subscription. Registration alone does not start it.

The current Checkout configuration requires one. Checkout displays the future monthly charge before confirmation.

The selected monthly plan begins unless cancelled. If payment cannot continue, monitoring pauses and archive access is normally restricted.

Starter supports 1 creator, Basic 5, Pro 10, and Business 25. Each confirmed creator occupies one slot for at least 30 days and includes both Story and Post monitoring.

Yes. Use the Stripe billing portal, which shows the effective date and any billing adjustment.

Use the billing portal from the dashboard. Access continues through the recorded subscription access period.

Monitoring stops after access expires. Grants remain recorded; resubscribing restores eligible prior grants without filling inactive Story gaps.

Stripe hosts Checkout and the billing portal and processes payment details. StoryViewer stores Stripe references, not card numbers.

Subscription charges are non-refundable after a billing period or trial converts, except where applicable law requires a refund. Contact support if you believe a charge was made in error or a mandatory consumer remedy applies.

No. StoryViewer supports publicly accessible content and does not accept TikTok account passwords.

StoryViewer itself sends no creator notification. It cannot make claims about logging or notices controlled by TikTok or upstream providers.

No. Customer sign-in uses Google, and monitoring only needs a public creator username or profile reference.

Secure HTTP-only sessions, Google verification, CSRF checks, account authorization, no-store responses, and server-side media checks protect the implemented flow.

Use the Contact page and identify the content, your rights or authority, and a way to reach you. StoryViewer may verify the request, temporarily restrict access during review, and remove or restore access based on the evidence and applicable law.