The Curator — Frequently Asked Questions

Most questions sent to The Curator are about method: how works are chosen, whether attributions are checked, and how much of the writing is machine-assisted. Those answers should be public and identical for everyone, so they are collected here instead of being repeated privately.

Answers remain in the page source rather than loading on expand, so the full text is available to search engines, screen readers and find-in-page.

When salon features, collection tools or account limits change, the relevant answers are rewritten in the same release. Limits and terms are given as figures, not adjectives.

Deeper explanations are linked rather than duplicated: methodology and sourcing point to the trust page, account and billing point to the help centre, and anything needing a person points to contact.

Search spans every published answer, including ones hidden by the current filter. If nothing matches, the contact page explains which route reaches which desk; if something here is inaccurate, a correction request is the fastest path to a fix, and corrections are credited.

A question earns a page once it has arrived from three separate directions — sessions, support, reader mail. Below that it gets a reply rather than an entry, which keeps this list short enough to scan rather than search.

Answers are written to close the question. Where the truthful answer is 'no' or 'not yet', that is what it says.

Answers are rendered into the HTML rather than fetched on click, so find-in-page, screen readers, translation tools and search engines can read them without executing our filter code.

The search and filter controls are conveniences on top of content that already exists — which is why the page still works with scripting disabled.

Any answer quoting a limit — turn allowances, retention, refunds — is rewritten in the same release that changes the limit. An FAQ that contradicts the product is worse than no FAQ.

If an answer here disagrees with what the app does, that is a bug worth reporting, and the contact page routes it to the publisher.