How Can We Help You?

Search common questions about discovery, requests, favorites/bookmarks, premium logic, and support ticket behavior.

FAQ illustration
Create Ticket

Frequently Asked Questions

Answers below reflect current platform behavior across cloud analytics, requests, favorites/bookmarks, premium email options, notifications, and support.

Discovery & Keyword Cloud

How does the keyword cloud work?

The cloud is generated from weighted keyword usage and relationship edges between shows, members, groups, and cast/post links.
Counts can change when new posts, casts, or metadata are indexed, so node ranking and relationship strength are recalculated.
No. Some routes are internal app endpoints and may change without compatibility guarantees unless explicitly documented.

Requests & Voting

Why do I see possible duplicate warnings?

New requests are checked against recent submissions using title similarity, release timing, and cast overlap to consolidate demand.
Open means under review, On Hold means pending external conditions, and Resolved means the request has been completed or addressed.
Verification protects contact and request pipelines against automated abuse and reduces spam submissions.

Favorites & Filoz Premium

How do favorite limits work?

Standard accounts have base favorite limits, while users linked to verified Filoz premium can access higher favorite capacity. Bookmarked posts are managed separately in My Highlights.
That email toggle is a Premium Filoz-only feature. In-app favorite notifications still work for all users.
We match your account email against the Filoz premium API. If premium is active, premium favorite-email alerts stay available. If status expires or verification later fails, the email toggle is turned off automatically.

Security, Tickets & Notifications

How are ticket IDs generated?

Contact tickets use an RQ-prefixed reference with date + increment logic (for example YYYYMMDD + 4-digit sequence) to stay unique and sortable.
Users receive email notifications when admins reply, and admins are notified when users create tickets or add replies, including message text and ticket details.
Access is protected by authentication, role permissions, verification-code middleware, and two-factor policies. Users can enable 2FA with either email verification codes or an authenticator app.

Guides & Quick Actions

Open Full Guide
Platform Guide
Detailed explanation of cloud keywords, requests workflow, favorites/bookmarks, notifications, and premium gating.
Read Guide
Ask Support
Open a ticket from the contact form, track replies, and receive email notifications whenever an update is posted.
Create Ticket
Policy & Terms
Review usage rules, privacy commitments, and operational policy details for requests, accounts, and support.