Search and filter the most common questions about CineMind.
About these answers
Why the FAQ exists
The questions CineMind receives are rarely about buttons. They are about how recommendations are formed, why a film you love was scored the way it was, and how much of the writing is machine-assisted. Those answers deserve to be public and consistent, so they live here rather than in individual replies.
Every answer stays in the page source instead of being fetched when you expand it, so the full text is readable by search engines, assistive technology and browser find-in-page.
How answers are kept accurate
When the recommendation logic, the duel arena scoring or the account limits change, the affected answers are rewritten in the same release. Numbers — turn allowances, storage windows, refund terms — are stated exactly rather than described vaguely.
Longer explanations live elsewhere and are linked: taste and methodology questions point to the trust page, account and billing questions point to the help centre, and anything needing a person points to contact.
If your question is missing
Search covers every published answer, including those not currently visible under the active filter. If nothing matches, contact lists which route reaches which desk; if an answer is wrong rather than absent, a correction request is the fastest way to get it changed and credited.
Behind the answers on this page
How a question gets here
A question earns a place once it has arrived from three separate directions — sessions, support, reader mail. Below that threshold it gets a reply, not a page, which keeps this list short enough to scan.
Answers are written to close the question. Where the honest answer is 'no' or 'not yet', that is what appears.
Why everything is in the page source
Answers are rendered into the HTML rather than fetched on click, so find-in-page, screen readers, translation tools and search engines can all read them without running our filter code.
The search and filter controls sit on top of content that already exists, which is why the page still works with scripting turned off.
Keeping them accurate
Any answer quoting a limit — turn allowances, retention, refunds — is updated in the release that changes the limit. An FAQ contradicting the product is worse than none.
If something here disagrees with what the app does, that is a bug worth reporting; the contact page routes it to the publisher.